Website review, no card needed
2degreesmobile.co.nz website review
Visit site (opens in a new tab)Reviewed 3 November 202644 issues · 92 checks
This review found 44 issues worth fixing on 2degreesmobile.co.nz, 18 of them high impact, across 92 checks. The most urgent: use efficient cache lifetimes. 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 231 ms |
| May 23, 2026 | 229 ms |
| May 30, 2026 | 231 ms |
| Jun 6, 2026 | 233 ms |
| Jun 13, 2026 | 237 ms |
| Jun 20, 2026 | 240 ms |
| Jun 27, 2026 | 243 ms |
| Jul 4, 2026 | 246 ms |
| Jul 11, 2026 | 246 ms |
| Jul 18, 2026 | 246 ms |
| Jul 25, 2026 | 244 ms |
| Aug 1, 2026 | 243 ms |
| Aug 8, 2026 | 244 ms |
| Aug 15, 2026 | 244 ms |
| Aug 22, 2026 | 249 ms |
| Aug 29, 2026 | 252 ms |
| Sep 5, 2026 | 254 ms |
| Sep 12, 2026 | 255 ms |
| Sep 19, 2026 | 252 ms |
| Sep 26, 2026 | 249 ms |
| Oct 3, 2026 | 245 ms |
| Oct 10, 2026 | 246 ms |
| Oct 17, 2026 | 245 ms |
| Oct 24, 2026 | 248 ms |
| Oct 31, 2026 | 249 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.7 s
1.4 s
2.1 s
2.8 s
3.5 s
4.1 s
4.8 s
5.5 s
Speed
Use efficient cache lifetimes
16.3 s · 15.7 MB71 files are served with short cache lifetimes, so returning visitors download them again (15.7 MB).
Improve image delivery
3.6 s · 9.0 MB14 images could be 9.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.6 s faster on a phone.
Reduce unused JavaScript
4.5 s · 829 KiBAbout 829 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.
Render-blocking requests
1.7 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, 2degreesmobile.co.nz and Facebook and others), adding 2.2 MB and 1.7 s of main-thread time.
Google Tag Manager adds 968 ms
968 msGoogle Tag Manager costs a phone 968 ms of main-thread work and 1.1 MB 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.
Reduce unused CSS
600 ms · 118 KiBAbout 118 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
Minify JavaScript
450 ms · 86 KiB86 KiB could be saved by minifying JavaScript.
2degreesmobile.co.nz adds 412 ms
412 ms2degreesmobile.co.nz costs a phone 412 ms of main-thread work and 675 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 250 ms. During a long task the page ignores taps.
1,889 HTML elements
The page has 1,889 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 70 KiBPolyfills for old browsers add 70 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 202 ms
202 msYour server sent the HTML in 202 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 49.7 s
49.7 sYour largest element takes 49.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Ready to enter the Data Piñataverse? Play on any network. J…”.
Time to Interactive: 51.9 s
51.9 sThe page becomes fully interactive after 51.9 s. Good is under 3.8 s.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 701 ms
701 msScripts block taps and scrolling for 701 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 218 ms
218 msReal visitors wait 218 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.12
0.12For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.122
0.122The layout shifts by 0.122 while loading, so content jumps under the reader's thumb. Good is under 0.1.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 231 ms to 249 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 573 ms
573 msReal visitors wait 573 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 17.0 MB in 129 requests
17.0 MBYour homepage downloads 17.0 MB in 129 requests on a phone: images 14.6 MB (43), scripts 2.1 MB (43) and stylesheets 146 KiB (6). Under 2 MB keeps phones on slow connections fast.
12 images over 500 KB
12 images weigh 12.2 MB together. On a phone connection a single image that size takes seconds.
8 images far larger than shown
3.9 MB8 images are downloaded at several times the size a phone draws them, for example Data-Pinata-Banner-2026.png at 1,408 px wide, shown at 340 px. Resized copies would save about 3.9 MB.
13 images in older formats
13 images (8.7 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
12 images below the first screen load straight away
12 images further down the page (7.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
Data-Pinata-Banner-2026.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 4.8 g of CO₂ per visit
4.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.81 g of CO₂e: 577.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must be contained by particular parents (4 elements)
Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.
ARIA roles used must conform to valid values (1 element)
ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (4 elements)
Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4, h4 → h6 and h4 → h6), which makes the page harder to scan with a screen reader.
<td> elements in a large <table> do not have table headers.
<td> elements in a large <table> do not have table headers. (11 elements).
2 checks passed
Every image has alt text
All 50 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
253 internal links, 18 external
The homepage links to 253 pages on 2degreesmobile.co.nz and 18 external pages.
7 checks passed
Meta description: 108 characters
Your meta description is 108 characters: “Check out our Pay Monthly, Prepay & Business mobile plans, buy the latest phone or connect to our broadband.”.
One H1 headline
Your main headline reads: “Welcome to the Fight for Fair”.
Title: 60 characters
Your title is a healthy 60 characters: “2degrees - Best Mobile & Broadband Plans for Home & Business”.
Canonical URL set
The canonical URL is https://www.2degrees.nz/.
Structured data in place
Structured data found: Corporation and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.2degrees.nz/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.2degrees.nz/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
3 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (4,948 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.2degrees.nz/broadband/fibre-copper-broadband is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 94 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://static.cloudflareinsights.com/beacon.min.js/vce701823e78c4301a35b7e07294d87301792088814092'…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
17 of 18 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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 4,100 words of copy
The homepage carries about 4,100 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “T&Cs apply”.
26 calls to action
The homepage has 26 calls to action, for example “Shop Apple”, “Shop Samsung” and “Shop OPPO”.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
18 other companies contacted
Loading the homepage contacts 18 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 2degreesmobile.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
- CMS
- Drupal
- Hosting
- Two Degrees Networks Limited
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on 2degreesmobile.co.nz, including 24 speed issues, 2 SEO issues and 1 conversion gap. 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.