Tools & Wizards About Us

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

staging.krispykreme.com.au

Krispy Kreme - Famous Original Glazed Doughnuts - Australia

Page Load Speed

5.1 sec in total

First Response

619 ms

Resources Loaded

3.7 sec

Page Rendered

743 ms

About Website

Visit staging.krispykreme.com.au now to see the best up-to-date Staging Krispy Kreme content for Australia and also check out these interesting facts you probably never knew about staging.krispykreme.com.au

Krispy Kreme Australia, famous Original Glazed Doughnuts and barista crafted coffee fresh from our stores in NSW, VIC, QLD and WA or online doughnut delivery to your door.

Visit staging.krispykreme.com.au

Key Findings

We analyzed Staging.krispykreme.com.au page load time and found that the first response time was 619 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

staging.krispykreme.com.au performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value18.6 s

0/100

25%

SI (Speed Index)

Value14.4 s

1/100

10%

TBT (Total Blocking Time)

Value3,500 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value33.5 s

0/100

10%

Network Requests Diagram

staging.krispykreme.com.au

619 ms

calendar.min.css

39 ms

styles-m.min.css

46 ms

owl.carousel.min.css

33 ms

leaflet.min.css

166 ms

Our browser made a total of 192 requests to load all elements on the main page. We found that 94% of them (181 requests) were addressed to the original Staging.krispykreme.com.au, 1% (2 requests) were made to Fonts.googleapis.com and 1% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Staging.krispykreme.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.4 MB (48%)

Content Size

4.9 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Staging.krispykreme.com.au main page is 4.9 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. 80% 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. CSS take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 195.3 kB

  • Original 238.1 kB
  • After minification 231.2 kB
  • After compression 42.8 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 195.3 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 16 B

  • Original 1.7 MB
  • After minification 1.7 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. Staging Krispy Kreme images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 834.6 kB

  • Original 1.2 MB
  • After minification 920.2 kB
  • After compression 334.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 834.6 kB or 71% of the original size.

CSS Optimization

-75%

Potential reduce by 1.3 MB

  • Original 1.8 MB
  • After minification 1.8 MB
  • After compression 445.0 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. Staging.krispykreme.com.au needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 146 (81%)

Requests Now

180

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 180 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Staging 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 127 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

staging.krispykreme.com.au accessibility score

74

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[role]s do not have all required [aria-*] attributes

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

staging.krispykreme.com.au best practices score

58

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

staging.krispykreme.com.au SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Staging.krispykreme.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 Staging.krispykreme.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.

Social Sharing Optimization

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