Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

wellington.govt.nz

Wellington City Council

Page Load Speed

10.8 sec in total

First Response

1.1 sec

Resources Loaded

9.4 sec

Page Rendered

362 ms

wellington.govt.nz screenshot

About Website

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.nz

Key Findings

We 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.

Performance Metrics

wellington.govt.nz performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value1,080 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

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

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 Optimization Overview & Recommendations

Page size can be reduced by 581.5 kB (30%)

Content Size

2.0 MB

After Optimization

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.

HTML Optimization

-87%

Potential reduce by 179.1 kB

  • Original 206.5 kB
  • After minification 176.1 kB
  • After compression 27.3 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.

Image Optimization

-3%

Potential reduce by 43.9 kB

  • Original 1.3 MB
  • After minification 1.2 MB

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.

JavaScript Optimization

-66%

Potential reduce by 227.4 kB

  • Original 342.0 kB
  • After minification 335.0 kB
  • After compression 114.6 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.

CSS Optimization

-81%

Potential reduce by 131.0 kB

  • Original 161.4 kB
  • After minification 159.3 kB
  • After compression 30.4 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.

Requests Breakdown

Number of requests can be reduced by 24 (44%)

Requests Now

54

After Optimization

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.

Accessibility Review

wellington.govt.nz accessibility score

100

Accessibility Issues

Best Practices

wellington.govt.nz best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

wellington.govt.nz SEO score

76

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: