1.9 sec in total
98 ms
1.2 sec
649 ms
Visit jellybelly.com now to see the best up-to-date Jelly Belly content for United States and also check out these interesting facts you probably never knew about jellybelly.com
Official Online Retailer of Gourmet Jelly Belly Candies and Confections. Jelly Belly Candy Company, over 100 years of Candy-Making Expertise
Visit jellybelly.comWe analyzed Jellybelly.com page load time and found that the first response time was 98 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
jellybelly.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value4.4 s
39/100
25%
Value13.2 s
2/100
10%
Value880 ms
33/100
30%
Value0.426
23/100
15%
Value22.4 s
1/100
10%
98 ms
552 ms
19 ms
12 ms
20 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 6% of them (5 requests) were addressed to the original Jellybelly.com, 49% (44 requests) were made to Cdn-us-cf.yottaa.net and 29% (26 requests) were made to C9027ff03ac6013382460a3ba3fac80a.yottaa.net. The less responsive or slowest element that took the longest time to load (552 ms) belongs to the original domain Jellybelly.com.
Page size can be reduced by 2.0 MB (37%)
5.3 MB
3.3 MB
In fact, the total size of Jellybelly.com main page is 5.3 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. 75% 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.0 MB which makes up the majority of the site volume.
Potential reduce by 732.0 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 732.0 kB or 77% of the original size.
Potential reduce by 41.0 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. Jelly Belly images are well optimized though.
Potential reduce by 29.6 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 29.6 kB or 63% of the original size.
Potential reduce by 1.2 MB
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. Jellybelly.com needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 87% of the original size.
Number of requests can be reduced by 6 (10%)
60
54
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jelly Belly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
jellybelly.com
98 ms
www.jellybelly.com
552 ms
mobile-logo.png
19 ms
font-awesome.min.css.Y$DU.css
12 ms
storefront.less
20 ms
modernizr.respond.js
55 ms
easyXDM.min.js
58 ms
layout.css.Y$DU.css
11 ms
jquery.min.js
62 ms
Brand_heroimage.jpg
13 ms
wisconsin_heroimage.jpg
13 ms
Retail_heroimage.jpg
13 ms
eGiftCards_heroimage.jpg
55 ms
slide.aspx
58 ms
slide.aspx
58 ms
slide.aspx
60 ms
slide.aspx
58 ms
mainBG2.jpg
3 ms
search_icon_blue.png
20 ms
usMap.png
15 ms
storefront.less
60 ms
organic_category_logo.png
76 ms
slide.aspx
59 ms
require-min.js
37 ms
_mzblank.gif
159 ms
footer-logo.png
37 ms
fontawesome-webfont.woff
36 ms
bargain_mega_menu_banner_new.jpg
41 ms
cycling_team_mm.jpg
44 ms
maxxis.jpg
41 ms
organic_category_logo.png
105 ms
0a067b49-b518-484c-9c66-b8300b00e793
41 ms
pre_icons.png
35 ms
3160fd96-6270-4fe0-ab34-fa341977d3b7
60 ms
324bbed7-c769-4a5a-9270-6a7a285a11be
32 ms
4e3b6374-5329-4081-b7ee-a6d036047229
102 ms
7e05fd40-05a7-495f-92dd-d065f56e1639
101 ms
b92f3956-aa1c-43f5-87a0-f4c0760170ef
63 ms
b5dd7f58-46fa-495c-bb03-078e0c3e8a2c
60 ms
2d9c14b6-9a97-46c5-a1be-fa137942902c
67 ms
850f3209-0cf8-4a3c-82cb-6ad484bc01e2
117 ms
1097fc88-0ca7-4b94-bf3f-d3ee13224fa2
182 ms
4c3ca5bb-94ee-4f02-aea0-b768be1681b7
167 ms
c9128f34-a263-4580-8d8a-75a29297d748
223 ms
eaba90c2-7fde-4db3-a4d1-01403e3fb276
179 ms
7d6d40de-e79b-4437-aee8-07948210db3a
218 ms
2d2261db-967a-4217-99d8-a80b5f44e02c
264 ms
6ca22e77-4cac-42e1-9546-ccadd5426c9b
272 ms
a7a2ef13-bdd1-4cf0-b4fd-bd59991fab1c
285 ms
278e91d8-3a76-4db1-b696-2b9b748e1a3d
283 ms
5512501e-c351-46bd-bdda-158b02255579
282 ms
3045c058-fe02-4456-876a-5a0a24a44ead
279 ms
5f8b686d-abd0-45c6-bf97-c762d185df78
336 ms
18999b2f-9f69-4b44-b7c4-55b65e332076
329 ms
dae1b79e-3bf4-4f1c-94c7-b501d92024b1
404 ms
38682414-ff14-4d0d-a751-1a8ff5091e7f
405 ms
15f15847-e7ea-48cf-8957-4e763badae38
403 ms
10dc6f86-e43d-4a81-9e41-9db566731fa4
407 ms
myJB.jpg
333 ms
find-store.png
26 ms
preHead_icons.png
25 ms
jblogo-new.png
27 ms
mobile-icons.png
26 ms
organic_category_logo.png
6 ms
3160fd96-6270-4fe0-ab34-fa341977d3b7
3 ms
b5dd7f58-46fa-495c-bb03-078e0c3e8a2c
4 ms
b92f3956-aa1c-43f5-87a0-f4c0760170ef
3 ms
2d9c14b6-9a97-46c5-a1be-fa137942902c
2 ms
7e05fd40-05a7-495f-92dd-d065f56e1639
2 ms
4e3b6374-5329-4081-b7ee-a6d036047229
3 ms
850f3209-0cf8-4a3c-82cb-6ad484bc01e2
3 ms
4c3ca5bb-94ee-4f02-aea0-b768be1681b7
2 ms
810153c0-7fdd-430a-b04a-88bb26b17328
3 ms
eaba90c2-7fde-4db3-a4d1-01403e3fb276
3 ms
1097fc88-0ca7-4b94-bf3f-d3ee13224fa2
3 ms
7d6d40de-e79b-4437-aee8-07948210db3a
4 ms
c9128f34-a263-4580-8d8a-75a29297d748
2 ms
2d2261db-967a-4217-99d8-a80b5f44e02c
3 ms
6ca22e77-4cac-42e1-9546-ccadd5426c9b
3 ms
3045c058-fe02-4456-876a-5a0a24a44ead
5 ms
5512501e-c351-46bd-bdda-158b02255579
5 ms
278e91d8-3a76-4db1-b696-2b9b748e1a3d
5 ms
a7a2ef13-bdd1-4cf0-b4fd-bd59991fab1c
4 ms
18999b2f-9f69-4b44-b7c4-55b65e332076
2 ms
5f8b686d-abd0-45c6-bf97-c762d185df78
3 ms
15f15847-e7ea-48cf-8957-4e763badae38
4 ms
dae1b79e-3bf4-4f1c-94c7-b501d92024b1
4 ms
38682414-ff14-4d0d-a751-1a8ff5091e7f
4 ms
10dc6f86-e43d-4a81-9e41-9db566731fa4
3 ms
jellybelly.com accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
jellybelly.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
jellybelly.com SEO score
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jellybelly.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Jellybelly.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.
jellybelly.com
Open Graph description is not detected on the main page of Jelly Belly. 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: