Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

pages.mercury.co.nz

Join Mercury

Page Load Speed

5.7 sec in total

First Response

1.6 sec

Resources Loaded

3.5 sec

Page Rendered

638 ms

pages.mercury.co.nz screenshot

About Website

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.nz

Key Findings

We 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.

Performance Metrics

pages.mercury.co.nz performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.709

7/100

15%

TTI (Time to Interactive)

Value17.9 s

3/100

10%

Network Requests Diagram

join

1571 ms

optimized-min.css

73 ms

optimized-min.css

97 ms

mercury.main.css

152 ms

commerce.main.css

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 Optimization Overview & Recommendations

Page size can be reduced by 118.3 kB (9%)

Content Size

1.4 MB

After Optimization

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.

HTML Optimization

-87%

Potential reduce by 101.2 kB

  • Original 116.8 kB
  • After minification 93.6 kB
  • After compression 15.6 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.

Image Optimization

-0%

Potential reduce by 631 B

  • Original 229.4 kB
  • After minification 228.7 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. Pages Mercury images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 15.1 kB

  • Original 829.5 kB
  • After minification 829.5 kB
  • After compression 814.4 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.

CSS Optimization

-1%

Potential reduce by 1.3 kB

  • Original 192.0 kB
  • After minification 192.0 kB
  • After compression 190.7 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.

Requests Breakdown

Number of requests can be reduced by 33 (65%)

Requests Now

51

After Optimization

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.

Accessibility Review

pages.mercury.co.nz accessibility score

81

Accessibility Issues

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

High

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

pages.mercury.co.nz best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

pages.mercury.co.nz SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: