8.1 sec in total
615 ms
7.3 sec
210 ms
Visit nzpam.govt.nz now to see the best up-to-date Nzpam content for New Zealand and also check out these interesting facts you probably never knew about nzpam.govt.nz
Visit nzpam.govt.nzWe analyzed Nzpam.govt.nz page load time and found that the first response time was 615 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
nzpam.govt.nz performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value6.0 s
12/100
25%
Value7.0 s
32/100
10%
Value310 ms
78/100
30%
Value0.485
17/100
15%
Value6.8 s
55/100
10%
615 ms
1587 ms
982 ms
787 ms
791 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 91% of them (63 requests) were addressed to the original Nzpam.govt.nz, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Universal.iperceptions.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Nzpam.govt.nz.
Page size can be reduced by 246.8 kB (17%)
1.4 MB
1.2 MB
In fact, the total size of Nzpam.govt.nz main page is 1.4 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. 25% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 103.6 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 53.1 kB, which is 45% 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 103.6 kB or 89% of the original size.
Potential reduce by 99.4 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. Nzpam images are well optimized though.
Potential reduce by 43.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 43.8 kB or 60% of the original size.
Number of requests can be reduced by 30 (54%)
56
26
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nzpam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
nzpam.govt.nz
615 ms
cms
1587 ms
base-cachekey-cms-7008.092.css
982 ms
resourcejquery-ui-themessunburstjqueryui-cachekey-cms-7008.095.css
787 ms
tw.accordion-cachekey-cms-7008.096.css
791 ms
fmit.jsutils-cachekey-cms-7008.099.css
408 ms
mbie_custom-cachekey-cms-7008.0911.css
410 ms
contentpanels-cachekey-cms-7008.0912.css
809 ms
bsbaudittool-cachekey-cms-7008.0914.css
622 ms
fck_override-cachekey-cms-7008.0915.css
829 ms
bootstrap.min-cachekey-cms-7008.0916.css
1963 ms
tw.lightweightalert-cachekey-cms-7008.0918.css
803 ms
ploneCustom-cachekey-cms-7008.0919.css
823 ms
jquery-cachekey-cms-7008.061.js
2431 ms
collective.js.jqueryui.custom.min-cachekey-cms-7008.064.js
2389 ms
resourcefmit.jsutils.javascriptjquery.cookie-cachekey-cms-7008.065.js
1075 ms
resourcesharedfixes.javascriptplone_calendar_fix-cachekey-cms-7008.066.js
1005 ms
fckeditor-cachekey-cms-7008.067.js
1220 ms
jquery-1.11.1.min-cachekey-cms-7008.069.js
2173 ms
logo.png
210 ms
search-icon.png
207 ms
mega2011_close.png
210 ms
image
3303 ms
image
3388 ms
image
994 ms
image
800 ms
image
412 ms
60a908065c0a4882b5352e7f13d9552d
411 ms
3f733230d4b24c1b96cd84a99475fef8
616 ms
90935f73782d416ebcbfa56f13cc6160
616 ms
7e309081fb3647489a7475cd71d84f36
816 ms
Safety%20icon.jpg
1006 ms
image-2
1008 ms
mbie-logo.png
1024 ms
nz-govt-logo.png
1196 ms
spinner.gif
1209 ms
gtm.js
75 ms
header-graphic.png
1203 ms
search-box.png
1220 ms
mega2011_left_end_gray_bordered.png
1392 ms
menu-normal-bg.png
1403 ms
mega-menu-bg.png
1336 ms
breadcrumb-bg.png
1354 ms
ul-bullet.png
1526 ms
slideshow-arrow.png
1541 ms
play.gif
1539 ms
pause.gif
1559 ms
heading-accent.png
1727 ms
latest-news-bg.png
1739 ms
footer-banner.png
1933 ms
top-icon.png
1760 ms
icons.png
1928 ms
mega2011_icons_normal.png
1944 ms
firasans-light-webfont.woff
2354 ms
firasans-regular-webfont.woff
2521 ms
firasans-medium-webfont.woff
2529 ms
analytics.js
5 ms
wrapper.js
149 ms
loop11.js
813 ms
collect
11 ms
firasans-bold-webfont.woff
2416 ms
flexslider-icon.woff
2428 ms
online-exploration-database
2784 ms
nzpandm.png
2198 ms
NZPAM%20Maps%20Tile.png
2587 ms
BO%202016%20Consultation%20tile.jpg
2394 ms
flexslider-icon.ttf
387 ms
flexslider-icon.svg
355 ms
iFrame.html
9 ms
nzpam.govt.nz accessibility score
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
Links do not have a discernible name
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.
nzpam.govt.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
nzpam.govt.nz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nzpam.govt.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 Nzpam.govt.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.
nzpam.govt.nz
Open Graph description is not detected on the main page of Nzpam. 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: