Access candywasted.com.

Report Summary

About Website

Click here to check amazing Candywasted content. Otherwise, check out these important facts you probably never knew about candywasted.com

We are a young couple with a passion for the sweeter side of life - the idea behind Candy Wasted is to make candy fun again!

Visit candywasted.com

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value4.0 s

88/100

10%

www.candywasted.com

1964 ms

wp-emoji-release.min.js

306 ms

jquery-ui.css

25 ms

cnss.css

659 ms

styles.css

748 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 65% of them (63 requests) were addressed to the original Candywasted.com, 8% (8 requests) were made to I1.wp.com and 4% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source I1.wp.com.

Content Size

1.7 MB

After Optimization

863.2 kB

In fact, the total size of Candywasted.com main page is 1.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 621.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 49.6 kB

Original 62.2 kB
After minification 60.5 kB
After compression 12.6 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 49.6 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 15.5 kB

Original 599.9 kB
After minification 584.4 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Candywasted images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 417.2 kB

Original 621.5 kB
After minification 616.8 kB
After compression 204.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 417.2 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 325.0 kB

Original 387.0 kB
After minification 318.0 kB
After compression 62.0 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Candywasted.com needs all CSS files to be minified and compressed as it can save up to 325.0 kB or 84% of the original size.

Requests Now

After Optimization

The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Candywasted. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

Document doesn't have a <title> element

High

<frame> or <iframe> elements do not have a title

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Document doesn't have a <title> element

To appear in search results, crawlers need access to your app.

High

Page is blocked from indexing

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

N/A
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Candywasted.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Candywasted.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

candywasted.com

Open Graph data is detected on the main page of Candywasted. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)