Your Website Score is





Similar Ranking

27
BRA FITTING SPECIALISTS IN JOHANNESBURG | THE BRA GURU
thebraguru.co.za
26
THE BRA GURU - ONLINE BRA SHOP - SHOP OUR BEST-SELLING BRAS
shop.thebraguru.co.za
24
THE REIGATE MARBLE SHOP | GRANITE WORKTOPS & MARBLE WORKTOPS IN SURREY AND ALL AROUND SUS---
marble-shop.co.uk
23
TURBOWORKS - BEST QUALITY TURBOCHARGERS - NO COMPROMISE
turboworks.co.za
22
HIRE A WEB DESIGNER | RESPONSIVE WEBSITE DESIGN
limelitedesign.co.za
22
OPTIMIZE YOUR WEBSITE WITH SEO TOOLS FOR FREE
seocheckfree.com
22
AX ELECTRICAL SERVICES | RELIABLE LONDON BASED ELECTRICIANS
axelectricalservices.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

27 thebraguru.co.za Last Updated: 4 weeks

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

Desktop

Mobile

Performance Desktop Score 60%
Best Practices Desktop Score 81%
SEO Desktop Score 92%
PWA Desktop Score 29%
Performance Mobile Score 14%
Best Practices Mobile Score 78%
SEO Mobile Score 92%
PWA Mobile Score 38%
Page Authority Authority 24%
Domain Authority Domain Authority 23%
Moz Rank 2.4/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 54 Characters
BRA FITTING SPECIALISTS IN JOHANNESBURG | THE BRA GURU
Meta Description 154 Characters
Are you looking for the perfect bra? The Bra Guru is not your average bra shop. We are your personal bra fitting specialists! Find your perfect fit today.
Effective URL 28 Characters
https://www.thebraguru.co.za
Excerpt Page content
Bra fitting specialists in Johannesburg | The Bra Guru ...
Keywords Cloud Density
bela8 book8 guru6 closed5 cape5 follow5 fitting5 call4 thebraguru4 studio4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
bela 8
book 8
guru 6
closed 5
cape 5
follow 5
fitting 5
call 4
thebraguru 4
studio 4
Google Preview Google search result preview
BRA FITTING SPECIALISTS IN JOHANNESBURG | THE BRA GURU
https://www.thebraguru.co.za
Are you looking for the perfect bra? The Bra Guru is not your average bra shop. We are your personal bra fitting specialists! Find your perfect fit to
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~255.14 KB
Code Size: ~86.89 KB
Text Size: ~168.25 KB Ratio: 65.94%

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
Speed Index 5.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Minimize main-thread work 2.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Properly size images Potential savings of 1,190 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint 3.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Server Backend Latencies 370 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
Eliminate render-blocking resources Potential savings of 710 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Serve static assets with an efficient cache policy 83 resources found
A long cache lifetime can speed up repeat visits to your page
Uses deprecated APIs 2 warnings found
Deprecated APIs will eventually be removed from the browser
Total Blocking Time 70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Network Round Trip Times 380 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 520 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid an excessive DOM size 742 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)
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
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
Time to Interactive 6.1 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint element 3,900 ms
This is the largest contentful element painted within the viewport
JavaScript execution time 0.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 27 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Avoid long main-thread tasks 6 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Use video formats for animated content Potential savings of 339 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Avoid chaining critical requests 40 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 189 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
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 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)
User Timing marks and measures 11 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Avoid enormous network payloads Total size was 4,233 KiB
Large network payloads cost users real money and are highly correlated with long load times
Cumulative Layout Shift 0.014
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid serving legacy JavaScript to modern browsers Potential savings of 22 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
Serve images in next-gen formats Potential savings of 1,881 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
First Contentful Paint 3.7 s
First Contentful Paint marks the time at which the first text or image is painted
First Meaningful Paint 3.7 s
First Meaningful Paint measures when the primary content of a page is visible
Efficiently encode images Potential savings of 326 KiB
Optimized images load faster and consume less cellular data
Avoid non-composited animations 4 animated elements found
Animations which are not composited can be janky and increase CLS

Mobile

Mobile Screenshot
Properly size images Potential savings of 580 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Total Blocking Time 1,450 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Defer offscreen images Potential savings of 83 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Avoid serving legacy JavaScript to modern browsers Potential savings of 22 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 the impact of third-party code Third-party code blocked the main thread for 520 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 images in next-gen formats Potential savings of 996 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 3.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Document uses legible font sizes 99.87% 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
Server Backend Latencies 400 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 non-composited animations 4 animated elements found
Animations which are not composited can be janky and increase CLS
Largest Contentful Paint element 11,130 ms
This is the largest contentful element painted within the viewport
Avoid enormous network payloads Total size was 3,335 KiB
Large network payloads cost users real money and are highly correlated with long load times
Reduce unused JavaScript Potential savings of 252 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Time to Interactive 16.1 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint 11.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Contentful Paint 6.7 s
First Contentful Paint marks the time at which the first text or image is painted
Network Round Trip Times 370 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
First Meaningful Paint 6.8 s
First Meaningful Paint measures when the primary content of a page is visible
Minimize main-thread work 8.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Uses deprecated APIs 2 warnings found
Deprecated APIs will eventually be removed from the browser
Avoid large layout shifts 6 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)
Max Potential First Input Delay 360 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Eliminate render-blocking resources Potential savings of 2,480 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
User Timing marks and measures 11 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Serve static assets with an efficient cache policy 83 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid chaining critical requests 52 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 initial server response time Root document took 3,230 ms
Keep the server response time for the main document short because all other requests depend on it
Use video formats for animated content Potential savings of 339 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
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
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
Cumulative Layout Shift 0.31
Cumulative Layout Shift measures the movement of visible elements within the viewport
Reduce unused CSS Potential savings of 27 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Speed Index 18.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid an excessive DOM size 739 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)
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