Your Website Score is

Similar Ranking

19
LIMELITE SEO ANALYZER
limelitehosting.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
SEO TOOLS BY LIMELITE
tools.limelitehosting.co.za
19
FREE SMS RECEIVE - RECEIVE SMS ONLINE WITH VIRTUAL NUMBERS
freesmsreceive.io
19
BRIGHTON EAGLE CHAUFFEUR & TAXI - CHAUFFEUR DRIVEN EXECUTIVE CAR HIRE
brightoneaglechauffeur.com
19
FREE BUSINESS DIRECTORY LISTINGS | BUSINESS LISTINGS
seekabiz.co.za

Latest Sites

19
HIGH DEFINITION ANDROID CAR RADIOS | KNK AUDIO VISUAL
knkaudiovisual.co.za
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
53
MARKET 50 DISCOUNT SALE
50discount-sale.com
99
YOUTUBE
youtube.com
26
FREEFORMĀ® TENTS | STRETCH TENTS FOR SALE
freeformtents.com

19 seekabiz.co.za Last Updated: 21 hours

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

Desktop

Mobile

Performance Desktop Score 48%
Best Practices Desktop Score 78%
SEO Desktop Score 85%
Performance Mobile Score 9%
Best Practices Mobile Score 93%
SEO Mobile Score 92%
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 22 Characters
https://seekabiz.co.za
Excerpt Page content
Free Business Directory Listings | Business Listings ...
Keywords Cloud Density
view36 cape28 africa26 south26 directions21 town18 services15 site12 business12 other11
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
view 36
cape 28
africa 26
south 26
directions 21
town 18
services 15
site 12
business 12
other 11
Google Preview Google search result preview
FREE BUSINESS DIRECTORY LISTINGS | BUSINESS LISTINGS
https://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: ~585.41 KB
Code Size: ~321.37 KB
Text Size: ~264.04 KB Ratio: 45.10%

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
Total Blocking Time 630 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce unused CSS Potential savings of 61 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Defer offscreen images Potential savings of 4 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid long main-thread tasks 7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Contentful Paint 1.2 s
First Contentful Paint marks the time at which the first text or image is painted
Time to Interactive 3.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Minify CSS Potential savings of 6 KiB
Minifying CSS files can reduce network payload sizes
Properly size images Potential savings of 472 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
First Meaningful Paint 1.2 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid chaining critical requests 73 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
Largest Contentful Paint 1.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce the impact of third-party code Third-party code blocked the main thread for 480 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
Avoid large layout shifts 3 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)
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
Reduce JavaScript execution time 1.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift 0.207
Cumulative Layout Shift measures the movement of visible elements within the viewport
Eliminate render-blocking resources Potential savings of 560 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce unused JavaScript Potential savings of 620 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid non-composited animations 2 animated elements found
Animations which are not composited can be janky and increase CLS
Largest Contentful Paint element 1,580 ms
This is the largest contentful element painted within the viewport
Network Round Trip Times 0 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
Initial server response time was short Root document took 30 ms
Keep the server response time for the main document short because all other requests depend on it
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Minify JavaScript Potential savings of 42 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Efficiently encode images Potential savings of 62 KiB
Optimized images load faster and consume less cellular data
Avoid enormous network payloads Total size was 2,960 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve images in next-gen formats Potential savings of 315 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Minimize main-thread work 4.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index 3.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Max Potential First Input Delay 310 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Server Backend Latencies 40 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
Avoid an excessive DOM size 2,369 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)
Serve static assets with an efficient cache policy 109 resources found
A long cache lifetime can speed up repeat visits to your page

Mobile

Mobile Screenshot
Largest Contentful Paint element 7,730 ms
This is the largest contentful element painted within the viewport
Max Potential First Input Delay 1,160 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
First Meaningful Paint 5.6 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint 5.6 s
First Contentful Paint marks the time at which the first text or image is painted
Server Backend Latencies 130 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
Speed Index 11.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce the impact of third-party code Third-party code blocked the main thread for 2,100 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
Avoid non-composited animations 2 animated elements found
Animations which are not composited can be janky and increase CLS
Serve images in next-gen formats Potential savings of 315 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Efficiently encode images Potential savings of 62 KiB
Optimized images load faster and consume less cellular data
Serve static assets with an efficient cache policy 116 resources found
A long cache lifetime can speed up repeat visits to your page
Eliminate render-blocking resources Potential savings of 2,760 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce unused CSS Potential savings of 62 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Cumulative Layout Shift 0.392
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid chaining critical requests 70 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
Reduce unused JavaScript Potential savings of 630 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Reduce JavaScript execution time 8.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minify CSS Potential savings of 6 KiB
Minifying CSS files can reduce network payload sizes
Minify JavaScript Potential savings of 42 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Initial server response time was short Root document took 70 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid large layout shifts 5 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)
Largest Contentful Paint 7.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Properly size images Potential savings of 115 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Network Round Trip Times 30 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
Total Blocking Time 4,160 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid an excessive DOM size 2,335 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)
Time to Interactive 18.5 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
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
Minimize main-thread work 15.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 513 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid enormous network payloads Total size was 4,084 KiB
Large network payloads cost users real money and are highly correlated with long load times
Document uses legible font sizes 93.31% 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

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