5.4 sec in total
486 ms
4.3 sec
610 ms
Welcome to nzpost.co.nz homepage info - get ready to check NZ Post best content for New Zealand right away, or after learning these important things about nzpost.co.nz
The New Zealand Post Group offers services to help New Zealand run. We connect people, businesses and communities.
Visit nzpost.co.nzWe analyzed Nzpost.co.nz page load time and found that the first response time was 486 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
nzpost.co.nz performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value17.5 s
0/100
25%
Value9.1 s
13/100
10%
Value1,820 ms
9/100
30%
Value0.003
100/100
15%
Value21.2 s
1/100
10%
486 ms
832 ms
223 ms
444 ms
616 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 52% of them (37 requests) were addressed to the original Nzpost.co.nz, 7% (5 requests) were made to Googletagmanager.com and 4% (3 requests) were made to Script.crazyegg.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Nzpost.co.nz.
Page size can be reduced by 257.9 kB (8%)
3.2 MB
2.9 MB
In fact, the total size of Nzpost.co.nz main page is 3.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. 65% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 200.1 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 30.5 kB, which is 14% 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 200.1 kB or 91% of the original size.
Potential reduce by 2.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. NZ Post images are well optimized though.
Potential reduce by 55.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 55.8 kB or 19% of the original size.
Potential reduce by 113 B
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. Nzpost.co.nz has all CSS files already compressed.
Number of requests can be reduced by 27 (44%)
62
35
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NZ Post. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
www.nzpost.co.nz
486 ms
www.nzpost.co.nz
832 ms
google_tag.script.js
223 ms
css_voVxdoCVD-SLpcrL3-4Brj7xMjwag3unnZzEBXmHHV8.css
444 ms
css_fKnogpaoLOqKPfMHt9rOXFDPZbZBaUZRSYcbUTq4lN4.css
616 ms
icon
41 ms
0998.js
37 ms
nzpost-logo-k.svg
611 ms
custom-logo.png
22 ms
js_yyl97sGkb3HLPv1vjQIQPEpYlGAFqWYJEOdI3dIPZNk.js
665 ms
embed.js
25 ms
js_HZTD49MNlr_Oo5unBN9xwSiK3imWp8OgyJ7r6tL7ZGg.js
813 ms
Send%20it.svg
668 ms
Find%20an%20address_6.svg
670 ms
Find%20a%20Rate.svg
824 ms
Find%20an%20NZ%20Post%20Store.svg
841 ms
parcel-leave.png
1355 ms
Mail%20delivery.png
1420 ms
Delivery.jpg
928 ms
express-illustration.png
1354 ms
apc-conveyor-promo.jpg
1365 ms
making-games.png
1419 ms
Asset%202_0.png
1353 ms
Asset%201_0.png
1576 ms
Facebook.svg
1580 ms
Twitter.svg
1577 ms
Linkedin.svg
1590 ms
Instagram.svg
1593 ms
nzpost-logo-footer-k.svg
1597 ms
www.nzpost.co.nz.json
21 ms
6735f9594d6bb8a4f1fe56c6b3e21cf5.js
14 ms
mothers-day-mob.jpg
1759 ms
mothers-day-hero.jpg
1376 ms
kahuku-hero-mob_0.jpg
1179 ms
kahuku-hero-desk.jpg
1389 ms
Grey_1.jpg
1202 ms
nz-post-pattern-10-line-medium-blue-cropped-70.svg
1197 ms
NZPSANSWEB-Semibold.woff
1356 ms
NZPSANSWEB-Bold.woff
1385 ms
NZPSANSWEB-Ultra.woff
1380 ms
NZPSANSWEB-Medium.woff
1553 ms
NZPSANSWEB-Regular.woff
1568 ms
NZPSANSWEB-Light.woff
1584 ms
gtm.js
77 ms
js
59 ms
destination
325 ms
destination
282 ms
destination
405 ms
analytics.js
452 ms
insight.min.js
386 ms
collect.js
392 ms
fbevents.js
445 ms
C9HTVZ1rmYztGcB5e7Fdbw==
626 ms
bukgztfw8m
446 ms
evergage.min.js
444 ms
activityi;src=4598948;type=remar0;cat=sitewd01;ord=3399613338476;npa=0;auiddc=579150051.1714865556;u1=%2F;pscdl=noapi;gtm=45fe4510z8811829445za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.nzpost.co.nz%2F
213 ms
insight_tag_errors.gif
183 ms
activityi;src=9050304;type=rt-br0;cat=nzpos0;ord=1112019197689;npa=0;auiddc=579150051.1714865556;u1=https%3A%2F%2Fwww.nzpost.co.nz%2F;u2=%2F;u3=;pscdl=noapi;gtm=45fe4510z8811829445za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.nzpost.co.nz%2F
142 ms
track_page_view
80 ms
collect
50 ms
collect
57 ms
clarity.js
37 ms
ga-audiences
79 ms
obtp.js
51 ms
conversion.js
92 ms
src=4598948;type=remar0;cat=sitewd01;ord=3399613338476;npa=0;auiddc=*;u1=%2F;pscdl=noapi;gtm=45fe4510z8811829445za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.nzpost.co.nz%2F
86 ms
src=9050304;type=rt-br0;cat=nzpos0;ord=1112019197689;npa=0;auiddc=*;u1=https%3A%2F%2Fwww.nzpost.co.nz%2F;u2=%2F;u3=;pscdl=noapi;gtm=45fe4510z8811829445za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.nzpost.co.nz%2F
99 ms
intercept-client-v1.25.0.js
23 ms
35 ms
17 ms
c.gif
8 ms
nzpost.co.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.
nzpost.co.nz 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
nzpost.co.nz 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nzpost.co.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 Nzpost.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.
nzpost.co.nz
Open Graph description is not detected on the main page of NZ Post. 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: