10.8 sec in total
1.1 sec
9.4 sec
362 ms
Click here to check amazing Wellington content for New Zealand. Otherwise, check out these important facts you probably never knew about wellington.govt.nz
Visit wellington.govt.nzWe analyzed Wellington.govt.nz page load time and found that the first response time was 1.1 sec and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
wellington.govt.nz performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value5.4 s
20/100
25%
Value6.4 s
40/100
10%
Value1,080 ms
25/100
30%
Value0.033
100/100
15%
Value9.4 s
31/100
10%
1086 ms
403 ms
670 ms
1115 ms
218 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 97% of them (56 requests) were addressed to the original Wellington.govt.nz, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Wellington.govt.nz.
Page size can be reduced by 581.5 kB (30%)
2.0 MB
1.4 MB
In fact, the total size of Wellington.govt.nz main page is 2.0 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. 30% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 179.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.3 kB, which is 15% 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 179.1 kB or 87% of the original size.
Potential reduce by 43.9 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. Wellington images are well optimized though.
Potential reduce by 227.4 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 227.4 kB or 66% of the original size.
Potential reduce by 131.0 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. Wellington.govt.nz needs all CSS files to be minified and compressed as it can save up to 131.0 kB or 81% of the original size.
Number of requests can be reduced by 24 (44%)
54
30
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wellington. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
wellington.govt.nz
1086 ms
VisitorIdentification.js
403 ms
wcc-14.0.min.css
670 ms
wcc-14.0.min.js
1115 ms
WebResource.axd
218 ms
ga.js
174 ms
list-bullet.png
205 ms
link-external.png
206 ms
nav-main-pattern.png
215 ms
quick-search.png
212 ms
nav-main-arrow-right-long-xsmall.png
370 ms
spacer.gif
396 ms
banner-weather-status-light.png
432 ms
banner-arrow-r.png
408 ms
banner-arrow-diag.png
428 ms
ajax-loader-dark.gif
433 ms
spacer43.png
574 ms
karori-carou.jpg
1861 ms
arrow-read-more.png
635 ms
nix_carousel.jpg
2074 ms
give-back-shift-forward-carousel.jpg
1945 ms
phlegm-carousel.jpg
1978 ms
wellymyway-carousel.jpg
1627 ms
film-museum-caro.png
2017 ms
zephyrometer-carousel.jpg
2107 ms
guitar.jpg
2568 ms
footer-pattern.png
2155 ms
social-mobile-facebook.png
2301 ms
social-mobile-flickr.png
2340 ms
social-mobile-twitter.png
2357 ms
social-mobile-youtube.png
2366 ms
footer-map-icon.png
2364 ms
spacer125.png
2508 ms
footer-links-arrow.png
2541 ms
link-external-dark.png
2560 ms
footer-apw-new.png
2601 ms
mega-ratesproperty.jpg
3471 ms
mega-parking.jpg
2844 ms
mega-environment.jpg
3127 ms
mega-community.jpg
4095 ms
mega-consents.jpg
3081 ms
mega-howcan.jpg
3123 ms
__utm.gif
12 ms
c6206d3d-1ef8-44ad-96fa-c25e22252eb0.woff
3640 ms
4d888997-2061-451b-8569-6cee195e9915.woff
4620 ms
11398868-5e58-467f-86d1-650e10dd998a.woff
3666 ms
summer-city-mega.jpg
5456 ms
mega-haveyoursay.jpg
3885 ms
mega-yourcouncil.jpg
4447 ms
mega-about.jpg
4513 ms
summer-web.jpg
6664 ms
owb-brent-lg.jpg
4490 ms
img_3310%20-%20crop.jpg
5101 ms
footer-map-xxlarge.jpg
4951 ms
carousel-controls.png
206 ms
carousel-pager.png
207 ms
nav-main-arrow-left.png
212 ms
b-grey-3-80.png
207 ms
wellington.govt.nz accessibility score
wellington.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
wellington.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 Wellington.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 Wellington.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.
wellington.govt.nz
Open Graph description is not detected on the main page of Wellington. 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: