au.com

Readiness by lane

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

Priority fixes for au.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 69 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

   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

3. Priority 3 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for au.com, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   15% of Telecommunications & Internet peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Harden

   security.txt published

   Observed: No valid /.well-known/security.txt with a Contact field was returned.

   What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

   13% of Telecommunications & Internet peers do this.

   Guide: A Practical Website Health Check for Owners

What au.com already does well

Practices fewer than half of Telecommunications & Internet peers use.

• Static files cached for 30 days or moreLong-lived caching on static files.41% of peers
• Content Security Policy presentContent-Security-Policy present.48% of peers

What we saw

Homepage checked

https://www.au.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 396-day validity, expiring 2027-02-06

Platform or framework

Adobe Experience Manager

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days

DMARC policy

p=reject

Homepage HTML

137 KB, br

Images on homepage

69 (png 46, jpg 27)

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

• cricketwireless.com76
• entel.pe76
• fizz.ca77
• jazztel.com77
• telekom.si77

Telecommunications & Internet readiness benchmark