2.8 sec in total
472 ms
2 sec
339 ms
Click here to check amazing Krispy Kreme content for United States. Otherwise, check out these important facts you probably never knew about krispykreme.com
Krispy Kreme doughnuts
Visit krispykreme.comWe analyzed Krispykreme.com page load time and found that the first response time was 472 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
krispykreme.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value6.8 s
7/100
25%
Value9.1 s
13/100
10%
Value16,910 ms
0/100
30%
Value0.024
100/100
15%
Value24.7 s
0/100
10%
472 ms
40 ms
12 ms
13 ms
14 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 25% of them (21 requests) were addressed to the original Krispykreme.com, 7% (6 requests) were made to Prod-promoadmin.s3.amazonaws.com and 5% (4 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Prod-promoadmin.s3.amazonaws.com.
Page size can be reduced by 1.3 MB (35%)
3.6 MB
2.4 MB
In fact, the total size of Krispykreme.com main page is 3.6 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. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 50.5 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 50.5 kB or 71% of the original size.
Potential reduce by 201.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. Krispy Kreme images are well optimized though.
Potential reduce by 296.4 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 296.4 kB or 72% of the original size.
Potential reduce by 730.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. Krispykreme.com needs all CSS files to be minified and compressed as it can save up to 730.4 kB or 77% of the original size.
Number of requests can be reduced by 46 (66%)
70
24
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Krispy Kreme. 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 as a result speed up the page load time.
krispykreme.com
472 ms
GetResource.ashx
40 ms
modernizr-2.6.2-respond-1.1.0.min.js
12 ms
modaldialog.js
13 ms
introbox.js
14 ms
WebResource.axd
29 ms
ScriptResource.axd
30 ms
ScriptResource.axd
21 ms
2607f6
24 ms
all.js
44 ms
9d290184-dc47-4bf2-8c11-e5da31b5d6f7.jpg
612 ms
activityi;src=5109506;type=conve0;cat=krisp0;ord=3836626766715.1987
83 ms
82 ms
boxLogo.svg
162 ms
boxFront.png
80 ms
logo.svg
35 ms
coffee.png
79 ms
doughnut.png
81 ms
FreshHotNow.png
78 ms
17902793-da32-4129-8da2-587c582adb8e.png
766 ms
85dc520d-5247-4efc-b209-cf2932c63964.png
999 ms
0c871320-3e03-49d6-b4b6-d07a131ad316.png
981 ms
2607F6_0_0.woff
103 ms
81 ms
xd_arbiter.php
62 ms
xd_arbiter.php
109 ms
Pug
86 ms
2607F6_D_0.woff
24 ms
icomoon.woff
23 ms
BEBAS___-webfont.woff
12 ms
widgets.js
80 ms
KrispyEnvironmentScripts.ashx
13 ms
main.js
20 ms
jquery.tmpl-1.1.js
11 ms
jquery.min.js
40 ms
fbevents.js
18 ms
tc.min.js
142 ms
2 ms
ga.js
66 ms
ping
269 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
186 ms
4cd74a7e-5a34-48f1-a421-c167d3deba4d.jpg
912 ms
2ce559ae-7bfc-49cb-b1d4-2dd99b16c528.jpg
1310 ms
__utm.gif
22 ms
ca.html
22 ms
collect
115 ms
pixel
60 ms
Pug
56 ms
cx
68 ms
rum
55 ms
adb.gif
30 ms
1
61 ms
cs
384 ms
yahoo.ashx
238 ms
like.php
122 ms
tap.php
27 ms
pixel.gif
63 ms
32 ms
sync
60 ms
sd
24 ms
cm
42 ms
rum
49 ms
360947.gif
39 ms
demconf.jpg
39 ms
cm
46 ms
xrefid.xgi
36 ms
cx
41 ms
mapuid
39 ms
pixel
39 ms
cm
16 ms
cm
13 ms
cx
27 ms
xrefid.xgi
26 ms
362378.gif
25 ms
7 ms
ga-audiences
47 ms
lr.gif
18 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
40 ms
vpc6VNjRPXV.js
70 ms
LVx-xkvaJ0b.png
73 ms
pixel
36 ms
pixel.gif
535 ms
adex.ashx
169 ms
jot
110 ms
1
54 ms
krispykreme.com accessibility score
krispykreme.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
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
krispykreme.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Krispykreme.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 Krispykreme.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.
krispykreme.com
Open Graph data is detected on the main page of Krispy Kreme. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: