10.9 sec in total
667 ms
7.5 sec
2.8 sec
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.comWe 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.
planitnz.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value10.5 s
0/100
25%
Value8.4 s
18/100
10%
Value9,270 ms
0/100
30%
Value0.224
56/100
15%
Value29.9 s
0/100
10%
667 ms
867 ms
1020 ms
231 ms
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 size can be reduced by 143.3 kB (12%)
1.2 MB
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.
Potential reduce by 110.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. 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.
Potential reduce by 25.0 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.
Potential reduce by 227 B
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.
Potential reduce by 7.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. 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.
Number of requests can be reduced by 16 (33%)
48
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.
planitnz.com
667 ms
www.planitnz.com
867 ms
gtm.js
1020 ms
css
231 ms
css
254 ms
font-awesome.min.css
217 ms
daterangepicker.css
231 ms
api.js
253 ms
pagecombinedstyle.css
161 ms
pagecombinedscript.js
218 ms
homepage.js
1379 ms
tracking.js
1522 ms
fbds.js
1330 ms
close.png
2543 ms
loading.gif
1983 ms
prev.png
1644 ms
next.png
2585 ms
SetWidth140-Planit-Logo.png
1644 ms
chat_icon.jpg
1224 ms
Home-Banner-Nelson.jpg
2345 ms
Home-Banner-Milford.jpg
2633 ms
slide_btn_prev.png
2344 ms
slide_btn_next.png
2344 ms
arrow_hover.png
3724 ms
profilepic.gif
3806 ms
bubble_left.png
2795 ms
frmbg1.jpg
4642 ms
cal_icon.jpg
2907 ms
checked_bg.gif
2995 ms
arrow.png
2798 ms
frmbg2.jpg
3223 ms
North-Island-Feature.jpg
3420 ms
South-Island-Feature.jpg
4039 ms
Small-Group-Tours.jpg
4099 ms
Car-Rental-Banner.jpg
4022 ms
CroppedImage240240-TASK-51758.jpg
4021 ms
CroppedImage240240-doha-2366127-1920.jpeg
5213 ms
CroppedImage240240-12-Day-Snow-Tour-Banner.jpg
4347 ms
CroppedImage240240-sydney-opera-house-3381786-1920.jpg
4384 ms
footsccions.gif
4322 ms
footlogo.gif
4071 ms
up.gif
4083 ms
blackx.png
4090 ms
formlogo.jpg
4099 ms
recaptcha__en.js
1599 ms
manhattandarling-regular-webfont.woff
4196 ms
corerhino65bold-webfont.woff
4124 ms
corerhino75heavy-webfont.woff
4484 ms
NaPecZTIAOhVxoMyOr9n_E7fdMPmCA.ttf
708 ms
NaPDcZTIAOhVxoMyOr9n_E7ffGjEGItzZg.ttf
942 ms
NaPDcZTIAOhVxoMyOr9n_E7ffAzHGItzZg.ttf
1148 ms
NaPDcZTIAOhVxoMyOr9n_E7ffBzCGItzZg.ttf
1153 ms
NaPDcZTIAOhVxoMyOr9n_E7ffHjDGItzZg.ttf
1152 ms
fontawesome-webfont.woff
612 ms
analytics.js
325 ms
oribi.js
569 ms
open_chat.cgi
419 ms
collect
278 ms
css
344 ms
0.96a16c18.chunk.js
344 ms
2.451b6ee6.chunk.js
346 ms
iframe.cedbaaf5.chunk.js
440 ms
collect
516 ms
o-0IIpQlx3QUlC5A4PNr6zRF.ttf
10 ms
o-0NIpQlx3QUlC5A4PNjXhFVatyE.ttf
10 ms
planitnz.com accessibility score
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
ARIA input fields do not have accessible names
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
<html> element does not have a [lang] attribute
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
planitnz.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
planitnz.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
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.
planitnz.com
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: