Tools & Wizards About Us
eatwell.co.nz screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

eatwell.co.nz

Eat Well: Healthy Recipes & Nutrition Tips - NZ Herald - NZ Herald

Page Load Speed

4.4 sec in total

First Response

82 ms

Resources Loaded

2.2 sec

Page Rendered

2.2 sec

eatwell.co.nz screenshot

About Website

Click here to check amazing Eat Well content for New Zealand. Otherwise, check out these important facts you probably never knew about eatwell.co.nz

Discover Eat Well by NZ Herald - your go-to source for nutritious recipes, diet advice, and wellness tips to maintain a healthy lifestyle.

Visit eatwell.co.nz

Key Findings

We analyzed Eatwell.co.nz page load time and found that the first response time was 82 ms and then it took 4.4 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

eatwell.co.nz performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value18.4 s

0/100

25%

SI (Speed Index)

Value35.4 s

0/100

10%

TBT (Total Blocking Time)

Value8,400 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value37.8 s

0/100

10%

Network Requests Diagram

eatwell.co.nz

82 ms

eatwell.co.nz

934 ms

246 ms

nzme.js

22 ms

462b232fcb63ec2c862d2638cae0e436.js

23 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Eatwell.co.nz, 57% (27 requests) were made to Nzherald.co.nz and 4% (2 requests) were made to Securepubads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (934 ms) belongs to the original domain Eatwell.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (82%)

Content Size

1.3 MB

After Optimization

222.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eatwell.co.nz main page is 1.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. 65% of websites need less resources to load. HTML takes 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 1.0 MB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 105.2 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 1.0 MB or 91% of the original size.

Image Optimization

-1%

Potential reduce by 164 B

  • Original 29.0 kB
  • After minification 28.9 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. Eat Well images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.4 kB

  • Original 87.5 kB
  • After minification 87.5 kB
  • After compression 86.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-16%

Potential reduce by 386 B

  • Original 2.5 kB
  • After minification 2.5 kB
  • After compression 2.1 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. Eatwell.co.nz needs all CSS files to be minified and compressed as it can save up to 386 B or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (76%)

Requests Now

42

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eatwell.co.nz

eatwell.co.nz

82 ms

eatwell.co.nz

eatwell.co.nz

934 ms

246 ms

nzme.js

nzme.js

22 ms

462b232fcb63ec2c862d2638cae0e436.js

462b232fcb63ec2c862d2638cae0e436.js

23 ms

default.css

default.css

19 ms

tailwind-dist.css

tailwind-dist.css

22 ms

style.css

style.css

48 ms

ncposts-6.1.1.min.css

ncposts-6.1.1.min.css

87 ms

react.js

react.js

31 ms

default.js

default.js

75 ms

gtm.js

gtm.js

79 ms

polyfill.js

polyfill.js

73 ms

braze.min.js

braze.min.js

24 ms

polyfills.js

polyfills.js

20 ms

lazyLoad.js

lazyLoad.js

38 ms

gpt.js

gpt.js

211 ms

admiral-adblock.js

admiral-adblock.js

19 ms

gam-adblock.js

gam-adblock.js

36 ms

pub-5276995754775409

pub-5276995754775409

227 ms

swg-gaa.js

swg-gaa.js

226 ms

mini-jquery.js

mini-jquery.js

186 ms

local-storage.min.js

local-storage.min.js

186 ms

ga360-tracking.js

ga360-tracking.js

189 ms

data-ref.js

data-ref.js

185 ms

ouibounce-tracking.js

ouibounce-tracking.js

185 ms

prebid.js

prebid.js

201 ms

appear.js

appear.js

216 ms

global-ad-script.js

global-ad-script.js

213 ms

image.js

image.js

931 ms

queryly.v4.js

queryly.v4.js

325 ms

zuora-min.js

zuora-min.js

293 ms

v2xtlP4zrEslXHTmHCAG-KuyisZPjRwmwGO9qErzCeItmOXmlm7rZx_w

v2xtlP4zrEslXHTmHCAG-KuyisZPjRwmwGO9qErzCeItmOXmlm7rZx_w

411 ms

UWPKL-8SUZA-9NCKM-A8X6N-X2F79

UWPKL-8SUZA-9NCKM-A8X6N-X2F79

409 ms

logo_50px.png

logo_50px.png

381 ms

default.svg

default.svg

149 ms

placeholder_l.png

placeholder_l.png

148 ms

placeholder_p.png

placeholder_p.png

150 ms

spritemap.svg

spritemap.svg

216 ms

Inter-VariableFont_slnt,wght.ttf

Inter-VariableFont_slnt,wght.ttf

248 ms

slick.woff

slick.woff

79 ms

pubads_impl.js

pubads_impl.js

23 ms

skeleton.gif

skeleton.gif

116 ms

config.json

config.json

70 ms

83069739

83069739

52 ms

sync.min.js

sync.min.js

13 ms

map

map

78 ms

Accessibility Review

eatwell.co.nz 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-hidden="true"] elements contain focusable descendents

High

[aria-*] attributes do not have valid values

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

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.

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

eatwell.co.nz best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

eatwell.co.nz SEO score

84

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

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 Eatwell.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 Eatwell.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

eatwell.co.nz

Open Graph data is detected on the main page of Eat Well. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: