12.9 sec in total
578 ms
12.2 sec
162 ms
Visit nzte.govt.nz now to see the best up-to-date NZTE content for New Zealand and also check out these interesting facts you probably never knew about nzte.govt.nz
Welcome to New Zealand Trade & Enterprise. We’re the New Zealand government’s international business development agency. We use our knowledge and networks to help New Zealand businesses grow internati...
Visit nzte.govt.nzWe analyzed Nzte.govt.nz page load time and found that the first response time was 578 ms and then it took 12.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
nzte.govt.nz performance score
name
value
score
weighting
Value6.0 s
3/100
10%
Value19.1 s
0/100
25%
Value13.9 s
1/100
10%
Value3,450 ms
2/100
30%
Value0.259
47/100
15%
Value25.7 s
0/100
10%
578 ms
6608 ms
391 ms
484 ms
474 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 5% of them (5 requests) were addressed to the original Nzte.govt.nz, 72% (67 requests) were made to Cache.web.nzte.govt.nz and 10% (9 requests) were made to Mail.nzte.co.nz. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain Nzte.govt.nz.
Page size can be reduced by 2.0 MB (77%)
2.7 MB
624.7 kB
In fact, the total size of Nzte.govt.nz main page is 2.7 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. 35% of websites need less resources to load. Javascripts take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 45.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 45.4 kB or 82% of the original size.
Potential reduce by 7.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. NZTE images are well optimized though.
Potential reduce by 1.8 MB
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 1.8 MB or 80% of the original size.
Potential reduce by 174.1 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. Nzte.govt.nz needs all CSS files to be minified and compressed as it can save up to 174.1 kB or 81% of the original size.
Number of requests can be reduced by 65 (72%)
90
25
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NZTE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 61 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.nzte.govt.nz
578 ms
www.nzte.govt.nz
6608 ms
1504203871.js
391 ms
style.C2o4rg.css
484 ms
bootstrap.CrGpDA.js
474 ms
widgets.js
127 ms
paths.CzPszg.js
471 ms
webfont.js
172 ms
logo-nzte.1453753314.svg
110 ms
a98IW2OC_normal.jpeg
198 ms
logo-nz-coa-small.1453753314.png
98 ms
bg-header-dna.1453753314.png
73 ms
landscape-crop.png
102 ms
pod-listing.png
101 ms
jR3Wv5Uwa0aGJgjSeHn45A
1277 ms
tweet-sprite.png
46 ms
logo-nz-govt.1453767291.png
30 ms
bg-trigger-m.1453753313.png
31 ms
nzteicon.CYuCnA.woff
175 ms
analytics.js
72 ms
common.9562878465e4b0ca61927e925022603a.js
20 ms
all.0d6462192a4f7fc4b3b2dcafc261095f.js
7 ms
jquery-1.9.1.42381d58e04bed1a4a6186ce94b4fc56.js
111 ms
lazyload.97093d049cc1211c8e2bd635ca5fe74c.js
10 ms
placeholder.acd37eebc242e8c1b4f4b854281aff8f.js
11 ms
subscribe.15f2dba964683c75661e70099b40f146.js
11 ms
dropdown.e9646bc11bf97805a362d87b96b735d6.js
42 ms
load.c8fb423d3ad91f7e59c6ad83751da2f3.js
31 ms
load.e5cd302d82ae5ab755948cf53f47a4cb.js
9 ms
loader.d403bb69ee4aa2b63e944ba9629257c0.js
31 ms
load.3c05994006e74884440de7a40534f650.js
31 ms
all.4ab855c77b170df6a3d255d35aaa37d2.js
32 ms
link.91b75593084498cdc915bde6cf1640aa.js
32 ms
scroll.71ce00371b7bce2c7fce932c73981b8a.js
33 ms
detector.fbef3890ca63d5aa1512a460bba86422.js
33 ms
mediaqueries.ab2c668ee6b502abb76b0f591617579e.js
34 ms
tracking.2b3b2fb4ce5f0d8b8515b2dc91be9d3d.js
34 ms
custom.42bbdb1536796fced0636382075da72e.js
33 ms
pageSelect.bdab87457e6324dbddd1869fa9feee8f.js
36 ms
feature.b8a6676de2766e65d4e4bc3ee50b4f8c.js
32 ms
collect
29 ms
collect
56 ms
templayed.e9da8f9279c308bcfe8af316beae9b47.js
13 ms
small.77acde6e19ba5febe0de5a1d1d5ef63d.js
11 ms
large.ea935628a6c7713787afb4e48960f3e7.js
11 ms
useragent.fc6201052e3e26a1e2060fbfa80c7bcc.js
10 ms
dataManager.4b47caf16b8d227b684496291e04e053.js
12 ms
sectionTracking.7434a726993d79312389fa5bbe6b4de0.js
11 ms
linkedPageTracking.7914fe2873d00bcd11f9653c5e8bec69.js
12 ms
formTracking.d854b27e5e5da87e672d0d8590312b2e.js
10 ms
pageTimer.adeb3946f30b8a2af3f2a02c516b36f9.js
18 ms
googleAnalyticsManager.5dd63908eaa0de6ddd4495799e53bcf6.js
12 ms
dynamic.36e6fbd3c8b088953208924f08729ae4.js
11 ms
storage.52273c13617fc0981a754354aaacedd4.js
7 ms
jquery.hoverIntent.212eecc7623e7f4a9cd22f9cca67d818.js
5 ms
enquire.2ec07b6a59c82650eeefd1effad4a64b.js
6 ms
twitter.1278db4601a6865bfff1794c32db9905.js
9 ms
appendAround.353c73fd225c833638ac3245bf7b3ce7.js
5 ms
jquery.phatfingaz.a0c1cdd831add3018812707dfa9c9010.js
7 ms
jquery.printernator.3413432fe4e117bbc71a15ac8fd021aa.js
6 ms
jquery.ba-tinypubsub.5c9095d319e97c76f12a0f4f14d1a0a1.js
6 ms
jquery.lazyload.1.8.2.2810e1add56422e61c7722c1190b5c28.js
8 ms
jquery.placeholdit.7d68ec83bc80117c0af5aeb9ae28869e.js
10 ms
jquery.ba-throttle-debounce.min.d366b139f754022a38322dbd9d5435d5.js
9 ms
jquery.easing.1.3.233ecbe15e84a77a748076bdff031ff7.js
11 ms
jquery.lazyscroll.4317260e22856a2d262d07920f25f91c.js
6 ms
loading.1453753314.gif
15 ms
goal-tracking.ashx
115 ms
abs-haka_LandscapeCrop.jpg.width.400.ashx
22 ms
extrawhiteone-v3_LandscapeCrop.jpg.width.400.ashx
6 ms
page1_mihi_largeImage_LandscapeCrop.jpg.width.400.ashx
17 ms
42-38849618_LandscapeCrop.jpg.width.200.ashx
14 ms
mobile.6e6ab0102844aa1caf415e9286e9f43a.js
13 ms
landing.165078d7da26cd2e65630b656588ac88.js
16 ms
touch-instruct.201304141200.png
188 ms
jquery.evensteven.755a8806c632fc02f9042cf1a96aecec.js
6 ms
html5-reset-1.0.1.css
1218 ms
style-mini-form.css
1225 ms
jquery-ui-1.8.custom.css
196 ms
date-picker.css
1227 ms
modernizr-2.5.3.js
1655 ms
jquery-1.8.3.min.js
604 ms
jquery-ui-1.9.2.custom.min.js
1204 ms
timepicker.js
625 ms
form.js
622 ms
Placeholders.jquery.min.js
619 ms
fileuploader.css
620 ms
fileupload.js
814 ms
input-placeholder-value.min.js
1242 ms
pnz_204559_PodListing.jpg
6 ms
139572852__cc__PodListing.jpg
6 ms
lamb_PodListing.jpg
13 ms
kiwifruit_-_high_res_PodListing.jpg
11 ms
nzte.govt.nz 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
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
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
nzte.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
nzte.govt.nz SEO score
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 Nzte.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 Nzte.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.
nzte.govt.nz
Open Graph data is detected on the main page of NZTE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: