Tools & Wizards About Us
weetbix.co.nz screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

weetbix.co.nz

Weet-Bix New Zealand - Weet-Bix NZ

Page Load Speed

15.7 sec in total

First Response

482 ms

Resources Loaded

14.7 sec

Page Rendered

528 ms

weetbix.co.nz screenshot

About Website

Visit weetbix.co.nz now to see the best up-to-date Weet Bix content for New Zealand and also check out these interesting facts you probably never knew about weetbix.co.nz

Visit weetbix.co.nz

Key Findings

We analyzed Weetbix.co.nz page load time and found that the first response time was 482 ms and then it took 15.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

weetbix.co.nz performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value1,450 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.988

2/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

weetbix.co.nz

482 ms

weetbix.co.nz

10730 ms

wp-emoji-release.min.js

233 ms

style.css

695 ms

jquery-ui.css

44 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 61% of them (53 requests) were addressed to the original Weetbix.co.nz, 8% (7 requests) were made to Apis.google.com and 7% (6 requests) were made to Ssl.gstatic.com. The less responsive or slowest element that took the longest time to load (10.7 sec) belongs to the original domain Weetbix.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 467.7 kB (14%)

Content Size

3.3 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weetbix.co.nz main page is 3.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. 60% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 61.9 kB

  • Original 73.8 kB
  • After minification 56.7 kB
  • After compression 11.9 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. This page needs HTML code to be minified as it can gain 17.1 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 61.9 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 85.6 kB

  • Original 2.8 MB
  • After minification 2.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. Weet Bix images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 111.5 kB

  • Original 218.7 kB
  • After minification 211.8 kB
  • After compression 107.2 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 111.5 kB or 51% of the original size.

CSS Optimization

-81%

Potential reduce by 208.7 kB

  • Original 257.2 kB
  • After minification 255.9 kB
  • After compression 48.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. Weetbix.co.nz needs all CSS files to be minified and compressed as it can save up to 208.7 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (48%)

Requests Now

79

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weet Bix. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

weetbix.co.nz

weetbix.co.nz

482 ms

weetbix.co.nz

weetbix.co.nz

10730 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

233 ms

style.css

style.css

695 ms

jquery-ui.css

jquery-ui.css

44 ms

jquery.jscrollpane.css

jquery.jscrollpane.css

687 ms

sanitarium-news-public.css

sanitarium-news-public.css

688 ms

sanitarium-products-public.css

sanitarium-products-public.css

711 ms

sanitarium-recipes-public.css

sanitarium-recipes-public.css

712 ms

modernizr.js

modernizr.js

717 ms

jquery.min.js

jquery.min.js

51 ms

slick.min.js

slick.min.js

43 ms

search.js

search.js

914 ms

jquery.mousewheel.js

jquery.mousewheel.js

916 ms

jquery.jscrollpane.min.js

jquery.jscrollpane.min.js

919 ms

weetbix.min.js

weetbix.min.js

920 ms

platform.js

platform.js

74 ms

sanitarium-news-public.js

sanitarium-news-public.js

937 ms

sanitarium-products-public.js

sanitarium-products-public.js

938 ms

sanitarium-recipes-public.js

sanitarium-recipes-public.js

1146 ms

wp-embed.min.js

wp-embed.min.js

1145 ms

weet-bix-fruit-smoothies.ashx

weet-bix-fruit-smoothies.ashx

2065 ms

weet-bix-menu-new.png

weet-bix-menu-new.png

799 ms

weet-bix-bits-menu-new.png

weet-bix-bits-menu-new.png

885 ms

weetbix-go.png

weetbix-go.png

802 ms

WB-blends-website-1.png

WB-blends-website-1.png

1130 ms

GF-2.png

GF-2.png

872 ms

how-do-you-do-yours-subnav.png

how-do-you-do-yours-subnav.png

1099 ms

weetbix-bites-memory-game-subnav.png

weetbix-bites-memory-game-subnav.png

799 ms

how-many-do-you-do-subnav.png

how-many-do-you-do-subnav.png

879 ms

Inspiration.png

Inspiration.png

1118 ms

better-brekkie-programme.png

better-brekkie-programme.png

1100 ms

news-subnav.png

news-subnav.png

1107 ms

kickstartsubnav.png

kickstartsubnav.png

1114 ms

kidsTriathlonsubnav.png

kidsTriathlonsubnav.png

1554 ms

weetbix-all-blacks-hero-banner.jpg

weetbix-all-blacks-hero-banner.jpg

2010 ms

weetbix-go-main-banner.jpg

weetbix-go-main-banner.jpg

1792 ms

weetbix-banner-1600x556px.jpg

weetbix-banner-1600x556px.jpg

2734 ms

weetbix-breakfast-builder-tile2.jpg

weetbix-breakfast-builder-tile2.jpg

1577 ms

weetbix-all-blacks-tile.jpg

weetbix-all-blacks-tile.jpg

1588 ms

001_Home_Weetbix_Go_TileV3.jpg

001_Home_Weetbix_Go_TileV3.jpg

2015 ms

weetbix-five-health-star-rating-tile.jpg

weetbix-five-health-star-rating-tile.jpg

1811 ms

kick-start-breakfast-tile.jpg

kick-start-breakfast-tile.jpg

1819 ms

gluten-free-weetbix-tile.jpg

gluten-free-weetbix-tile.jpg

2020 ms

bits-game-new.jpg

bits-game-new.jpg

2519 ms

GlutenFree-Badge.png

GlutenFree-Badge.png

2050 ms

weetbix-calculator-tile.jpg

weetbix-calculator-tile.jpg

2237 ms

newsletter-tile.jpg

newsletter-tile.jpg

2238 ms

power-up-weet-bix-porridge.ashx

power-up-weet-bix-porridge.ashx

1639 ms

Weetbix-Porridge.ashx

Weetbix-Porridge.ashx

2548 ms

gtm.js

gtm.js

131 ms

sdk.js

sdk.js

791 ms

dot-bg.png

dot-bg.png

2232 ms

ui-sc5cf2813c1.png

ui-sc5cf2813c1.png

2263 ms

analytics.js

analytics.js

21 ms

collect

collect

6 ms

collect

collect

91 ms

Gibson-Regular-webfont.woff

Gibson-Regular-webfont.woff

2281 ms

Gibson-Bold-webfont.woff

Gibson-Bold-webfont.woff

2296 ms

Gibson-SemiBold-webfont.woff

Gibson-SemiBold-webfont.woff

2294 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

14 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

29 ms

subscribe_embed

subscribe_embed

120 ms

fontello.woff

fontello.woff

2315 ms

cheappine-sans-webfont.woff

cheappine-sans-webfont.woff

2487 ms

Gibson-Light-webfont.woff

Gibson-Light-webfont.woff

2497 ms

postmessageRelay

postmessageRelay

50 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

17 ms

rpc:shindig_random.js

rpc:shindig_random.js

38 ms

www-subscribe-embed-vflTum1sJ.css

www-subscribe-embed-vflTum1sJ.css

26 ms

www-subscribe-embed.js

www-subscribe-embed.js

38 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

www-hitchhiker-vflvB63an.png

www-hitchhiker-vflvB63an.png

20 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

rough-break.png

rough-break.png

2290 ms

rough-break-top.png

rough-break-top.png

1945 ms

167 ms

xd_arbiter.php

xd_arbiter.php

429 ms

cb=gapi.loaded_2

cb=gapi.loaded_2

3 ms

border_3.gif

border_3.gif

6 ms

subscribe_embed

subscribe_embed

52 ms

spacer.gif

spacer.gif

6 ms

bubbleSprite_3.png

bubbleSprite_3.png

10 ms

bubbleDropR_3.png

bubbleDropR_3.png

11 ms

bubbleDropB_3.png

bubbleDropB_3.png

14 ms

www-subscribe-embed-card-vflqARhQ4.css

www-subscribe-embed-card-vflqARhQ4.css

2 ms

www-subscribe-embed-card.js

www-subscribe-embed-card.js

11 ms

Accessibility Review

weetbix.co.nz accessibility score

91

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Best Practices

weetbix.co.nz best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

weetbix.co.nz SEO score

83

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

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 Weetbix.co.nz 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 Weetbix.co.nz 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

weetbix.co.nz

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