7.8 sec in total
640 ms
6.9 sec
231 ms
Visit maps.doc.govt.nz now to see the best up-to-date Maps Doc content for New Zealand and also check out these interesting facts you probably never knew about maps.doc.govt.nz
Explore our nature with interactive mapping tools and free downloadable data.
Visit maps.doc.govt.nzWe analyzed Maps.doc.govt.nz page load time and found that the first response time was 640 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
maps.doc.govt.nz performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value9.7 s
0/100
25%
Value9.7 s
11/100
10%
Value1,000 ms
27/100
30%
Value0.766
5/100
15%
Value15.5 s
7/100
10%
640 ms
1772 ms
35 ms
205 ms
1925 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Maps.doc.govt.nz, 55% (21 requests) were made to Doc.govt.nz and 16% (6 requests) were made to Ajax.aspnetcdn.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Doc.govt.nz.
Page size can be reduced by 266.3 kB (56%)
474.8 kB
208.5 kB
In fact, the total size of Maps.doc.govt.nz main page is 474.8 kB. 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. Images take 186.5 kB which makes up the majority of the site volume.
Potential reduce by 54.8 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 54.8 kB or 76% of the original size.
Potential reduce by 70.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. Obviously, Maps Doc needs image optimization as it can save up to 70.0 kB or 38% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 106.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 106.6 kB or 62% of the original size.
Potential reduce by 34.9 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. Maps.doc.govt.nz needs all CSS files to be minified and compressed as it can save up to 34.9 kB or 80% of the original size.
Number of requests can be reduced by 14 (45%)
31
17
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Maps Doc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
maps.doc.govt.nz
640 ms
maps
1772 ms
jquery.min.js
35 ms
fonts.css
205 ms
CssMinify.aspx
1925 ms
minify_js.aspx
621 ms
hoverIntent.min.js
415 ms
jquery.onscreen.js
448 ms
jquery-ui.min.js
55 ms
jquery-ui.css
59 ms
jquery.fancybox.css
422 ms
jquery.fancybox.pack.js
1036 ms
jcarousel.min.js
899 ms
71D9488CC9E874046.css
517 ms
WebResource.axd
620 ms
WebResource.axd
481 ms
conversion.js
15 ms
analytics.js
26 ms
CssMinify.aspx
274 ms
doc-logo-black-and-white.png
329 ms
discover-outdoors-screenshot-223.jpg
1547 ms
doc-maps-devices-223.jpg
865 ms
geoportal-screenshot-223.jpg
1484 ms
img.ashx
469 ms
img.ashx
716 ms
ClearSans-Regular.woff
2620 ms
ClearSans-Bold.woff
3081 ms
collect
139 ms
153 ms
ui-bg_flat_75_ffffff_40x100.png
120 ms
collect
62 ms
icons-16.png
2941 ms
collect
12 ms
ui-icons_222222_256x240.png
54 ms
ui-bg_highlight-soft_75_cccccc_1x100.png
56 ms
ui-bg_glass_75_e6e6e6_1x400.png
56 ms
ui-icons_888888_256x240.png
58 ms
92 ms
maps.doc.govt.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
Image elements do not have [alt] attributes
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
maps.doc.govt.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
Missing source maps for large first-party JavaScript
maps.doc.govt.nz SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Maps.doc.govt.nz can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Maps.doc.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.
maps.doc.govt.nz
Open Graph description is not detected on the main page of Maps Doc. 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: