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 kb-ot.co.za Last Updated: 1 week

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

Desktop

Mobile

Performance Desktop Score 64%
Best Practices Desktop Score 100%
SEO Desktop Score 73%
PWA Desktop Score 29%
Performance Mobile Score 28%
Best Practices Mobile Score 96%
SEO Mobile Score 76%
PWA Mobile Score 38%
Page Authority Authority 3%
Domain Authority Domain Authority 5%
Moz Rank 0.3/10
Bounce Rate Rate 0%
Title Tag 115 Characters
OCCUPATIONAL THERAPIST JOHANNESBURG | KIRSTEN BEUKES OCCUPATIONAL THERAPISTS
Meta Description 128 Characters
Kirsten Beukes Occupational Therapists is a medico-legal and vocational rehabilitation practise based in Randburg, Johannesburg.
Effective URL 23 Characters
https://www.kb-ot.co.za
Excerpt Page content
Occupational Therapist Johannesburg | Kirsten Beukes Occupational Therapists Home About Team Services Functional capacity evaluation Return to work rehabilitat...
Keywords Cloud Density
occupational19 work12 therapists10 kirsten9 beukes9 more8 read7 services7 challenges6 therapy6
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
occupational 19
work 12
therapists 10
kirsten 9
beukes 9
more 8
read 7
services 7
challenges 6
therapy 6
Google Preview Google search result preview
OCCUPATIONAL THERAPIST JOHANNESBURG
https://www.kb-ot.co.za
Kirsten Beukes Occupational Therapists is a medico-legal and vocational rehabilitation practise based in Randburg, Johannesburg.
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~40.64 KB
Code Size: ~19.39 KB
Text Size: ~21.25 KB Ratio: 52.29%

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
Eliminate render-blocking resources Potential savings of 410 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Network Round Trip Times 10 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
Defer offscreen images Potential savings of 388 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Reduce unused JavaScript Potential savings of 830 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
First Meaningful Paint 1.4 s
First Meaningful Paint measures when the primary content of a page is visible
Links do not have descriptive text 7 links found
Descriptive link text helps search engines understand your content
Minify JavaScript Potential savings of 2 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Minimize main-thread work 3.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid chaining critical requests 24 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
Initial server response time was short Root document took 170 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid large layout shifts 7 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)
Serve static assets with an efficient cache policy 10 resources found
A long cache lifetime can speed up repeat visits to your page
Total Blocking Time 170 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 13 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Time to Interactive 4.4 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint element 4,070 ms
This is the largest contentful element painted within the viewport
Avoid enormous network payloads Total size was 5,533 KiB
Large network payloads cost users real money and are highly correlated with long load times
Properly size images Potential savings of 554 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid an excessive DOM size 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)
Efficiently encode images Potential savings of 1,705 KiB
Optimized images load faster and consume less cellular data
Cumulative Layout Shift 0.004
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minify CSS Potential savings of 13 KiB
Minifying CSS files can reduce network payload sizes
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
Reduce the impact of third-party code Third-party code blocked the main thread for 260 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 serving legacy JavaScript to modern browsers Potential savings of 7 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 Contentful Paint 1.4 s
First Contentful Paint marks the time at which the first text or image is painted
Serve images in next-gen formats Potential savings of 2,166 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Reduce JavaScript execution time 2.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index 3.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Server Backend Latencies 630 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
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
Largest Contentful Paint 4.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce unused CSS Potential savings of 121 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity

Mobile

Mobile Screenshot
Minify JavaScript Potential savings of 2 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Largest Contentful Paint 25.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Document uses legible font sizes 99.92% 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
Links do not have descriptive text 7 links found
Descriptive link text helps search engines understand your content
Reduce initial server response time Root document took 1,170 ms
Keep the server response time for the main document short because all other requests depend on it
Minimize main-thread work 11.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Efficiently encode images Potential savings of 1,705 KiB
Optimized images load faster and consume less cellular data
Cumulative Layout Shift 0.01
Cumulative Layout Shift measures the movement of visible elements within the viewport
Defer offscreen images Potential savings of 1,584 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Minify CSS Potential savings of 13 KiB
Minifying CSS files can reduce network payload sizes
Max Potential First Input Delay 390 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid chaining critical requests 24 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
First Contentful Paint 4.5 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint element 25,400 ms
This is the largest contentful element painted within the viewport
Reduce JavaScript execution time 8.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid enormous network payloads Total size was 5,484 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Meaningful Paint 4.5 s
First Meaningful Paint measures when the primary content of a page is visible
Tap targets are not sized appropriately 95% 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
Server Backend Latencies 1,470 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
Serve static assets with an efficient cache policy 10 resources found
A long cache lifetime can speed up repeat visits to your page
Reduce unused CSS Potential savings of 122 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Properly size images Potential savings of 6 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Network Round Trip Times 10 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 2,320 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Time to Interactive 25.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Eliminate render-blocking resources Potential savings of 1,840 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid large layout shifts 5 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)
Speed Index 18.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve images in next-gen formats Potential savings of 2,145 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid an excessive DOM size 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)
Reduce the impact of third-party code Third-party code blocked the main thread for 3,430 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 serving legacy JavaScript to modern browsers Potential savings of 7 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 unused JavaScript Potential savings of 833 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
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

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