Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

napier.govt.nz

Napier City Council | New Zealand

Page Load Speed

8.4 sec in total

First Response

1.4 sec

Resources Loaded

6.7 sec

Page Rendered

323 ms

napier.govt.nz screenshot

About Website

Visit napier.govt.nz now to see the best up-to-date Napier content for New Zealand and also check out these interesting facts you probably never knew about napier.govt.nz

Information on Napier's rates, rubbish and recycling, property information, council news and events, and how to contact Napier City Council.

Visit napier.govt.nz

Key Findings

We analyzed Napier.govt.nz page load time and found that the first response time was 1.4 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

napier.govt.nz performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value28.6 s

0/100

25%

SI (Speed Index)

Value31.1 s

0/100

10%

TBT (Total Blocking Time)

Value16,650 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.232

54/100

15%

TTI (Time to Interactive)

Value32.2 s

0/100

10%

Network Requests Diagram

napier.govt.nz

1379 ms

combined.css

776 ms

display_logic.css

517 ms

modernizr.custom.js

522 ms

jquery.min.js

798 ms

Our browser made a total of 171 requests to load all elements on the main page. We found that 46% of them (79 requests) were addressed to the original Napier.govt.nz, 11% (18 requests) were made to Data.napier.govt.nz and 9% (16 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Napier.govt.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (43%)

Content Size

2.9 MB

After Optimization

1.7 MB

In fact, the total size of Napier.govt.nz main page is 2.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 86.8 kB

  • Original 104.8 kB
  • After minification 95.0 kB
  • After compression 18.0 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 86.8 kB or 83% of the original size.

Image Optimization

-21%

Potential reduce by 324.3 kB

  • Original 1.6 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. Obviously, Napier needs image optimization as it can save up to 324.3 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 635.1 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 387.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 635.1 kB or 62% of the original size.

CSS Optimization

-84%

Potential reduce by 208.2 kB

  • Original 248.0 kB
  • After minification 213.5 kB
  • After compression 39.7 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. Napier.govt.nz needs all CSS files to be minified and compressed as it can save up to 208.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 77 (46%)

Requests Now

167

After Optimization

90

The browser has sent 167 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Napier. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

napier.govt.nz accessibility score

72

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

[aria-*] attributes do not have valid values

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best Practices

napier.govt.nz best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

napier.govt.nz SEO score

90

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

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 Napier.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 Napier.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 Napier. 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: