11.4 sec in total
483 ms
10 sec
869 ms
Welcome to mercury.co.nz homepage info - get ready to check Mercury best content for New Zealand right away, or after learning these important things about mercury.co.nz
Mercury - Leading NZ power company, also offering phone, internet & gas. Bundle your utilities & save! Call 0800 36 98 45 to sign up, or join online.
Visit mercury.co.nzWe analyzed Mercury.co.nz page load time and found that the first response time was 483 ms and then it took 10.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
mercury.co.nz performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value13.1 s
0/100
25%
Value10.9 s
6/100
10%
Value3,110 ms
2/100
30%
Value0.367
29/100
15%
Value22.8 s
1/100
10%
483 ms
1088 ms
933 ms
473 ms
709 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 54% of them (62 requests) were addressed to the original Mercury.co.nz, 9% (10 requests) were made to D.adroll.com and 4% (4 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (7.8 sec) belongs to the original domain Mercury.co.nz.
Page size can be reduced by 850.4 kB (30%)
2.8 MB
2.0 MB
In fact, the total size of Mercury.co.nz main page is 2.8 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. 70% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 91.3 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 91.3 kB or 80% of the original size.
Potential reduce by 104.4 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. Mercury images are well optimized though.
Potential reduce by 382.7 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 382.7 kB or 65% of the original size.
Potential reduce by 272.0 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. Mercury.co.nz needs all CSS files to be minified and compressed as it can save up to 272.0 kB or 83% of the original size.
Number of requests can be reduced by 53 (58%)
92
39
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mercury. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
mercury.co.nz
483 ms
www.mercury.co.nz
1088 ms
style-twonavigation.css
933 ms
Fonts.css
473 ms
WebResource.axd
709 ms
GetResource.ashx
1178 ms
ScriptResource.axd
954 ms
ScriptResource.axd
703 ms
js
707 ms
jquery.min.js
31 ms
jquery.fancybox.pack.js
950 ms
jquery.fancybox.css
951 ms
8wa.js
34 ms
ios-orientationchange-fix.js
486 ms
jquery-ui-1.10.1.custom.min.js
700 ms
jquery.pageslide_modified.js
709 ms
jquery.scrollTo-1.4.2-min.js
766 ms
jquery.localscroll-1.2.7-min.js
764 ms
jquery.flexslider-min.js
767 ms
jquery.tinyscrollbar.min.js
933 ms
init.js
944 ms
script.js
949 ms
gtm.js
64 ms
GetFile.aspx
2114 ms
mercury_logo.png
591 ms
arrow.png
590 ms
home-page-banner-v2.aspx
3888 ms
Mercury-energy-our-backyard.aspx
1929 ms
img3.jpg
1208 ms
Easy_Discount
7750 ms
Join-mercury-energy-icon-(2).png.aspx;;
4242 ms
Move-house-with-mercury-icon-(5).png.aspx;;
5276 ms
good-energy-monitor-icon-(4).png.aspx;;
4273 ms
manage-your-accout-mercury-energy-icon-(4).png.aspx;;
3772 ms
audi.jpg.aspx;;
1962 ms
mitsubishi-outlander.gif.aspx;;
3728 ms
nissan-leaf.gif.aspx;;
3967 ms
bmw-i3-charging.gif.aspx;;
4242 ms
learn-about-gem.jpg
4206 ms
gem-features.gif
4446 ms
family.jpg
4479 ms
hands.jpg
4731 ms
baby.jpg
5254 ms
latest-project.jpg
5193 ms
footer-facebook-icon.png
4713 ms
footer-twitter-icon.png
4949 ms
footer-youtube-icon.png
4966 ms
close_button.png
5180 ms
analytics.js
21 ms
fp.js
76 ms
munchkin.js
6 ms
fbds.js
114 ms
activityi;src=4503808;type=remar0;cat=remar00;ord=1;num=4972084408277;~oref=http%3A%2F%2Fwww.mercury.co.nz%2F
36 ms
munchkin.js
4 ms
visitWebPage
22 ms
collect
11 ms
collect
69 ms
TAGS=retargeting%3Dmercuryhome
1191 ms
i.cid
519 ms
offsite_event.php
24 ms
ga-audiences
49 ms
16 ms
header_drop_shadow.png
4945 ms
pixel
34 ms
ProximaNova-RegWeb.woff
5601 ms
ProximaNova-BoldWeb.woff
5143 ms
yellow_grad_bg.gif
5152 ms
U10rUQQMjxw
108 ms
-8JZJcZy8Cc
247 ms
bg-light.jpg
5170 ms
icons-sea692e76a4.png
6363 ms
platform.png
7402 ms
mini-nav-centre.png
6368 ms
button-right.png
6399 ms
0322.js
17 ms
www-embed-player-vflZsBgOl.css
143 ms
www-embed-player.js
182 ms
base.js
233 ms
MercurySans.woff
5670 ms
MercurySans-SemiBold.woff
5891 ms
MercurySans-Light.woff
6046 ms
updated.png
6762 ms
play-video.png
7355 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
22 ms
ad_status.js
73 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
79 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
92 ms
pixel
70 ms
i.match
405 ms
user1-dark.png
6221 ms
roundtrip.js
7 ms
LXKX22WDOFGJNGUH45HGBU.js
218 ms
out
11 ms
31 ms
out
6 ms
out
7 ms
out
8 ms
out
11 ms
out
14 ms
out
18 ms
out
17 ms
out
19 ms
u.php
46 ms
adsct
129 ms
23 ms
sd
5 ms
377928.gif
7 ms
sync
16 ms
in
6 ms
tap.php
181 ms
user2-dark.png
5531 ms
user3-dark.png
5624 ms
bg-dark.jpg
3936 ms
3 ms
mercury.co.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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
mercury.co.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
Missing source maps for large first-party JavaScript
mercury.co.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
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 Mercury.co.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 Mercury.co.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.
mercury.co.nz
Open Graph description is not detected on the main page of Mercury. 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: