28 sec in total
2.2 sec
19 sec
6.8 sec
Welcome to krispykreme.com.ph homepage info - get ready to check Krispy Kreme best content for Philippines right away, or after learning these important things about krispykreme.com.ph
Visit krispykreme.com.phWe analyzed Krispykreme.com.ph page load time and found that the first response time was 2.2 sec and then it took 25.8 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.
krispykreme.com.ph performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value13.3 s
0/100
25%
Value13.4 s
2/100
10%
Value350 ms
73/100
30%
Value0.011
100/100
15%
Value18.6 s
3/100
10%
2177 ms
772 ms
771 ms
771 ms
1513 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 76% of them (53 requests) were addressed to the original Krispykreme.com.ph, 4% (3 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Krispykreme.com.ph.
Page size can be reduced by 5.1 MB (29%)
17.5 MB
12.4 MB
In fact, the total size of Krispykreme.com.ph main page is 17.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. 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 16.5 MB which makes up the majority of the site volume.
Potential reduce by 30.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. 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 30.1 kB or 77% of the original size.
Potential reduce by 4.4 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. Obviously, Krispy Kreme needs image optimization as it can save up to 4.4 MB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 459.5 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 459.5 kB or 61% of the original size.
Potential reduce by 185.6 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.ph needs all CSS files to be minified and compressed as it can save up to 185.6 kB or 82% of the original size.
Number of requests can be reduced by 28 (45%)
62
34
The browser has sent 62 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 19 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.krispykreme.com.ph
2177 ms
style.css
772 ms
css
771 ms
advps-style.css
771 ms
facebook-btn.css
1513 ms
lightbox.min.css
1481 ms
jquery.js
1678 ms
jquery-migrate.min.js
1324 ms
advps.frnt.script.js
1362 ms
jquery.bxslider.min.js
1361 ms
index-2.js
1570 ms
api.js
1220 ms
menu.js
1234 ms
toggle.js
1209 ms
slide-show.js
1192 ms
google-maps.js
1193 ms
facebook-script.js
1192 ms
wp-lightbox-2.min.js
1192 ms
wp-embed.min.js
1367 ms
foundation.min.css
1155 ms
normalize.css
1300 ms
single-style.css
1301 ms
2607f6
1041 ms
wp-emoji-release.min.js
1613 ms
css
106 ms
sdk.js
936 ms
analytics.js
936 ms
menu.png
1125 ms
close.png
1124 ms
facebook-icon.png
1176 ms
twitter-icon.png
1111 ms
instagram-icon.png
1175 ms
youtube-icon.png
1176 ms
pinterest-icon.png
1175 ms
google-icon.png
1176 ms
coffee.png
2419 ms
donut-bite.png
2418 ms
seal.png
2389 ms
click-coffee-new.png
2356 ms
click-donut.png
2387 ms
Ghirardelli-Chiller-Web-Asset-half.png
2419 ms
Matcha-Web-Asset-half-1.png
2487 ms
Holes-Web-Asset-half-1.png
4738 ms
round_KKF-2.png
2422 ms
round_signature-coffee-2.png
2389 ms
Beverage-round.png
2421 ms
click-social.png
2422 ms
10.png
2478 ms
arrow-yellow.png
2479 ms
bg.jpeg
1880 ms
like.php
2781 ms
collect
305 ms
EvPKapBawcLZ3hbihjhqAaCWcynf_cDxXwCLxiixG1c.ttf
201 ms
2koEo4AKFSvK4B52O_MwaonF5uFdDttMLvmWuJdhhgs.ttf
430 ms
bebas.TTF
931 ms
icomoon.woff
931 ms
2607F6_D_0.woff
930 ms
2607F6_0_0.woff
1280 ms
3Xx3V3Rdihv.css
921 ms
946 ms
widgets.js
367 ms
0sTQzbapM8j.js
853 ms
0sTQzbapM8j.js
1265 ms
load-story
1926 ms
api-twitter.php
426 ms
js
356 ms
donut-choco.png
1384 ms
button.3ccb64e61d4c01fae12cd2b0ed9b2bab.js
489 ms
json-store.php
554 ms
follow_button.f8c8d971a6ac545cf416e3c1ad4bbc65.en.html
560 ms
krispykreme.com.ph accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
krispykreme.com.ph 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
Page has valid source maps
krispykreme.com.ph SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Krispykreme.com.ph 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 Krispykreme.com.ph 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.ph
Open Graph description is not detected on the main page of Krispy Kreme. 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: