Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

nationalpark.co.nz

Tongariro National Park Visitor Information

Page Load Speed

6.3 sec in total

First Response

30 ms

Resources Loaded

5.8 sec

Page Rendered

482 ms

nationalpark.co.nz screenshot

About Website

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

Welcome to Tongariro National Park! Find out what to do, where to stay and how to plan your trip to this UNESCO Dual World Heritage Area

Visit nationalpark.co.nz

Key Findings

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

nationalpark.co.nz performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

nationalpark.co.nz

30 ms

nationalpark.co.nz

687 ms

www.nationalpark.co.nz

1479 ms

main.js

92 ms

js

72 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 57% of them (28 requests) were addressed to the original Nationalpark.co.nz, 22% (11 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Nationalpark.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 89.8 kB (2%)

Content Size

4.3 MB

After Optimization

4.2 MB

In fact, the total size of Nationalpark.co.nz main page is 4.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 35.5 kB

  • Original 45.6 kB
  • After minification 40.7 kB
  • After compression 10.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. This page needs HTML code to be minified as it can gain 4.9 kB, which is 11% 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 35.5 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 54.3 kB

  • Original 4.0 MB
  • After minification 3.9 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. National Park images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

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

-0%

Potential reduce by 58 B

  • Original 50.5 kB
  • After minification 50.5 kB
  • After compression 50.4 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. Nationalpark.co.nz has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (45%)

Requests Now

31

After Optimization

17

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

Accessibility Review

nationalpark.co.nz accessibility score

77

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

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

Missing source maps for large first-party JavaScript

SEO Factors

nationalpark.co.nz SEO score

85

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nationalpark.co.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nationalpark.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

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