Tools & Wizards About Us
heritageroses.org.nz screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

heritageroses.org.nz

Welcome - Heritage Roses New Zealand Incorporated

Page Load Speed

4.3 sec in total

First Response

230 ms

Resources Loaded

3.5 sec

Page Rendered

569 ms

heritageroses.org.nz screenshot

About Website

Click here to check amazing Heritage Roses content. Otherwise, check out these important facts you probably never knew about heritageroses.org.nz

Heritage Roses NZ was formed in June 1980 with the aim of growing and learning about old fashioned roses for all gardening enthusiasts.

Visit heritageroses.org.nz

Key Findings

We analyzed Heritageroses.org.nz page load time and found that the first response time was 230 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

heritageroses.org.nz performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value9.2 s

1/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value1,690 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

heritageroses.org.nz

230 ms

heritageroses.org.nz

1050 ms

cf7ic-style.css

19 ms

styles.css

748 ms

style.css

30 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 82% of them (50 requests) were addressed to the original Heritageroses.org.nz, 15% (9 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Heritageroses.org.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 213.9 kB (21%)

Content Size

1.0 MB

After Optimization

817.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Heritageroses.org.nz main page is 1.0 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. 40% of websites need less resources to load. Images take 664.8 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 97.1 kB

  • Original 130.5 kB
  • After minification 130.3 kB
  • After compression 33.4 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 97.1 kB or 74% of the original size.

Image Optimization

-17%

Potential reduce by 115.6 kB

  • Original 664.8 kB
  • After minification 549.2 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, Heritage Roses needs image optimization as it can save up to 115.6 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 439 B

  • Original 136.9 kB
  • After minification 136.9 kB
  • After compression 136.5 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

-1%

Potential reduce by 751 B

  • Original 99.0 kB
  • After minification 99.0 kB
  • After compression 98.2 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. Heritageroses.org.nz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 40 (83%)

Requests Now

48

After Optimization

8

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

heritageroses.org.nz

heritageroses.org.nz

230 ms

heritageroses.org.nz

heritageroses.org.nz

1050 ms

cf7ic-style.css

cf7ic-style.css

19 ms

styles.css

styles.css

748 ms

style.css

style.css

30 ms

style.min.css

style.min.css

720 ms

theme.min.css

theme.min.css

752 ms

header-footer.min.css

header-footer.min.css

755 ms

elementor-icons.min.css

elementor-icons.min.css

41 ms

frontend.min.css

frontend.min.css

49 ms

swiper.min.css

swiper.min.css

56 ms

post-8.css

post-8.css

63 ms

frontend.min.css

frontend.min.css

84 ms

global.css

global.css

77 ms

post-16.css

post-16.css

96 ms

post-47.css

post-47.css

100 ms

post-39.css

post-39.css

100 ms

default.css

default.css

118 ms

css

css

41 ms

fontawesome.min.css

fontawesome.min.css

119 ms

solid.min.css

solid.min.css

128 ms

brands.min.css

brands.min.css

130 ms

jquery.min.js

jquery.min.js

145 ms

jquery-migrate.min.js

jquery-migrate.min.js

146 ms

custom.js

custom.js

164 ms

index.js

index.js

160 ms

index.js

index.js

173 ms

api.js

api.js

66 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

176 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

184 ms

wp-polyfill.min.js

wp-polyfill.min.js

192 ms

index.js

index.js

199 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

210 ms

imagesloaded.min.js

imagesloaded.min.js

208 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

224 ms

webpack.runtime.min.js

webpack.runtime.min.js

225 ms

frontend-modules.min.js

frontend-modules.min.js

244 ms

hooks.min.js

hooks.min.js

238 ms

i18n.min.js

i18n.min.js

259 ms

frontend.min.js

frontend.min.js

258 ms

waypoints.min.js

waypoints.min.js

274 ms

core.min.js

core.min.js

257 ms

frontend.min.js

frontend.min.js

258 ms

elements-handlers.min.js

elements-handlers.min.js

261 ms

home-bg.jpg

home-bg.jpg

54 ms

logo.png

logo.png

53 ms

home-slider-c-heritage-roses-nz.jpg

home-slider-c-heritage-roses-nz.jpg

1356 ms

home-slider-b-heritage-roses-nz.jpg

home-slider-b-heritage-roses-nz.jpg

1339 ms

home-slider-a-heritage-roses-nz.jpg

home-slider-a-heritage-roses-nz.jpg

1371 ms

home-slider-d-heritage-roses-nz.jpg

home-slider-d-heritage-roses-nz.jpg

1362 ms

fa-solid-900.woff

fa-solid-900.woff

1380 ms

fa-brands-400.woff

fa-brands-400.woff

1332 ms

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG9_FrYtHaw.woff

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG9_FrYtHaw.woff

21 ms

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG-3FrYtHaw.woff

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG-3FrYtHaw.woff

26 ms

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG4HFrYtHaw.woff

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG4HFrYtHaw.woff

53 ms

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG1_FrYtHaw.woff

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG1_FrYtHaw.woff

67 ms

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG9_ErYtHaw.woff

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG9_ErYtHaw.woff

94 ms

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaGwHCrYtHaw.woff

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaGwHCrYtHaw.woff

71 ms

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaGzjCrYtHaw.woff

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaGzjCrYtHaw.woff

72 ms

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG1_CrYtHaw.woff

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG1_CrYtHaw.woff

71 ms

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG3bCrYtHaw.woff

k3kCo84MPvpLmixcA63oeAL7Iqp5IZJF9bmaG3bCrYtHaw.woff

84 ms

Accessibility Review

heritageroses.org.nz accessibility score

96

Accessibility Issues

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

Best Practices

heritageroses.org.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

heritageroses.org.nz SEO score

97

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

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 Heritageroses.org.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 Heritageroses.org.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

heritageroses.org.nz

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