telia.fi

Readiness by lane

Green: telia.fi. Thin bar: Telecommunications & Internet peer median.

Priority fixes for telia.fi

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   81% of Telecommunications & Internet peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

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

   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.

   52% of Telecommunications & Internet peers do this.

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

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 10 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.

   Guide: Lazy Loading Without Broken Pages

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 3 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.

   37% of Telecommunications & Internet peers do this.

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

What telia.fi already does well

Practices fewer than half of Telecommunications & Internet peers use.

• CAA records limit who can issue certificatesCAA record present.15% of peers
• Nameservers spread across providersNameservers spread across more than one operator.16% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.41% of peers

What we saw

Homepage checked

https://www.telia.fi/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Telia Finland Oyj, 365-day validity, expiring 2027-01-07

DNS operators

3 self-run or other nameserver domains

HSTS

max-age 365 days

DMARC policy

p=reject

Homepage HTML

149 KB, gzip

Images on homepage

10 (gif 6, jpg 3, svg 1)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Telecommunications & Internet sites

• digimobil.es72
• niointernet.com.br73
• tele2.se73
• three.co.uk74
• virginmedia.com73

Telecommunications & Internet readiness benchmark