Website readiness profile · Snapshot 23 October 2026
finishers.com
finishers.com's public homepage, certificate and DNS checked against 31 practices and compared with 387 Events & Online Ticketing sites.
- Readiness index
- 76/100
- Ahead of
- 82%
- Practices observed
- 21/31
- Popularity band
- Top 50K
Events & Online Ticketing median 63
of measured Events & Online Ticketing sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: finishers.com. Thin bar: Events & Online Ticketing peer median.
Enable
85/100
Peers 78
Harden
65/100
Peers 57
Accelerate
90/100
Peers 59
Recover
0/100
Peers 7
Priority fixes for finishers.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for finishers.com was p=none, which asks receivers to take no action on failing mail.
Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.
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.
44% of Events & Online Ticketing peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.
Priority 2 · Enable
Canonical URL declared
Observed: The homepage did not declare a canonical URL.
What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.
65% of Events & Online Ticketing 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 Next.js: Add it in next.config.js headers().
52% of Events & Online Ticketing 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.
On Next.js: Next.js documents nonce-based CSP with middleware.
30% of Events & Online Ticketing peers do this.
Guide: Payment Security and PCI DSS: What Website Owners Need to Know
What finishers.com already does well
Practices fewer than half of Events & Online Ticketing peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.9% of peers
- CAA records limit who can issue certificatesCAA limits issuance to globalsign.com, letsencrypt.org, pki.goog and others.11% of peers
- No render-blocking scripts in <head>Head scripts load without blocking.35% of peers
What we saw
- Homepage checked
- https://www.finishers.com/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Let's Encrypt, 89-day validity, expiring 2026-12-07
- CDN or edge
- Vercel
- Platform or framework
- Next.js
- DNS operators
- 1 self-run or other nameserver domain
- HSTS
- max-age 730 days
- DMARC policy
- p=none
- Homepage HTML
- 169 KB, br
- Images on homepage
- 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
Not observed 10
Observed 21
- 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
- CAA records limit who can issue certificates
- DNSSEC signed
- HTTP/2 negotiated
- HTML compressed
- Static files cached for 30 days or more
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- Meta description written
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- At most one redirect to the homepage
Own finishers.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: finishers.com. This profile covers configuration only.