Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

candyretailer.com

Buy Candy Online | Fresh Candy Shipped Fast| CandyRetailer.com

Page Load Speed

10.9 sec in total

First Response

3.1 sec

Resources Loaded

7.4 sec

Page Rendered

380 ms

candyretailer.com screenshot

About Website

Visit candyretailer.com now to see the best up-to-date Candy Retailer content and also check out these interesting facts you probably never knew about candyretailer.com

Browse our large selection of candy online. Candy by the box, by the pound at CandyRetailer.com. Candy bars, chocolate candy, nostalgic candy and more.

Visit candyretailer.com

Key Findings

We analyzed Candyretailer.com page load time and found that the first response time was 3.1 sec and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

candyretailer.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

69/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value1,960 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

www.candyretailer.com

3056 ms

js

67 ms

js

100 ms

css

48 ms

font-awesome.min.css

40 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 88% of them (46 requests) were addressed to the original Candyretailer.com, 4% (2 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Candyretailer.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 151.1 kB (10%)

Content Size

1.5 MB

After Optimization

1.4 MB

In fact, the total size of Candyretailer.com main page is 1.5 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 120.3 kB

  • Original 132.5 kB
  • After minification 83.1 kB
  • After compression 12.2 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. This page needs HTML code to be minified as it can gain 49.4 kB, which is 37% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 120.3 kB or 91% of the original size.

Image Optimization

-2%

Potential reduce by 19.9 kB

  • Original 1.3 MB
  • After minification 1.2 MB

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. Candy Retailer images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 6.9 kB

  • Original 90.2 kB
  • After minification 90.2 kB
  • After compression 83.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. This website has mostly compressed JavaScripts.

CSS Optimization

-9%

Potential reduce by 4.1 kB

  • Original 44.4 kB
  • After minification 44.4 kB
  • After compression 40.3 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. Candyretailer.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 19 (40%)

Requests Now

48

After Optimization

29

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

Accessibility Review

candyretailer.com accessibility score

77

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

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.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

candyretailer.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

candyretailer.com SEO score

84

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

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/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Candyretailer.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Candyretailer.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Candy Retailer. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: