STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

xl.co.id

xl.co.id's public homepage, certificate and DNS checked against 31 practices and compared with 285 Telecommunications & Internet sites.

Readiness index
84/100

Telecommunications & Internet median 67

Ahead of
94%

of measured Telecommunications & Internet sites

Practices observed
25/31

0 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:40:52 UTC from one location. How we measure

Readiness by lane

Green: xl.co.id. Thin bar: Telecommunications & Internet peer median.

Enable

92/100

Peers 82

Harden

83/100

Peers 61

Accelerate

75/100

Peers 57

Recover

100/100

Peers 16

Priority fixes for xl.co.id

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 74 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 Cloudflare: Cloudflare Polish can convert images to WebP.

    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.

  2. Priority 2 · Enable

    Social preview image set

    Observed: The homepage had no og:image, so shared links may show without a preview image.

    What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.

    59% of Telecommunications & Internet peers do this.

  3. Priority 3 · Harden

    CAA records limit who can issue certificates

    Observed: No CAA record was found for xl.co.id, 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.

    On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

    15% of Telecommunications & Internet peers do this.

  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.

    On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

    13% of Telecommunications & Internet peers do this.

What xl.co.id 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
  • Certificate lifetime of 100 days or lessShort-lived 90-day certificate from Google Trust Services, already inside the 2027 limit.28% of peers
  • Reachable over IPv6IPv6 address published.33% of peers

What we saw

Homepage checked
https://www.xl.co.id/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2026-12-28
CDN or edge
Cloudflare
Platform or framework
Next.js
DNS operators
2 self-run or other nameserver domains
HSTS
max-age 365 days
DMARC policy
p=quarantine
Homepage HTML
272 KB, br
Images on homepage
74 (jpg 49, png 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

Observed 25

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTML compressed
  • Static files cached for 30 days or more
  • Offscreen images lazy-loaded
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Page language declared
  • At most one redirect to the homepage
  • Nameservers spread across providers

Own xl.co.id?

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: xl.co.id. This profile covers configuration only.

Compare with other Telecommunications & Internet sites