Your Website Score is

Latest Sites

19
CARKELAI
carkelai.com
9
YOUTUBE
youtube.com
26
SERGIDEV
sergidev.me
1
-
w.com
2
YOUTUBE
youtu.be
2
ABOUT | MUSIC.COM
music.com
19
SOUNDSNAP | PREMIUM AND FREE SOUND EFFECTS - SFX DOWNLOADS
soundsnap.com

Top Technologies

Google Font API
Font Scripts
Nginx
Web Servers
CloudFlare
CDN
Varnish
Cache Tools
Google Tag Manager
Tag Managers
Twitter Bootstrap
Web Frameworks
Font Awesome
Font Scripts
Apache
Web Servers

3 candycrushfitness.uk Last Updated: 2 months

Success 32% of passed verification steps
Warning 30% of total warning
Errors 38% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 94%
Best Practices Desktop Score 81%
SEO Desktop Score 82%
PWA Desktop Score 71%
Performance Mobile Score 73%
Best Practices Mobile Score 81%
SEO Mobile Score 85%
PWA Mobile Score 75%
Page Authority Authority 5%
Domain Authority Domain Authority 1%
Moz Rank 0.5/10
Bounce Rate Rate 0%
Title Tag 0 Characters
NO DATA
Meta Description 0 Characters
NO DATA
Effective URL 27 Characters
http://candycrushfitness.uk
Excerpt Page content
This site requires Javascript to work, please enable Javascript in your browser or use a browser with Javascript support
Keywords Cloud Density
javascript3 browser2 support1 enable1 work1 requires1 site1 please1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
javascript 3
browser 2
support 1
enable 1
work 1
requires 1
site 1
please 1
Google Preview Your look like this in google search result
candycrushfitness.uk
http://candycrushfitness.uk
This site requires Javascript to work, please enable Javascript in your browser or use a browser with Javascript support
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~831 B
Code Size: ~140 B
Text Size: ~691 B Ratio: 83.15%

Social Data

Estimation Traffic and Earnings

8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Initial server response time was short Root document took 110 ms
Keep the server response time for the main document short because all other requests depend on it
Eliminate render-blocking resources Potential savings of 370 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minimize third-party usage Third-party code blocked the main thread for 50 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 30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Network Round Trip Times 50 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
Avoids enormous network payloads Total size was 1,888 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Meaningful Paint 1.1 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid large layout shifts 1 layout shift 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 1.1 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Does not use HTTPS 5 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
Avoid non-composited animations 4 animated elements found
Animations which are not composited can be janky and increase CLS
Properly size images Potential savings of 1,362 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
JavaScript execution time 0.0 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 8 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
Max Potential First Input Delay 70 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint element 1,450 ms
This is the largest contentful element painted within the viewport
Server Backend Latencies 160 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
Reduce unused CSS Potential savings of 36 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
Reduce unused JavaScript Potential savings of 74 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted
Avoids an excessive DOM size 64 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)
Cumulative Layout Shift 0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint 1.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Time to Interactive 1.1 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Minimizes main-thread work 0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts 3 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)

Mobile

Mobile Screenshot
Avoid large layout shifts 1 layout shift 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)
Server Backend Latencies 140 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
Reduce unused CSS Potential savings of 36 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Network Round Trip Times 60 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
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
Avoids an excessive DOM size 64 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)
Document uses legible font sizes 73.03% 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
Avoids enormous network payloads Total size was 1,888 KiB
Large network payloads cost users real money and are highly correlated with long load times
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Properly size images Potential savings of 1,334 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
First Meaningful Paint 2.9 s
First Meaningful Paint measures when the primary content of a page is visible
Time to Interactive 3.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
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
Avoid large layout shifts 2 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)
Reduce unused JavaScript Potential savings of 74 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Minimize third-party usage Third-party code blocked the main thread for 0 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
Speed Index 2.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Minimizes main-thread work 0.9 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 80 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Initial server response time was short Root document took 130 ms
Keep the server response time for the main document short because all other requests depend on it
Eliminate render-blocking resources Potential savings of 1,350 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid chaining critical requests 8 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 element 6,120 ms
This is the largest contentful element painted within the viewport
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
First Contentful Paint 2.9 s
First Contentful Paint marks the time at which the first text or image is painted
Tap targets are sized appropriately 100% 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
Does not use HTTPS 5 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
Largest Contentful Paint 6.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Warning! Your title is not optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Warning! Your website is not SSL secured (HTTPS).
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
candycrushfitness.co Available
candycrushfitness.us Available
candycrushfitness.com Available
candycrushfitness.org Available
candycrushfitness.net Available
cndycrushfitness.uk Available
dandycrushfitness.uk Available
randycrushfitness.uk Available

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Server: nginx
Date: Sun, 14 Apr 2024 22:05:57 GMT
Content-Type: text/html
Content-Length: 831
Connection: keep-alive
Expires: Thu, 01 Jan 1970 00:00:01 GMT
Cache-Control: no-cache