Tools & Wizards About Us
naturalus.co.nz screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

naturalus.co.nz

Home - Naturalus

Page Load Speed

13.7 sec in total

First Response

503 ms

Resources Loaded

12.6 sec

Page Rendered

507 ms

naturalus.co.nz screenshot

About Website

Visit naturalus.co.nz now to see the best up-to-date Naturalus content and also check out these interesting facts you probably never knew about naturalus.co.nz

All natural products, handmade in Christchurch, New Zealand, by a medical herbalist with a passion for herbal healing.

Visit naturalus.co.nz

Key Findings

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

naturalus.co.nz performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

8/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value260 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value8.9 s

35/100

10%

Network Requests Diagram

naturalus.co.nz

503 ms

www.naturalus.co.nz

2927 ms

jquery.min.js

47 ms

jquery-migrate.min.js

47 ms

v4-shims.min.js

218 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 61% of them (39 requests) were addressed to the original Naturalus.co.nz, 14% (9 requests) were made to Fonts.gstatic.com and 13% (8 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Naturalus.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 281.0 kB (24%)

Content Size

1.2 MB

After Optimization

886.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Naturalus.co.nz main page is 1.2 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. 45% of websites need less resources to load. Images take 594.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 198.1 kB

  • Original 237.7 kB
  • After minification 237.3 kB
  • After compression 39.6 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 198.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 2 B

  • Original 594.8 kB
  • After minification 594.8 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. Naturalus images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 58.1 kB

  • Original 214.3 kB
  • After minification 214.3 kB
  • After compression 156.3 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 58.1 kB or 27% of the original size.

CSS Optimization

-21%

Potential reduce by 24.9 kB

  • Original 120.6 kB
  • After minification 120.6 kB
  • After compression 95.7 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. Naturalus.co.nz needs all CSS files to be minified and compressed as it can save up to 24.9 kB or 21% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (89%)

Requests Now

53

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

naturalus.co.nz

naturalus.co.nz

503 ms

www.naturalus.co.nz

www.naturalus.co.nz

2927 ms

jquery.min.js

jquery.min.js

47 ms

jquery-migrate.min.js

jquery-migrate.min.js

47 ms

v4-shims.min.js

v4-shims.min.js

218 ms

js

js

105 ms

custom-pro-widget-nav-menu.min.css

custom-pro-widget-nav-menu.min.css

432 ms

script.js

script.js

683 ms

css

css

61 ms

frontend.min.js

frontend.min.js

634 ms

frontend.js

frontend.js

638 ms

general.min.js

general.min.js

638 ms

eael-6.js

eael-6.js

848 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

641 ms

e-202435.js

e-202435.js

54 ms

frontend.js

frontend.js

645 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

854 ms

scroll-to-top.min.js

scroll-to-top.min.js

855 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

856 ms

webpack.runtime.min.js

webpack.runtime.min.js

855 ms

frontend-modules.min.js

frontend-modules.min.js

862 ms

hooks.min.js

hooks.min.js

41 ms

i18n.min.js

i18n.min.js

52 ms

frontend.min.js

frontend.min.js

1062 ms

waypoints.min.js

waypoints.min.js

1066 ms

core.min.js

core.min.js

51 ms

frontend.min.js

frontend.min.js

1274 ms

elements-handlers.min.js

elements-handlers.min.js

1277 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

1 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

1 ms

jetpack.css

jetpack.css

1 ms

TreesOverlay90.jpg

TreesOverlay90.jpg

78 ms

Nat-Logo-Stamp-FX2022-Nov9-Teal.png

Nat-Logo-Stamp-FX2022-Nov9-Teal.png

134 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

17 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrc.woff

22 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff

27 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrc.woff

29 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrc.woff

30 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff

30 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff

34 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrc.woff

34 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrc.woff

30 ms

Nat-Logo-Stamp-FX2022-Dec31-800-teal.png

Nat-Logo-Stamp-FX2022-Dec31-800-teal.png

5 ms

frontend.min.css

frontend.min.css

220 ms

astra-local-fonts.css

astra-local-fonts.css

216 ms

menu-animation.min.css

menu-animation.min.css

215 ms

frontend.css

frontend.css

219 ms

frontend.css

frontend.css

216 ms

elementor.css

elementor.css

215 ms

header-footer-elementor.css

header-footer-elementor.css

215 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

219 ms

general.min.css

general.min.css

215 ms

eael-6.css

eael-6.css

217 ms

swiper.min.css

swiper.min.css

217 ms

post-475.css

post-475.css

214 ms

custom-pro-frontend-lite.min.css

custom-pro-frontend-lite.min.css

216 ms

all.min.css

all.min.css

219 ms

v4-shims.min.css

v4-shims.min.css

216 ms

post-6.css

post-6.css

216 ms

bg-09-free-img.jpg

bg-09-free-img.jpg

2186 ms

post-849.css

post-849.css

215 ms

post-1583.css

post-1583.css

214 ms

animations.min.css

animations.min.css

216 ms

scroll-to-top.min.css

scroll-to-top.min.css

214 ms

Accessibility Review

naturalus.co.nz accessibility score

96

Accessibility Issues

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

Best Practices

naturalus.co.nz best practices score

75

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

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

SEO Factors

naturalus.co.nz SEO score

100

Search Engine Optimization Advices

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

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

naturalus.co.nz

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