Tools & Wizards About Us
candy.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

candy.com

Home - Candy

Page Load Speed

78.6 sec in total

First Response

1.4 sec

Resources Loaded

23.3 sec

Page Rendered

54 sec

candy.com screenshot

About Website

Click here to check amazing Candy content for United States. Otherwise, check out these important facts you probably never knew about candy.com

Candy Digital powers the world's largest fan communities. Discover, collect, and unlock exclusive experiences from MLB, DC, and more.

Visit candy.com

Key Findings

We analyzed Candy.com page load time and found that the first response time was 1.4 sec and then it took 77.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

candy.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value20.8 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value9,890 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

www.candy.com

1361 ms

css

117 ms

rewardpoints.css

351 ms

rewardpoints_new.css

287 ms

transactionpoint.css

351 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 9% of them (6 requests) were addressed to the original Candy.com, 60% (39 requests) were made to D3vuec9wjh8whu.cloudfront.net and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (8.2 sec) relates to the external source Script.hotjar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.3 MB (38%)

Content Size

6.1 MB

After Optimization

3.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Candy.com main page is 6.1 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 106.7 kB

  • Original 119.8 kB
  • After minification 76.2 kB
  • After compression 13.1 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 43.6 kB, which is 36% 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 106.7 kB or 89% of the original size.

Image Optimization

-5%

Potential reduce by 163.2 kB

  • Original 3.3 MB
  • After minification 3.1 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 images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 1.3 MB

  • Original 1.9 MB
  • After minification 1.8 MB
  • After compression 598.9 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 1.3 MB or 68% of the original size.

CSS Optimization

-90%

Potential reduce by 792.0 kB

  • Original 884.4 kB
  • After minification 709.0 kB
  • After compression 92.4 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. Candy.com needs all CSS files to be minified and compressed as it can save up to 792.0 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (39%)

Requests Now

59

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.candy.com

www.candy.com

1361 ms

css

css

117 ms

rewardpoints.css

rewardpoints.css

351 ms

rewardpoints_new.css

rewardpoints_new.css

287 ms

transactionpoint.css

transactionpoint.css

351 ms

styles.css

styles.css

917 ms

main.css

main.css

323 ms

jquery-1.11.2.min.js

jquery-1.11.2.min.js

1110 ms

giftvoucher.js

giftvoucher.js

1110 ms

modernizr.custom.13979.js

modernizr.custom.13979.js

1138 ms

vendor-aa8b829c.js

vendor-aa8b829c.js

1076 ms

plugins-50b1b7d2.js

plugins-50b1b7d2.js

1075 ms

main-7dfcc77c.js

main-7dfcc77c.js

1074 ms

async_survey

async_survey

1075 ms

autocomplete-v2.css

autocomplete-v2.css

1041 ms

searchspring-autocomplete.min.js

searchspring-autocomplete.min.js

1041 ms

css

css

878 ms

background-texture.png

background-texture.png

1395 ms

gtm.js

gtm.js

87 ms

hotjar-116461.js

hotjar-116461.js

506 ms

analytics.js

analytics.js

2010 ms

candy-by-pound.jpg

candy-by-pound.jpg

453 ms

c_by-gift.jpg

c_by-gift.jpg

1795 ms

allnatural-banner.jpg

allnatural-banner.jpg

157 ms

patriotic-candy-navigation.jpg

patriotic-candy-navigation.jpg

156 ms

SPRING-CANDY.jpg

SPRING-CANDY.jpg

1660 ms

Candy_Home_1800x785-Fall.jpg

Candy_Home_1800x785-Fall.jpg

1588 ms

candyByColor.jpg

candyByColor.jpg

1590 ms

wedding.jpg

wedding.jpg

1590 ms

giantCandy.jpg

giantCandy.jpg

1589 ms

Candy.com_Snack_Boxes.jpg

Candy.com_Snack_Boxes.jpg

1589 ms

KISSES-Gifts-Under-50.jpg

KISSES-Gifts-Under-50.jpg

1662 ms

corporate-candy.jpg

corporate-candy.jpg

1755 ms

under-20.jpg

under-20.jpg

1753 ms

candyByColor_1.jpg

candyByColor_1.jpg

1660 ms

spring.jpg

spring.jpg

1754 ms

206-00001-assorted-gummi-bears-640x402.jpg

206-00001-assorted-gummi-bears-640x402.jpg

1754 ms

209-00320-welch-mixed-fruits-snacks-66ct-box.jpg

209-00320-welch-mixed-fruits-snacks-66ct-box.jpg

1823 ms

251-00001-worlds-largest-gummy-bear-5lb_1.jpg

251-00001-worlds-largest-gummy-bear-5lb_1.jpg

1823 ms

262-00015-rock-candy-sticks.jpg

262-00015-rock-candy-sticks.jpg

1745 ms

71-10006-worlds-largest-gummy-worm-bluerasp-cherry_1.jpg

71-10006-worlds-largest-gummy-worm-bluerasp-cherry_1.jpg

1744 ms

logo-jelly-belly.png

logo-jelly-belly.png

1744 ms

logo-pez-candy.png

logo-pez-candy.png

1745 ms

logo-star-burst.png

logo-star-burst.png

1944 ms

logo-wonka.png

logo-wonka.png

1945 ms

logo-reeses.png

logo-reeses.png

1944 ms

home-about-us.jpg

home-about-us.jpg

1944 ms

by-gift-baskets.jpg

by-gift-baskets.jpg

1578 ms

tag.js

tag.js

8163 ms

bat.js

bat.js

1620 ms

prompt_embed_static.js

prompt_embed_static.js

2695 ms

modules-f524bccd859bfc7e394e1123f7f90405.js

modules-f524bccd859bfc7e394e1123f7f90405.js

8211 ms

rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html

rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html

8206 ms

header-wave.png

header-wave.png

6874 ms

sprites-69c6e870.svg

sprites-69c6e870.svg

2388 ms

color-texture.png

color-texture.png

6777 ms

search.jpg

search.jpg

6873 ms

sprites-273fd9b9.png

sprites-273fd9b9.png

798 ms

conversion_async.js

conversion_async.js

858 ms

js

js

5634 ms

q5TOjIw4CenPw6C-TW06FkYcuY_p1FpnGh_-AVRTy68.ttf

q5TOjIw4CenPw6C-TW06FkYcuY_p1FpnGh_-AVRTy68.ttf

5544 ms

Z-Q1hzbY8uAo3TpTyPFMXStgOkza8-IgufpcxDXwA4k.ttf

Z-Q1hzbY8uAo3TpTyPFMXStgOkza8-IgufpcxDXwA4k.ttf

5545 ms

q5TOjIw4CenPw6C-TW06FmXsbhz3CPIl2p9zz1-595g.ttf

q5TOjIw4CenPw6C-TW06FmXsbhz3CPIl2p9zz1-595g.ttf

5546 ms

q5TOjIw4CenPw6C-TW06FqEIpwaexIb52HBYsHbHBeA.ttf

q5TOjIw4CenPw6C-TW06FqEIpwaexIb52HBYsHbHBeA.ttf

5545 ms

Eh9ZVPLDFF2xhCIl_We4NA.ttf

Eh9ZVPLDFF2xhCIl_We4NA.ttf

5545 ms

Accessibility Review

candy.com accessibility score

94

Accessibility Issues

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.

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

Links do not have a discernible name

Best Practices

candy.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Browser errors were logged to the console

SEO Factors

candy.com SEO score

80

Search Engine Optimization Advices

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Candy.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Candy.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

candy.com

Open Graph description is not detected on the main page of Candy. 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: