16 sec in total
1.7 sec
13 sec
1.3 sec
Visit krispykremesa.com.au now to see the best up-to-date Krispy Kreme Sa content and also check out these interesting facts you probably never knew about krispykremesa.com.au
Visit krispykremesa.com.auWe analyzed Krispykremesa.com.au page load time and found that the first response time was 1.7 sec and then it took 14.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
krispykremesa.com.au performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value7.3 s
4/100
25%
Value15.4 s
0/100
10%
Value4,100 ms
1/100
30%
Value0.001
100/100
15%
Value19.5 s
2/100
10%
1712 ms
19 ms
1156 ms
13 ms
1154 ms
Our browser made a total of 176 requests to load all elements on the main page. We found that 91% of them (161 requests) were addressed to the original Krispykremesa.com.au, 2% (4 requests) were made to Google-analytics.com and 2% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (8 sec) belongs to the original domain Krispykremesa.com.au.
Page size can be reduced by 335.7 kB (8%)
4.3 MB
3.9 MB
In fact, the total size of Krispykremesa.com.au main page is 4.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.8 MB which makes up the majority of the site volume.
Potential reduce by 300.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 300.5 kB or 84% of the original size.
Potential reduce by 35.1 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 Sa images are well optimized though.
Potential reduce by 106 B
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.
Number of requests can be reduced by 120 (74%)
162
42
The browser has sent 162 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Krispy Kreme Sa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 82 to 1 for JavaScripts and from 40 to 1 for CSS and as a result speed up the page load time.
krispykremesa.com.au
1712 ms
shop.css
19 ms
main.min.css
1156 ms
sbi-styles.min.css
13 ms
extendify-utilities.css
1154 ms
extension.min.css
24 ms
stores.min.css
690 ms
woocommerce-layout-grid.min.css
21 ms
woocommerce-grid.min.css
32 ms
wordpress-store-locator-public.css
36 ms
bootstrap.min.css
57 ms
all.min.css
49 ms
wordpress-store-locator-custom.css
63 ms
mnm-frontend.css
66 ms
astra-addon-659db95f6dae39-56528089.css
74 ms
elementor-icons.min.css
13 ms
frontend-lite.min.css
18 ms
swiper.min.css
26 ms
post-26071.css
28 ms
slick-carousal.css
33 ms
all.css
37 ms
solid.min.css
49 ms
frontend-lite.min.css
49 ms
global.css
59 ms
post-26125.css
60 ms
post-26091.css
68 ms
post-26087.css
67 ms
frontend.css
77 ms
style.css
75 ms
fontawesome.min.css
88 ms
brands.min.css
91 ms
jquery.min.js
99 ms
jquery-migrate.min.js
101 ms
wp-polyfill-inert.min.js
108 ms
regenerator-runtime.min.js
121 ms
wp-polyfill.min.js
147 ms
hooks.min.js
137 ms
w.js
17 ms
frontend.js
147 ms
extension.min.js
156 ms
jquery.blockUI.min.js
160 ms
add-to-cart.min.js
166 ms
js.cookie.min.js
170 ms
woocommerce.min.js
176 ms
core.min.js
178 ms
slick.js
196 ms
custom-tm.js
192 ms
js
63 ms
widget-theme-elements.min.css
174 ms
widget-icon-list.min.css
180 ms
widget-woocommerce.min.css
187 ms
widget-nav-menu.min.css
188 ms
widget-animated-headline.min.css
188 ms
widget-posts.min.css
10 ms
wc-blocks.css
17 ms
post-26078.css
17 ms
animations.min.css
1013 ms
frontend.min.js
26 ms
add-to-cart-quantity-btn.min.js
24 ms
sourcebuster.min.js
31 ms
order-attribution.min.js
35 ms
react.min.js
41 ms
deprecated.min.js
44 ms
dom.min.js
50 ms
react-dom.min.js
58 ms
escape-html.min.js
65 ms
element.min.js
70 ms
is-shallow-equal.min.js
72 ms
i18n.min.js
80 ms
keycodes.min.js
81 ms
priority-queue.min.js
88 ms
compose.min.js
98 ms
private-apis.min.js
95 ms
redux-routine.min.js
107 ms
data.min.js
109 ms
lodash.min.js
120 ms
wc-blocks-registry.js
119 ms
url.min.js
129 ms
api-fetch.min.js
135 ms
wc-settings.js
138 ms
data-controls.min.js
147 ms
html-entities.min.js
146 ms
notices.min.js
155 ms
wc-blocks-middleware.js
158 ms
wc-blocks-data.js
166 ms
dom-ready.min.js
169 ms
js
70 ms
a11y.min.js
170 ms
primitives.min.js
166 ms
warning.min.js
174 ms
blocks-components.js
175 ms
blocks-checkout.js
183 ms
order-attribution-blocks.min.js
175 ms
imagesloaded.min.js
180 ms
jquery.flexslider.min.js
176 ms
astra-addon-659db95f6df1a4-60894424.js
187 ms
single-product-ajax-cart.min.js
174 ms
ajax-add-to-cart.js
175 ms
frontend.js
946 ms
bootstrap.min.js
176 ms
wordpress-store-locator-public-single.js
175 ms
wordpress-store-locator-public.js
178 ms
cart-fragments.min.js
176 ms
jquery.smartmenus.min.js
180 ms
sbi-scripts.min.js
1788 ms
underscore.min.js
180 ms
wp-util.min.js
179 ms
add-to-cart-variation.min.js
193 ms
webpack-pro.runtime.min.js
191 ms
webpack.runtime.min.js
199 ms
frontend-modules.min.js
199 ms
frontend.min.js
205 ms
waypoints.min.js
210 ms
frontend.min.js
212 ms
elements-handlers.min.js
222 ms
lazyload.min.js
220 ms
g.gif
276 ms
analytics.js
398 ms
fbevents.js
394 ms
events.js
434 ms
sbi-sprite.png
804 ms
dots.svg
293 ms
Asset-24.svg
824 ms
yellow-donut3.svg
818 ms
brandon_text_regular-webfont.woff
1021 ms
brandon_text_medium-webfont.woff
999 ms
brandon_text_bold-webfont.woff
1549 ms
brandontext-black-webfont.woff
1588 ms
eicons.woff
1989 ms
2cd42a885fe05ec9b61112419ef2e69d.woff
1797 ms
fa-brands-400.woff
2128 ms
fa-brands-400.woff
186 ms
fa-solid-900.woff
2409 ms
fa-solid-900.woff
4506 ms
fa-solid-900.woff
214 ms
fa-regular-400.woff
214 ms
ec.js
8 ms
collect
22 ms
krispykremesa.com.au
2320 ms
collect
10 ms
final-logo.svg
878 ms
hot-now-red.svg
1811 ms
logo.svg
1731 ms
order-now.svg
1890 ms
Krispy-Kreme-Online-Gift-Boxes-NOV-2023-KK-Website-Banner-1980x890px-FINAL.jpg
3643 ms
Krispy-Kreme-Website-Updated-Banner-1980x890-Hot-light-FINAL.png
4325 ms
Krispy-Kreme-Website-Updated-Banner-1980x890-Custom-FINAL.png
4591 ms
Krispy-Kreme-Online-Gift-Boxes-NOV-2023-KK-Mobile-Web-Banner-1800x3000px-FINAL-scaled.jpg
3821 ms
Krispy-Kreme-Website-Updated-Mobile-Web-Banner-1800x300px-FINAL-Hot-Light.png
5302 ms
Krispy-Kreme-Website-Updated-Mobile-Web-Banner-1800x300px-FINAL-Custom.png
6551 ms
glazed_1.png
4851 ms
Sprinkles.png
5228 ms
strawberry-truffle.png
5742 ms
candy-cloud.png
6011 ms
glazed-orig.svg
7206 ms
home-of.svg
5236 ms
Asset-25.svg
5244 ms
6-Pack-Original-Glazed-e1612157363715.jpg
6164 ms
Original-Glazed-Dozen.png
6670 ms
gifting.png
6897 ms
Doughnut-Decorating.png
6576 ms
3-Tired-Stand_with-doughnuts.png
7772 ms
friends-image.jpg
7897 ms
custom-orders.jpg
7930 ms
Krispy-Kreme-Doughnut-Decorating-Social-Website-Tile-570x395-1-433x300.png
8019 ms
collect
26 ms
js
67 ms
placeholder.png
7503 ms
2enjoy.svg
7755 ms
2kk-logo.svg
7662 ms
ubereats-button-970x323.png
8012 ms
main.js
7223 ms
doordash-button-970x323.png
7960 ms
menulog-button-970x323.png
7256 ms
fa-solid-900.ttf
5675 ms
woocommerce-smallscreen-grid.min.css
10 ms
krispykremesa.com.au 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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
krispykremesa.com.au best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
krispykremesa.com.au SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Krispykremesa.com.au 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 Krispykremesa.com.au 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.
krispykremesa.com.au
Open Graph description is not detected on the main page of Krispy Kreme Sa. 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: