Website review, no card needed
mercury.co.nz website review
Visit site (opens in a new tab)Reviewed 18 November 202629 issues · 77 checks
This review found 29 issues worth fixing on mercury.co.nz, 7 of them high impact, across 77 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.4 s |
| Nov 14, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 159 ms |
| Jun 6, 2026 | 156 ms |
| Jun 13, 2026 | 156 ms |
| Jun 20, 2026 | 156 ms |
| Jun 27, 2026 | 153 ms |
| Jul 4, 2026 | 153 ms |
| Jul 11, 2026 | 149 ms |
| Jul 18, 2026 | 147 ms |
| Jul 25, 2026 | 146 ms |
| Aug 1, 2026 | 146 ms |
| Aug 8, 2026 | 150 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 159 ms |
| Aug 29, 2026 | 164 ms |
| Sep 5, 2026 | 172 ms |
| Sep 12, 2026 | 179 ms |
| Sep 19, 2026 | 187 ms |
| Sep 26, 2026 | 192 ms |
| Oct 3, 2026 | 195 ms |
| Oct 10, 2026 | 197 ms |
| Oct 17, 2026 | 202 ms |
| Oct 24, 2026 | 207 ms |
| Oct 31, 2026 | 211 ms |
| Nov 7, 2026 | 207 ms |
| Nov 14, 2026 | 199 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.7 s
3.0 s
Speed
Reduce unused JavaScript
2.7 s · 747 KiBAbout 747 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 368 KiB13 files are served with short cache lifetimes, so returning visitors download them again (368 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and ContentSquare and others), adding 1.3 MB and 1.0 s of main-thread time.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 538 ms
538 msGoogle Tag Manager costs a phone 538 ms of main-thread work and 677 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
550 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 203 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 37 KiB37 KiB could be saved by minifying JavaScript.
Legacy JavaScript
50 ms · 25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Improve image delivery
24 KiB1 image could be 24 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1 checks passed
Server response: 375 ms
375 msYour server sent the HTML in 375 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.2 s
14.2 sYour largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s.
Time to Interactive: 16.8 s
16.8 sThe page becomes fully interactive after 16.8 s. Good is under 3.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 159 ms to 199 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 520 ms
520 msScripts block taps and scrolling for 520 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.117
0.117The layout shifts by 0.117 while loading, so content jumps under the reader's thumb. Good is under 0.1.
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 195 ms
195 msReal visitors wait 195 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 422 ms
422 msReal visitors wait 422 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 40% faster for real visitors
-40%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.4 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.3 MB in 110 requests
2.3 MBYour homepage downloads 2.3 MB in 110 requests on a phone: scripts 1.8 MB (42), images 211 KiB (9) and fonts 136 KiB (5). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.66 g of CO₂e: 79.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 5 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 4 problems
Structured data found (ImageObject, Organization, Service and SoftwareApplication) but with 4 problems, for example “Service: no offers (price) block”.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
53 internal links, 7 external
The homepage links to 53 pages on mercury.co.nz and 7 external pages.
6 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Mercury - Leading NZ power company, also offering phone, internet & gas. Bundle your utilities & save! Call 0800 36 98 …”.
Title: 65 characters
Your title is a healthy 65 characters: “Power Company - NZ Gas, Electricity & Internet Provider | Mercury”.
Canonical URL set
The canonical URL is https://www.mercury.co.nz/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.mercury.co.nz/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (435 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.mercury.co.nz/llms.txt (106 KiB, 559 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a meta description
https://www.mercury.co.nz/help-and-support/consumer-care-and-support and https://www.mercury.co.nz/terms-conditions/privacy-policy use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://www.mercury.co.nz/help-and-support, https://www.mercury.co.nz/electricity, https://www.mercury.co.nz/gas, https://www.mercury.co.nz/broadband, https://www.mercury.co.nz/mobile and https://www.mercury.co.nz/moving-house and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.mercury.co.nz/terms-conditions has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
2 checks passed
Tap targets are thumb-sized
7 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 222 words
The homepage has only about 222 words of visible text; thin pages give Google and first-time buyers little to go on.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Terms and eligibility apply” and “JOIN US”.
13 calls to action
The homepage has 13 calls to action, for example “Join”, “Contact Us” and “Terms and eligibility apply”.
1 short form
A short form (1 field at most) is right on the homepage.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at mercury.co.nz, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Hosting
- Vercel
Hiring
- Hiring
- 74 open roles
- Teams
- Engineering (17), People (8), Product (8), Sales & Partnerships (8)
- Job board
- greenhouse
Company
- Employees
- 4,224
- Founded
- 1999
- Headquarters
- Auckland
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on mercury.co.nz, including 13 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.