Tools & Wizards About Us
fernznewzealand.co.nz screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    63% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

fernznewzealand.co.nz

New Zealand Ferns | Shade Plants Ferns | Ferns – Native Plants

Page Load Speed

7.9 sec in total

First Response

1.1 sec

Resources Loaded

6.5 sec

Page Rendered

336 ms

fernznewzealand.co.nz screenshot

About Website

Welcome to fernznewzealand.co.nz homepage info - get ready to check Fernz New Zealand best content right away, or after learning these important things about fernznewzealand.co.nz

NZ Ferns is a family owned business. We are the famous New Zealand Ferns, Shade Plants Ferns, Ferns – Native Plants, Blechnum ferns, Dicksonia ferns supplier

Visit fernznewzealand.co.nz

Key Findings

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

Performance Metrics

fernznewzealand.co.nz performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.2 s

0/100

25%

SI (Speed Index)

Value16.2 s

0/100

10%

TBT (Total Blocking Time)

Value240 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

fernznewzealand.co.nz

1132 ms

fernznewzealand.co.nz

1185 ms

style.css

478 ms

custom.css

726 ms

global.css

910 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 93% of them (56 requests) were addressed to the original Fernznewzealand.co.nz, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Fernznewzealand.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 138.1 kB (17%)

Content Size

811.4 kB

After Optimization

673.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fernznewzealand.co.nz main page is 811.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Images take 693.2 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 23.5 kB

  • Original 32.4 kB
  • After minification 29.6 kB
  • After compression 8.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. 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 23.5 kB or 73% of the original size.

Image Optimization

-11%

Potential reduce by 77.4 kB

  • Original 693.2 kB
  • After minification 615.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. Obviously, Fernz New Zealand needs image optimization as it can save up to 77.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-29%

Potential reduce by 17.2 kB

  • Original 60.2 kB
  • After minification 58.9 kB
  • After compression 43.0 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 17.2 kB or 29% of the original size.

CSS Optimization

-78%

Potential reduce by 20.0 kB

  • Original 25.6 kB
  • After minification 17.6 kB
  • After compression 5.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. Fernznewzealand.co.nz needs all CSS files to be minified and compressed as it can save up to 20.0 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (58%)

Requests Now

57

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fernznewzealand.co.nz

fernznewzealand.co.nz

1132 ms

fernznewzealand.co.nz

fernznewzealand.co.nz

1185 ms

style.css

style.css

478 ms

custom.css

custom.css

726 ms

global.css

global.css

910 ms

responsive.css

responsive.css

1126 ms

jquery-1.6.4.min.js

jquery-1.6.4.min.js

1590 ms

cufon-yui.js

cufon-yui.js

1601 ms

Kozuka_Gothic_Pro_L_300.font.js

Kozuka_Gothic_Pro_L_300.font.js

1156 ms

cufon-replace.js

cufon-replace.js

950 ms

script.js

script.js

1130 ms

flashobject.js

flashobject.js

1190 ms

jquery.equalheights.js

jquery.equalheights.js

1347 ms

jquery.bxslider.css

jquery.bxslider.css

1361 ms

jquery-1.9.1.js

jquery-1.9.1.js

2509 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

1425 ms

jquery.bxslider.js

jquery.bxslider.js

1802 ms

reset.css

reset.css

1123 ms

superfish.css

superfish.css

1178 ms

grid.css

grid.css

1337 ms

forms.css

forms.css

1348 ms

prettyPhoto.css

prettyPhoto.css

1359 ms

galleryfic.css

galleryfic.css

1403 ms

kwicks.css

kwicks.css

1555 ms

coin-slider.css

coin-slider.css

1558 ms

advanced.css

advanced.css

1568 ms

superfish.js

superfish.js

226 ms

coin-slider.js

coin-slider.js

230 ms

tabs.js

tabs.js

223 ms

FF-cash.js

FF-cash.js

225 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

225 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

555 ms

jquery.color.js

jquery.color.js

557 ms

jquery.backgroundPosition.js

jquery.backgroundPosition.js

553 ms

jquery.insetBorderEffect.js

jquery.insetBorderEffect.js

554 ms

analytics.js

analytics.js

50 ms

ga.js

ga.js

87 ms

collect

collect

37 ms

__utm.gif

__utm.gif

18 ms

texture.jpg

texture.jpg

234 ms

logo.png

logo.png

244 ms

Unfortunately%20we%20have%20been%20extremely%20busy%20processing%20orders%20over%20the%20past%20few%20weeks%20&%20haven't%20had%20time%20to%20update%20our%20website%20stock%20quantities,so%20any%20items%20showing%20'Out%20of%20Stock',%20may%20currently%20now%20be%20in%20stoc.png

Unfortunately%20we%20have%20been%20extremely%20busy%20processing%20orders%20over%20the%20past%20few%20weeks%20&%20haven't%20had%20time%20to%20update%20our%20website%20stock%20quantities,so%20any%20items%20showing%20'Out%20of%20Stock',%20may%20currently%20now%20be%20in%20stoc.png

1243 ms

banner2.jpg

banner2.jpg

562 ms

banner3.jpg

banner3.jpg

571 ms

banner4.jpg

banner4.jpg

568 ms

banner5.jpg

banner5.jpg

681 ms

page1-img1.jpg

page1-img1.jpg

702 ms

page1-img2.jpg

page1-img2.jpg

1018 ms

page1-img3.jpg

page1-img3.jpg

1017 ms

page1-icon1.png

page1-icon1.png

802 ms

header.jpg

header.jpg

904 ms

cart.png

cart.png

923 ms

menu-border.png

menu-border.png

1019 ms

flash.jpg

flash.jpg

1135 ms

content.png

content.png

1145 ms

border-bot.gif

border-bot.gif

1238 ms

circ-list.png

circ-list.png

1235 ms

bx_loader.gif

bx_loader.gif

1048 ms

controls.png

controls.png

1165 ms

adv-trigger.png

adv-trigger.png

228 ms

Accessibility Review

fernznewzealand.co.nz accessibility score

100

Accessibility Issues

Best Practices

fernznewzealand.co.nz best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

SEO Factors

fernznewzealand.co.nz SEO score

92

Search Engine Optimization Advices

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

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

fernznewzealand.co.nz

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