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
26
BEST WEB HOSTING COMPANY | CHEAP WEB HOSTING SERVICES
visualwebtechnologies.com
26
503 SERVICE UNAVAILABLE
blimeysolutions.com
26
503 SERVICE UNAVAILABLE
tropojaconstructionltd.co.uk
26
FREEFORMĀ® TENTS | STRETCH TENTS FOR SALE
freeformtents.com
26
ELSONY WASTE REMOVAL | AFFORDABLE WASTE & RUBBISH COLLECTION & REMOVAL IN N11, N12 & SURROUNDING AREAS
elsonywaste.co.uk

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

27 thebraguru.co.za Last Updated: 3 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 90%
Best Practices Desktop Score 100%
SEO Desktop Score 100%
Performance Mobile Score 16%
Best Practices Mobile Score 96%
SEO Mobile Score 100%
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
book10 bela8 thebraguru6 studio6 guru6 call6 cape5 follow5 fitting5 closed5
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
book 10
bela 8
thebraguru 6
studio 6
guru 6
call 6
cape 5
follow 5
fitting 5
closed 5
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: ~265.95 KB
Code Size: ~87.43 KB
Text Size: ~178.52 KB Ratio: 67.13%

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
Properly size images Potential savings of 1,395 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Efficiently encode images Potential savings of 326 KiB
Optimized images load faster and consume less cellular data
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
Serve static assets with an efficient cache policy 83 resources found
A long cache lifetime can speed up repeat visits to your page
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
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Total Blocking Time 50 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 767 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 unused JavaScript Potential savings of 267 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
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,560 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid large layout shifts 15 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 1.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Eliminate render-blocking resources Potential savings of 160 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Max Potential First Input Delay 80 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
JavaScript execution time 0.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive 1.9 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
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
Speed Index 3.2 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid non-composited animations 5 animated elements found
Animations which are not composited can be janky and increase CLS
Serve images in next-gen formats Potential savings of 2,048 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Reduce unused CSS Potential savings of 26 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 4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minimizes main-thread work 1.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 110 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
Minimize third-party usage Third-party code blocked the main thread for 20 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
Largest Contentful Paint element 1,020 ms
This is the largest contentful element painted within the viewport
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
Cumulative Layout Shift 0.015
Cumulative Layout Shift measures the movement of visible elements within the viewport

Mobile

Mobile Screenshot
Avoid non-composited animations 5 animated elements found
Animations which are not composited can be janky and increase CLS
Serve images in next-gen formats Potential savings of 1,522 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid long main-thread tasks 14 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoid an excessive DOM size 764 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 39 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Largest Contentful Paint 8.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Largest Contentful Paint element 8,520 ms
This is the largest contentful element painted within the viewport
Network Round Trip Times 40 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
Avoid chaining critical requests 51 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
Total Blocking Time 1,290 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minimize main-thread work 7.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Reduce JavaScript execution time 3.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
Max Potential First Input Delay 350 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Serve static assets with an efficient cache policy 83 resources found
A long cache lifetime can speed up repeat visits to your page
Reduce unused JavaScript Potential savings of 265 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Reduce initial server response time Root document took 2,720 ms
Keep the server response time for the main document short because all other requests depend on it
Reduce the impact of third-party code Third-party code blocked the main thread for 440 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 10.9 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Document uses legible font sizes 99.86% 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
Cumulative Layout Shift 0.346
Cumulative Layout Shift measures the movement of visible elements within the viewport
Properly size images Potential savings of 769 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Reduce unused CSS Potential savings of 26 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Server Backend Latencies 110 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 enormous network payloads Total size was 3,950 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Meaningful Paint 4.2 s
First Meaningful Paint measures when the primary content of a page is visible
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 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
Avoid large layout shifts 15 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)
Speed Index 13.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources Potential savings of 1,950 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Contentful Paint 4.2 s
First Contentful Paint marks the time at which the first text or image is painted

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