Website readiness profile · Snapshot 23 October 2026
when2meet.com
when2meet.com's public homepage, certificate and DNS checked against 31 practices and compared with 50 Work Productivity Apps sites.
- Readiness index
- 32/100
- Ahead of
- 0%
- Practices observed
- 7/29
- Popularity band
- Top 50K
Work Productivity Apps median 72
of measured Work Productivity Apps sites
2 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: when2meet.com. Thin bar: Work Productivity Apps peer median.
Enable
18/100
Peers 83
Harden
38/100
Peers 62
Accelerate
40/100
Peers 68
Recover
0/100
Peers 0
Priority fixes for when2meet.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTML compressed
Observed: The homepage HTML (45 KB) was delivered without gzip, Brotli or zstd compression.
Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.
What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.
On Amazon CloudFront: Enable Compress objects automatically on the cache behaviour.
92% of Work Productivity Apps peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.
Guide: How to Set a Website Performance Budget That Teams Can Keep
Priority 2 · Enable
Mobile viewport configured
Observed: The homepage had no viewport meta tag, so phones may render it zoomed out.
What to do: Add <meta name="viewport" content="width=device-width, initial-scale=1"> and check the layout on small screens.
96% of Work Productivity Apps peers do this.
Priority 3 · Enable
robots.txt published
Observed: No robots.txt file was returned at the site root.
What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.
92% of Work Productivity Apps peers do this.
Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes
Priority 4 · 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.
42% of Work Productivity Apps peers do this.
What we saw
- Homepage checked
- https://www.when2meet.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-01-06
- CDN or edge
- Amazon CloudFront
- DNS operators
- Amazon Route 53
- Homepage HTML
- 45 KB, uncompressed
- 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
Not observed 22
- HSTS kept for at least a year
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTTP/3 advertised
- HTML compressed
- Static files cached for 30 days or more
- robots.txt published
- XML sitemap discoverable
- Reachable over IPv6
- Canonical URL declared
- Mobile viewport configured
- Structured data present
- Social preview image set
- Page language declared
- Nameservers spread across providers
Observed 7
- HTTP requests move to HTTPS
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- HTTP/2 negotiated
- No render-blocking scripts in <head>
- Meta description written
- At most one redirect to the homepage
Not measured 2
- Modern image formats in use
- Offscreen images lazy-loaded
Own when2meet.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: when2meet.com. This profile covers configuration only.