Your Website Score is





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

1 siteconcept.xyz Last Updated: 2 months

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

Desktop

Mobile

Performance Desktop Score 95%
Best Practices Desktop Score 82%
SEO Desktop Score 73%
Performance Mobile Score 64%
Best Practices Mobile Score 83%
SEO Mobile Score 73%
Page Authority Authority 8%
Domain Authority Domain Authority 1%
Moz Rank 0.8/10
Bounce Rate Rate 0%
Title Tag 0 Characters
NO DATA
Meta Description 0 Characters
NO DATA
Effective URL 22 Characters
http://siteconcept.xyz
Google Preview Google search result preview
siteconcept.xyz
http://siteconcept.xyz
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~114 B
Code Size: ~58 B
Text Size: ~56 B Ratio: 49.12%

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
Time to Interactive 1.0 s
Time to Interactive is the amount of time it takes for the page to become fully 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
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Server Backend Latencies 10 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 long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Contentful Paint 0.6 s
First Contentful Paint marks the time at which the first text or image is painted
Minimizes main-thread work 0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Does not use HTTPS 2 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
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
Largest Contentful Paint 1.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Initial server response time was short Root document took 20 ms
Keep the server response time for the main document short because all other requests depend on it
Reduce unused JavaScript Potential savings of 184 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoids enormous network payloads Total size was 376 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve static assets with an efficient cache policy 5 resources found
A long cache lifetime can speed up repeat visits to your page
Eliminate render-blocking resources Potential savings of 300 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Cumulative Layout Shift 0.073
Cumulative Layout Shift measures the movement of visible elements within the viewport
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
JavaScript execution time 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint element 1,280 ms
This is the largest contentful element painted within the viewport
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated
robots.txt is not valid 1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Avoid an excessive DOM size 57 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 multiple page redirects Potential savings of 200 ms
Redirects introduce additional delays before the page can be loaded
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)

Mobile

Mobile Screenshot
Largest Contentful Paint 5.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Meaningful Paint 3.0 s
First Meaningful Paint measures when the primary content of a page is visible
Reduce the impact of third-party code Third-party code blocked the main thread for 360 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
Reduce unused JavaScript Potential savings of 184 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Serve static assets with an efficient cache policy 5 resources found
A long cache lifetime can speed up repeat visits to your page
Document uses legible font sizes 100% 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
Does not use HTTPS 2 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
Cumulative Layout Shift 0.072
Cumulative Layout Shift measures the movement of visible elements within the viewport
Initial server response time was short Root document took 20 ms
Keep the server response time for the main document short because all other requests depend on it
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
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)
First Contentful Paint 2.5 s
First Contentful Paint marks the time at which the first text or image is painted
Avoids enormous network payloads Total size was 375 KiB
Large network payloads cost users real money and are highly correlated with long load times
robots.txt is not valid 1 error found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Max Potential First Input Delay 380 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Total Blocking Time 470 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Time to Interactive 5.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Minimizes main-thread work 1.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 10 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 21 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)
Largest Contentful Paint element 5,200 ms
This is the largest contentful element painted within the viewport
JavaScript execution time 1.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
Speed Index 3.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Eliminate render-blocking resources Potential savings of 1,270 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid multiple page redirects Potential savings of 750 ms
Redirects introduce additional delays before the page can be loaded

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