telstra.com.au

Readiness by lane

Green: telstra.com.au. Thin bar: Telecommunications & Internet peer median.

Priority fixes for telstra.com.au

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 18 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.

   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 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 300 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.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 18 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 1 external script 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 telstra.com.au already does well

Practices fewer than half of Telecommunications & Internet peers use.

• Nameservers spread across providersNameservers spread across more than one operator.16% of peers
• Reachable over IPv6IPv6 address published.33% of peers

What we saw

Homepage checked

https://www.telstra.com.au/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 396-day validity, expiring 2027-03-19

CDN or edge

Amazon CloudFront

Platform or framework

Adobe Experience Manager

DNS operators

Akamai Edge DNS, plus 1 self-run or other nameserver domain

HSTS

max-age 365 days

DMARC policy

p=reject

Homepage HTML

302 KB, gzip

Images on homepage

18 (jpg 20, png 9)

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

• airtel.co.tz68
• orange.es69
• pisowifipause.ph69
• sfr.fr69
• turkcell.com.tr69

Telecommunications & Internet readiness benchmark