Your Website Score is

Similar Ranking

19
LIMELITE SEO ANALYZER
limelitehosting.co.za
19
BLIMEY SOLUTIONS LTD - CIS ACCOUNTING & RECRUITMENT SERVICES IN LONDON
blimeysolutions.com
19
HIGH DEFINITION ANDROID CAR RADIOS | KNK AUDIO VISUAL
knkaudiovisual.co.za
19
SIMS PEEK | SIMS STORIES FOR SIMS FANS
simspeek.com
19
SEO TOOLS BY LIMELITE
tools.limelitehosting.co.za
19
ÇAKIRLAR SAĞLIK KABINI - BATIKENT ANKARA
cakirlarsaglikkabini.com.tr
19
TROPOJA CONSTRUCTION LTD | TRUSTED CONSTRUCTION COMPANY IN LONDON
tropojaconstructionltd.co.uk

Latest Sites

19
FREE BUSINESS DIRECTORY LISTINGS | BUSINESS LISTINGS
seekabiz.co.za
22
HIRE A WEB DESIGNER | RESPONSIVE WEBSITE DESIGN
limelitedesign.co.za
26
THE BRA GURU - ONLINE BRA SHOP - SHOP OUR BEST-SELLING BRAS
shop.thebraguru.co.za
19
HIGH DEFINITION ANDROID CAR RADIOS | KNK AUDIO VISUAL
knkaudiovisual.co.za
19
SIMS PEEK | SIMS STORIES FOR SIMS FANS
simspeek.com
19
BRIGHTON EAGLE CHAUFFEUR & TAXI - CHAUFFEUR DRIVEN EXECUTIVE CAR HIRE
brightoneaglechauffeur.com
89
BUFFER: ALL-YOU-NEED SOCIAL MEDIA TOOLKIT FOR SMALL BUSINESSES
buffer.com

19 seekabiz.co.za Last Updated: 4 hours

Success 63% of passed verification steps
Warnings 7% of total warnings
Errors 30% of total errors, require urgent action

Desktop

Mobile

Performance Desktop Score 42%
Best Practices Desktop Score 63%
SEO Desktop Score 83%
PWA Desktop Score 29%
Performance Mobile Score 7%
Best Practices Mobile Score 59%
SEO Mobile Score 93%
PWA Mobile Score 38%
Page Authority Authority 24%
Domain Authority Domain Authority 6%
Moz Rank 2.4/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 52 Characters
FREE BUSINESS DIRECTORY LISTINGS | BUSINESS LISTINGS
Meta Description 138 Characters
Free business directory connecting you to products and services. Submit your directory listing today! Boost your online presence for free.
Effective URL 21 Characters
http://seekabiz.co.za
Excerpt Page content
Free Business Directory Listings | Business Listings ...
Keywords Cloud Density
view36 south22 africa22 cape22 directions21 site15 town15 services15 business12 other11
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
view 36
south 22
africa 22
cape 22
directions 21
site 15
town 15
services 15
business 12
other 11
Google Preview Google search result preview
FREE BUSINESS DIRECTORY LISTINGS | BUSINESS LISTINGS
http://seekabiz.co.za
Free business directory connecting you to products and services. Submit your directory listing today! Boost your online presence for free.
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~583.8 KB
Code Size: ~319.9 KB
Text Size: ~263.9 KB Ratio: 45.20%

Social Data

Only Registered Users

Sign up for see all features and reviews about this site

Login

Estimated Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Desktop

Desktop Screenshot
Minify CSS Potential savings of 6 KiB
Minifying CSS files can reduce network payload sizes
JavaScript execution time 1.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 3.6 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint 8.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid non-composited animations 2 animated elements found
Animations which are not composited can be janky and increase CLS
Largest Contentful Paint element 8,020 ms
This is the largest contentful element painted within the viewport
Cumulative Layout Shift 0.204
Cumulative Layout Shift measures the movement of visible elements within the viewport
Eliminate render-blocking resources Potential savings of 4,250 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Properly size images Potential savings of 591 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid an excessive DOM size 2,353 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Max Potential First Input Delay 140 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid chaining critical requests 78 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Network Round Trip Times 110 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Minimize third-party usage Third-party code blocked the main thread for 30 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Initial server response time was short Root document took 110 ms
Keep the server response time for the main document short because all other requests depend on it
Total Blocking Time 160 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve images in next-gen formats Potential savings of 415 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Does not use HTTPS 74 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
First Meaningful Paint 4.2 s
First Meaningful Paint measures when the primary content of a page is visible
Minimize main-thread work 2.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Reduce unused CSS Potential savings of 63 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid serving legacy JavaScript to modern browsers Potential savings of 8 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Efficiently encode images Potential savings of 167 KiB
Optimized images load faster and consume less cellular data
Minify JavaScript Potential savings of 42 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Serve static assets with an efficient cache policy 106 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid enormous network payloads Total size was 3,217 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed Index 6.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid large layout shifts 8 elements found
These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Reduce unused JavaScript Potential savings of 575 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Time to Interactive 8.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Defer offscreen images Potential savings of 158 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Server Backend Latencies 220 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Mobile

Mobile Screenshot
Avoid an excessive DOM size 2,319 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Minify JavaScript Potential savings of 42 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Meaningful Paint 7.9 s
First Meaningful Paint measures when the primary content of a page is visible
Server Backend Latencies 380 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Network Round Trip Times 70 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Efficiently encode images Potential savings of 167 KiB
Optimized images load faster and consume less cellular data
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Reduce unused CSS Potential savings of 63 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Minify CSS Potential savings of 6 KiB
Minifying CSS files can reduce network payload sizes
Reduce the impact of third-party code Third-party code blocked the main thread for 1,650 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Serve static assets with an efficient cache policy 103 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid serving legacy JavaScript to modern browsers Potential savings of 8 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Largest Contentful Paint element 13,760 ms
This is the largest contentful element painted within the viewport
Initial server response time was short Root document took 130 ms
Keep the server response time for the main document short because all other requests depend on it
Defer offscreen images Potential savings of 810 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 16.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources Potential savings of 6,490 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid enormous network payloads Total size was 3,069 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid chaining critical requests 74 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Properly size images Potential savings of 165 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint 13.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Document uses legible font sizes 93.7% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Max Potential First Input Delay 1,120 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minimize main-thread work 12.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Serve images in next-gen formats Potential savings of 415 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Time to Interactive 24.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Avoid large layout shifts 4 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
First Contentful Paint 7.9 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid non-composited animations 2 animated elements found
Animations which are not composited can be janky and increase CLS
Does not use HTTPS 72 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Total Blocking Time 3,000 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce JavaScript execution time 7.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 4 elements found
These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Reduce unused JavaScript Potential savings of 580 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Cumulative Layout Shift 0.392
Cumulative Layout Shift measures the movement of visible elements within the viewport
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

Only Registered Users

Sign up for see all features and reviews about this site

Login

Server Information

Only Registered Users

Sign up for see all features and reviews about this site

Login