Website readiness profile · Snapshot 23 October 2026
lastlink.com
lastlink.com's public homepage, certificate and DNS checked against 31 practices and compared with 157 Online Payment & Wallets sites.
- Readiness index
- 69/100
- Ahead of
- 55%
- Practices observed
- 20/30
- Popularity band
- Top 50K
Online Payment & Wallets median 64
of measured Online Payment & Wallets sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: lastlink.com. Thin bar: Online Payment & Wallets peer median.
Enable
92/100
Peers 72
Harden
40/100
Peers 63
Accelerate
100/100
Peers 61
Recover
0/100
Peers 6
Priority fixes for lastlink.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
HTTP requests move to HTTPS
Observed: A request to http://lastlink.com/ was not redirected to HTTPS.
Why it matters: Visitors who type the address or follow an old link start on unencrypted HTTP. A redirect moves them to the encrypted site before any cookies or form data are sent.
What to do: Add a permanent (301 or 308) redirect from every http:// URL to the same https:// URL at your CDN, load balancer or web server.
On Amazon CloudFront: Set the viewer protocol policy of each cache behaviour to Redirect HTTP to HTTPS.
95% of Online Payment & Wallets peers do this. Limit: Measured for the homepage only, from one location, at the time of the check.
Priority 2 · Harden
HSTS kept for at least a year
Observed: The homepage response did not include a Strict-Transport-Security header.
What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.
On Amazon CloudFront: Attach a response headers policy with Strict-Transport-Security to each distribution.
60% of Online Payment & Wallets peers do this.
Priority 3 · Harden
Framing restricted
Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.
What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.
On Amazon CloudFront: Set frame options in a response headers policy.
64% of Online Payment & Wallets peers do this.
Priority 4 · Harden
Content Security Policy present
Observed: The homepage response did not include a Content-Security-Policy header.
What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.
49% of Online Payment & Wallets peers do this.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
What lastlink.com already does well
Practices fewer than half of Online Payment & Wallets peers use.
- Reachable over IPv6IPv6 address published.28% of peers
- HTTP/3 advertisedHTTP/3 advertised.35% of peers
- Referrer-Policy setReferrer-Policy present.37% of peers
What we saw
- Homepage checked
- https://lastlink.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-03-26
- CDN or edge
- Amazon CloudFront
- DNS operators
- Cloudflare
- DMARC policy
- p=quarantine
- Homepage HTML
- 182 KB, br
- Images on homepage
- 69 (jpg 30, png 18, svg 9, webp 4)
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
Not observed 10
Observed 20
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Referrer-Policy set
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Modern image formats in use
- 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
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Not measured 1
- Static files cached for 30 days or more
Own lastlink.com?
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: lastlink.com. This profile covers configuration only.