virginmedia.com

Readiness by lane

Green: virginmedia.com. Thin bar: Telecommunications & Internet peer median.

Priority fixes for virginmedia.com

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Accelerate

   Modern image formats in use

   Observed: The homepage had 26 images and none used WebP or AVIF.

   Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   On Next.js: The next/image component serves optimized formats automatically.

   52% of Telecommunications & Internet peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

2. Priority 2 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Next.js: Add it in next.config.js headers().

   68% of Telecommunications & Internet peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 2 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   37% of Telecommunications & Internet peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Next.js: Next.js documents nonce-based CSP with middleware.

   48% of Telecommunications & Internet peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What virginmedia.com already does well

Practices fewer than half of Telecommunications & Internet peers use.

• HTTP/3 advertisedHTTP/3 advertised.13% of peers
• CAA records limit who can issue certificatesCAA limits issuance to globalsign.com.15% of peers
• Referrer-Policy setReferrer-Policy present.33% of peers

What we saw

Homepage checked

https://www.virginmedia.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 199-day validity, expiring 2026-11-28

CDN or edge

Google edge

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

672 KB, gzip

Images on homepage

26 (png 5, svg 1)

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

Compare with other Telecommunications & Internet sites

• digimobil.es72
• doctorsim.com72
• niointernet.com.br73
• tele2.se73
• telia.fi73

Telecommunications & Internet readiness benchmark