14.8 sec in total
4.8 sec
9.8 sec
260 ms
Click here to check amazing NZX content for New Zealand. Otherwise, check out these important facts you probably never knew about nzx.com
NZX operates New Zealand capital, risk and commodity markets. We provide high quality market information, featuring real time stock quotes, market data, market news and tools to support business decis...
Visit nzx.comWe analyzed Nzx.com page load time and found that the first response time was 4.8 sec and then it took 10.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
nzx.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value8.7 s
1/100
25%
Value8.6 s
17/100
10%
Value830 ms
35/100
30%
Value0.745
6/100
15%
Value19.8 s
2/100
10%
4779 ms
1597 ms
975 ms
1319 ms
2032 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 33% of them (25 requests) were addressed to the original Nzx.com, 12% (9 requests) were made to Content.aimatch.com and 11% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Nzx.com.
Page size can be reduced by 1.3 MB (67%)
1.9 MB
625.6 kB
In fact, the total size of Nzx.com main page is 1.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. 60% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 30.2 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 4.9 kB, which is 13% 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 30.2 kB or 79% of the original size.
Potential reduce by 34.3 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, NZX needs image optimization as it can save up to 34.3 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 896.2 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 896.2 kB or 69% of the original size.
Potential reduce by 334.2 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. Nzx.com needs all CSS files to be minified and compressed as it can save up to 334.2 kB or 76% of the original size.
Number of requests can be reduced by 36 (52%)
69
33
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NZX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
nzx.com
4779 ms
application.css
1597 ms
EJSChart.css
975 ms
jquery-ui.css
1319 ms
EJSChart.js
2032 ms
application.js
3576 ms
adhub.js
1167 ms
in.js
30 ms
platform.js
80 ms
v60.js
160 ms
out_bound_analytics.js
583 ms
spritesheet.png
209 ms
nzx-logo.png
206 ms
expandable-menu-fragment.png
266 ms
fZCSdeZWYGs
184 ms
TJugP2AcEmE
241 ms
nzx_agri.png
1141 ms
price-sensitive-flag-mini.png
235 ms
invested-logo.png
241 ms
t2button-border.png
405 ms
mcclay.jpg
808 ms
Smartshares_final.jpg
525 ms
superlife-logo.png
524 ms
agrihq_logo_new-small.png
525 ms
fundsource.png
1248 ms
OpenSans-Bold-webfont.woff
810 ms
OpenSans-Semibold-webfont.woff
1226 ms
OpenSans-Regular-webfont.woff
995 ms
OpenSans-Light-webfont.woff
950 ms
footer-logo.png
1010 ms
widgets.js
151 ms
secureAnonymousFramework
95 ms
cb=gapi.loaded_0
110 ms
cb=gapi.loaded_1
158 ms
follow
240 ms
analytics.js
188 ms
em.js
638 ms
storageframe.html
116 ms
www-embed-player-vflZsBgOl.css
114 ms
www-embed-player.js
145 ms
base.js
376 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
35 ms
postmessageRelay
64 ms
collect
24 ms
m
58 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
14 ms
collect
247 ms
api.js
69 ms
core:rpc:shindig.random:shindig.sha1.js
245 ms
2536007149-postmessagerelay.js
240 ms
rs=AGLTcCM2TygKB0mUTs1bvsRYQQZWb_gy-g
67 ms
rs=AGLTcCPhDrHY2vagSjsLFOxeufqSzVU3ow
86 ms
rs=AGLTcCM2Yox_1lk51nTTwbNJK4rlySAFTA
116 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
315 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
345 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
435 ms
jot
238 ms
viewid=64296821016
169 ms
viewid=64296821016
168 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
55 ms
ad_status.js
140 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
86 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
80 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
120 ms
index.html
290 ms
viewid=64296821016
119 ms
AgriHQ_Pulse_Mrec_.jpg
235 ms
728x90_NZX0019_12-09-2015_v02_edgePreload.js
28 ms
jquery.min.js
87 ms
edge.4.0.1.min.js
82 ms
728x90_NZX0019_12-09-2015_v02_edge.js
46 ms
728x90_NZX0019_12-09-2015_v02_edgeActions.js
68 ms
jquery.min.js
31 ms
edge.4.0.1.min.js
32 ms
728x90_NZX0019_12-09-2015_v02_edge.js
17 ms
main.css
21 ms
nzx.com 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 input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
nzx.com 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
Missing source maps for large first-party JavaScript
nzx.com 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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nzx.com 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 Nzx.com 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.
nzx.com
Open Graph description is not detected on the main page of NZX. 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: