6.7 sec in total
610 ms
5.6 sec
460 ms
Welcome to dunedin.govt.nz homepage info - get ready to check Dunedin best content for New Zealand right away, or after learning these important things about dunedin.govt.nz
This is the Dunedin City Council website homepage
Visit dunedin.govt.nzWe analyzed Dunedin.govt.nz page load time and found that the first response time was 610 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
dunedin.govt.nz performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value10.6 s
0/100
25%
Value11.0 s
6/100
10%
Value200 ms
89/100
30%
Value0.658
8/100
15%
Value16.8 s
5/100
10%
610 ms
1200 ms
190 ms
379 ms
379 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 92% of them (45 requests) were addressed to the original Dunedin.govt.nz, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Dunedin.govt.nz.
Page size can be reduced by 450.5 kB (13%)
3.6 MB
3.1 MB
In fact, the total size of Dunedin.govt.nz main page is 3.6 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. 45% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 85.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 85.4 kB or 88% of the original size.
Potential reduce by 56.8 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. Dunedin images are well optimized though.
Potential reduce by 164.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 164.6 kB or 68% of the original size.
Potential reduce by 143.8 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. Dunedin.govt.nz needs all CSS files to be minified and compressed as it can save up to 143.8 kB or 87% of the original size.
Number of requests can be reduced by 14 (30%)
47
33
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dunedin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
dunedin.govt.nz
610 ms
www.dunedin.govt.nz
1200 ms
normalize.css
190 ms
1140.css
379 ms
colorbox.css
379 ms
dcc-styles.css
576 ms
general.js
386 ms
translation.js
384 ms
js_strings.en.js
386 ms
jquery-1.8.2.min.js
802 ms
plugins.js
635 ms
jquery.content-panel-switcher.js
634 ms
jquery-ui.js
9 ms
css3-mediaqueries.js
634 ms
jquery.tmpl.min.js
635 ms
funnelback-completion.js
635 ms
refresh-script.js
763 ms
dcc-main-logo.png
761 ms
nav.png
764 ms
_search.png
766 ms
cdv2.jpg
988 ms
join-the-library.jpg
957 ms
map-isite.jpg
1326 ms
albatross1.jpg
3184 ms
sprite-search.png
363 ms
sprite.png
579 ms
calendar-arrows.png
541 ms
map-dcc.png
732 ms
Cover-Number-36.jpg
1900 ms
robbie-rocks-Adbox-432x290.jpg
916 ms
March-Booksale-2016-432x290px.jpg
1181 ms
mayor.jpg
1201 ms
transport-adbox.jpg
919 ms
whats-on.jpg
920 ms
webcam.jpg
1290 ms
dcc-footer-logo.png
1106 ms
dunedin-logo.png
1107 ms
nzgovt-logo.png
1295 ms
sprite-newsheadings.png
1267 ms
footer-big-image.jpg
1525 ms
ga.js
73 ms
weather
1481 ms
word.gif
1150 ms
overlay.png
1150 ms
border.png
1338 ms
controls.png
1339 ms
ui-bg_flat_75_ffffff_40x100.png
1410 ms
__utm.gif
10 ms
fine.jpg
191 ms
dunedin.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-*] attributes do not match their roles
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
dunedin.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
dunedin.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
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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 Dunedin.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 Dunedin.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.
dunedin.govt.nz
Open Graph description is not detected on the main page of Dunedin. 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: