STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

lefrecce.it

lefrecce.it's public homepage, certificate and DNS checked against 31 practices and compared with 203 Trains & Public Transport sites.

Readiness index
41/100

Trains & Public Transport median 60

Ahead of
11%

of measured Trains & Public Transport sites

Practices observed
9/28

3 of 31 could not be measured

Popularity band
Top 5K

Chrome UX Report top-sites list

Measured 2026-10-23 12:00:19 UTC from one location. How we measure

Readiness by lane

Green: lefrecce.it. Thin bar: Trains & Public Transport peer median.

Enable

21/100

Peers 73

Harden

51/100

Peers 57

Accelerate

55/100

Peers 53

Recover

0/100

Peers 15

Priority fixes for lefrecce.it

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

  1. Priority 1 · Enable

    Mobile viewport configured

    Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.

    Why it matters: Without it, phones render the page at desktop width and shrink it, which makes text tiny and hard to use.

    What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.

    95% of Trains & Public Transport peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

  2. Priority 2 · Harden

    TLS 1.3 negotiated

    Observed: The TLS connection negotiated TLSv1.2.

    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.

    85% of Trains & Public Transport peers do this.

  3. Priority 3 · Enable

    XML sitemap discoverable

    Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

    What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

    66% of Trains & Public Transport peers do this.

  4. Priority 4 · Harden

    DMARC policy enforces quarantine or reject

    Observed: No DMARC record was found at _dmarc.lefrecce.it.

    What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

    40% of Trains & Public Transport peers do this.

What lefrecce.it already does well

Practices fewer than half of Trains & Public Transport peers use.

  • HSTS kept for at least a yearHSTS with a 365-day max-age covering subdomains.41% of peers
  • No render-blocking scripts in <head>Head scripts load without blocking.43% of peers

What we saw

Homepage checked
https://www.lefrecce.it/
Homepage response
HTTP 200
TLS
TLSv1.2, HTTP/2
Certificate
DigiCert, 198-day validity, expiring 2026-12-21
CDN or edge
Akamai
DNS operators
Akamai Edge DNS
HSTS
max-age 365 days, includeSubDomains, preload
Homepage HTML
0 KB, gzip
Images on homepage
0

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 9

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • Certificate has more than 14 days left
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • HTTP/2 negotiated
  • No render-blocking scripts in <head>
  • robots.txt published
  • At most one redirect to the homepage

Not measured 3

  • HTML compressed
  • Modern image formats in use
  • Offscreen images lazy-loaded

Own lefrecce.it?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Live status for this site: Status Is Down: lefrecce.it. This profile covers configuration only.

Compare with other Trains & Public Transport sites