Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

planitnz.com

New Zealand Tours, Bus Passes & Travel Planning » Planit NZ Travel

Page Load Speed

10.9 sec in total

First Response

667 ms

Resources Loaded

7.5 sec

Page Rendered

2.8 sec

planitnz.com screenshot

About Website

Visit planitnz.com now to see the best up-to-date Planit NZ content for United States and also check out these interesting facts you probably never knew about planitnz.com

Planit NZ can provide you with tailor made self drive holidays, and the best price on day trips, multi-day tours and car or campervan rentals. Let us help you plan the trip of a lifetime to New Zealan...

Visit planitnz.com

Key Findings

We analyzed Planitnz.com page load time and found that the first response time was 667 ms and then it took 10.3 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

planitnz.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value9,270 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.224

56/100

15%

TTI (Time to Interactive)

Value29.9 s

0/100

10%

Network Requests Diagram

planitnz.com

667 ms

www.planitnz.com

867 ms

gtm.js

1020 ms

css

231 ms

css

254 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 60% of them (39 requests) were addressed to the original Planitnz.com, 11% (7 requests) were made to Fonts.gstatic.com and 6% (4 requests) were made to Cdn.livechatinc.com. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Planitnz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 143.3 kB (12%)

Content Size

1.2 MB

After Optimization

1.0 MB

In fact, the total size of Planitnz.com 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. 70% of websites need less resources to load. Images take 991.1 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 110.4 kB

  • Original 123.8 kB
  • After minification 91.5 kB
  • After compression 13.3 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 32.3 kB, which is 26% 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 110.4 kB or 89% of the original size.

Image Optimization

-3%

Potential reduce by 25.0 kB

  • Original 991.1 kB
  • After minification 966.1 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. Planit NZ images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 227 B

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

CSS Optimization

-14%

Potential reduce by 7.6 kB

  • Original 54.4 kB
  • After minification 54.4 kB
  • After compression 46.9 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. Planitnz.com needs all CSS files to be minified and compressed as it can save up to 7.6 kB or 14% of the original size.

Requests Breakdown

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

Requests Now

48

After Optimization

32

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

Accessibility Review

planitnz.com accessibility score

63

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

High

Form elements do not have associated labels

High

Links do not have a discernible 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.

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

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

planitnz.com best practices score

67

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

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

planitnz.com SEO score

82

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Planitnz.com 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 Planitnz.com 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 description is not detected on the main page of Planit NZ. 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: