5.7 sec in total
1.6 sec
3.5 sec
638 ms
Welcome to pages.mercury.co.nz homepage info - get ready to check Pages Mercury best content for New Zealand right away, or after learning these important things about pages.mercury.co.nz
Visit pages.mercury.co.nzWe analyzed Pages.mercury.co.nz page load time and found that the first response time was 1.6 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
pages.mercury.co.nz performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value15.5 s
0/100
25%
Value11.7 s
4/100
10%
Value900 ms
31/100
30%
Value0.709
7/100
15%
Value17.9 s
3/100
10%
1571 ms
73 ms
97 ms
152 ms
116 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Pages.mercury.co.nz, 5% (3 requests) were made to Googletagmanager.com and 5% (3 requests) were made to Mercury.co.nz. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Mercury.co.nz.
Page size can be reduced by 118.3 kB (9%)
1.4 MB
1.2 MB
In fact, the total size of Pages.mercury.co.nz main page is 1.4 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. 55% of websites need less resources to load. Javascripts take 829.5 kB which makes up the majority of the site volume.
Potential reduce by 101.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 23.3 kB, which is 20% 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 101.2 kB or 87% of the original size.
Potential reduce by 631 B
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. Pages Mercury images are well optimized though.
Potential reduce by 15.1 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. This website has mostly compressed JavaScripts.
Potential reduce by 1.3 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. Pages.mercury.co.nz has all CSS files already compressed.
Number of requests can be reduced by 33 (65%)
51
18
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pages 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 23 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
join
1571 ms
optimized-min.css
73 ms
optimized-min.css
97 ms
mercury.main.css
152 ms
commerce.main.css
116 ms
VisitorIdentification.js
866 ms
evergage.min.js
24 ms
adrum.js
860 ms
jquery.min.js
30 ms
conversion.js
84 ms
embed.js
41 ms
optimized-min.js
55 ms
optimized-min.js
17 ms
optimized-min.js
27 ms
optimized-min.js
45 ms
optimized-min.js
53 ms
optimized-min.js
41 ms
mercury.vendor.js
51 ms
mercury.main.js
61 ms
commerce.main.js
93 ms
gtm.js
240 ms
join-wonders-mobile-hero.jpg
211 ms
custom-logo.png
312 ms
samsung-montage-500x500-grey.jpg
210 ms
6_months_braodband_free.jpg
238 ms
gas_get_a_bundled_discount.jpg
209 ms
woman-on-mobile.jpg
209 ms
mcy_play_store.png
209 ms
mcy_app_store.png
235 ms
mcy_social_linkedin.svg
236 ms
mcy_social_instagram.svg
234 ms
mcy_social_facebook.svg
236 ms
include.js
341 ms
mcy_search_icon.svg
215 ms
mcy_icons_close.svg
290 ms
broadband-blue.svg
289 ms
gas-blue.svg
1187 ms
mobile-blue.svg
285 ms
person-yellow.svg
288 ms
gift-yellow.svg
286 ms
energy-yellow.svg
318 ms
mcy_chat_button.svg
320 ms
268 ms
BryantCondensed-Medium.ttf
105 ms
BryantCondensed-Regular.ttf
105 ms
BryantCondensed-Light.ttf
105 ms
BryantCondensed-Bold.ttf
118 ms
js
57 ms
destination
123 ms
fbevents.js
122 ms
ig.js
225 ms
180 ms
activityi;src=4503808;type=sitewide;cat=fcbsi0;ord=1;num=4388546325639;u=https%3A%2F%2Fwww.mercury.co.nz%2Fjoin;npa=0;auiddc=2140466916.1710074888;pscdl=noapi;gtm=45fe4360z8898323302za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.mercury.co.nz%2Fjoin
94 ms
config
262 ms
trustpower-customscript.js
104 ms
src=4503808;type=sitewide;cat=fcbsi0;ord=1;num=4388546325639;u=https%3A%2F%2Fwww.mercury.co.nz%2Fjoin;npa=0;auiddc=*;pscdl=noapi;gtm=45fe4360z8898323302za201;gcd=13l3l3l3l1;dma=0;epver=2;~oref=https%3A%2F%2Fwww.mercury.co.nz%2Fjoin
77 ms
pages.mercury.co.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Links do not have a discernible 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.
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.
pages.mercury.co.nz best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
pages.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pages.mercury.co.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 Pages.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.
pages.mercury.co.nz
Open Graph description is not detected on the main page of Pages 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: