Website readiness profile · Snapshot 23 October 2026
one.nz
one.nz's public homepage, certificate and DNS checked against 31 practices and compared with 285 Telecommunications & Internet sites.
- Readiness index
- 61/100
- Ahead of
- 32%
- Practices observed
- 17/31
- Popularity band
- Top 50K
Telecommunications & Internet median 67
of measured Telecommunications & Internet sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: one.nz. Thin bar: Telecommunications & Internet peer median.
Enable
87/100
Peers 82
Harden
75/100
Peers 61
Accelerate
15/100
Peers 57
Recover
0/100
Peers 16
Priority fixes for one.nz
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (166 KB) was delivered without gzip, Brotli or zstd compression.
Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.
What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.
On Amazon CloudFront: Enable Compress objects automatically on the cache behaviour.
90% of Telecommunications & Internet peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Guide: How to Set a Website Performance Budget That Teams Can Keep
Priority 2 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
On Amazon CloudFront: Choose HTTP/2 (or HTTP/2 and HTTP/3) as supported versions on the distribution.
72% of Telecommunications & Internet peers do this.
Priority 3 · Accelerate
Static files cached for 30 days or more
Observed: A same-site stylesheet or script was cacheable for 1800 seconds, short of the 30-day benchmark.
What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.
41% of Telecommunications & Internet peers do this.
Priority 4 · Accelerate
Offscreen images lazy-loaded
Observed: The homepage had 30 images and none used loading="lazy".
What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.
66% of Telecommunications & Internet peers do this.
What one.nz already does well
Practices fewer than half of Telecommunications & Internet peers use.
- Content Security Policy presentContent-Security-Policy present.48% of peers
What we saw
- Homepage checked
- https://one.nz/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3
- Certificate
- DigiCert, 364-day validity, expiring 2027-01-06
- CDN or edge
- Amazon CloudFront
- DNS operators
- 1 self-run or other nameserver domain
- HSTS
- max-age 730 days
- DMARC policy
- p=reject
- Homepage HTML
- 166 KB, uncompressed
- Images on homepage
- 30 (png 23)
Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.
Stack and providers
Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.
All 31 checks
Select a gap for the method and fix. How each check works
Not observed 14
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- Reachable over IPv6
- Social preview image set
- Nameservers spread across providers
Observed 17
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Modern image formats in use
- robots.txt published
- XML sitemap discoverable
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Structured data present
- Page language declared
- At most one redirect to the homepage
Own one.nz?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: one.nz. This profile covers configuration only.