7.2 sec in total
609 ms
6.4 sec
220 ms
Visit treasury.govt.nz now to see the best up-to-date Treasury content for New Zealand and also check out these interesting facts you probably never knew about treasury.govt.nz
The Treasury is New Zealand's lead advisor to the Government on economic and financial policy.
Visit treasury.govt.nzWe analyzed Treasury.govt.nz page load time and found that the first response time was 609 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
treasury.govt.nz performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value10.5 s
0/100
25%
Value10.4 s
8/100
10%
Value360 ms
72/100
30%
Value0.001
100/100
15%
Value8.1 s
42/100
10%
609 ms
2947 ms
1219 ms
820 ms
416 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 93% of them (41 requests) were addressed to the original Treasury.govt.nz, 5% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Treasury.govt.nz.
Page size can be reduced by 129.7 kB (40%)
321.0 kB
191.3 kB
In fact, the total size of Treasury.govt.nz main page is 321.0 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. 25% of websites need less resources to load. Images take 197.0 kB which makes up the majority of the site volume.
Potential reduce by 86.9 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 14.8 kB, which is 14% 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 86.9 kB or 81% of the original size.
Potential reduce by 42.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. Obviously, Treasury needs image optimization as it can save up to 42.8 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 34 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 21 (50%)
42
21
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Treasury. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
treasury.govt.nz
609 ms
www.treasury.govt.nz
2947 ms
base-cachekey5551.css
1219 ms
ploneglossary_popup-cachekey9889.css
820 ms
mtv-plone-cols-cachekey5046.css
416 ms
body-cachekey1137.css
1019 ms
treasury.theme.2012-cachekey1393.css
1023 ms
jquery-cachekey9542.js
1617 ms
ie5fixes-cachekey6069.js
1027 ms
dragdropreorder-cachekey0254.js
1201 ms
fullscreenmode-cachekey3433.js
1226 ms
input-label-cachekey9397.js
1027 ms
ploneglossary-cachekey5978.js
1037 ms
show_menu-cachekey7868.js
2225 ms
ga.js
71 ms
bg-logo-trsy.gif
202 ms
input_background.gif
204 ms
menu_background.png
206 ms
image_icon
203 ms
image_icon
205 ms
image_icon
206 ms
i-info.gif
402 ms
mail_icon.gif
406 ms
print_icon.gif
413 ms
slideshow-affordingourfuture.jpg
823 ms
investmentstatement.gif
623 ms
image_mini
1359 ms
image_mini
610 ms
image_mini
621 ms
image_mini
623 ms
image_mini
816 ms
image_mini
836 ms
image_preview
835 ms
image_preview
836 ms
image_preview
1027 ms
image_preview
1029 ms
image_preview
1048 ms
image_preview
1045 ms
twitter_icon.png
1045 ms
calendar-icon-new.gif
1231 ms
spinner.gif
1227 ms
widgets.js
21 ms
i-bullet-divider.gif
1207 ms
__utm.gif
12 ms
treasury.govt.nz accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
treasury.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
treasury.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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Treasury.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 Treasury.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.
treasury.govt.nz
Open Graph description is not detected on the main page of Treasury. 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: