Website readiness profile · Snapshot 23 October 2026
yousee.dk
yousee.dk's public homepage, certificate and DNS checked against 31 practices and compared with 285 Telecommunications & Internet sites.
- Readiness index
- 63/100
- Ahead of
- 40%
- Practices observed
- 19/31
- Popularity band
- Top 50K
Telecommunications & Internet median 67
of measured Telecommunications & Internet sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: yousee.dk. Thin bar: Telecommunications & Internet peer median.
Enable
67/100
Peers 82
Harden
63/100
Peers 61
Accelerate
58/100
Peers 57
Recover
100/100
Peers 16
Priority fixes for yousee.dk
Ordered by impact and by how common each practice is among peers.
Priority 1 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected HTTP/1.1 instead of HTTP/2.
Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
72% of Telecommunications & Internet peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
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.
81% of Telecommunications & Internet peers do this.
Priority 3 · Harden
HSTS kept for at least a year
Observed: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.
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.
54% of Telecommunications & Internet peers do this.
Priority 4 · 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.
83% of Telecommunications & Internet peers do this.
Guide: XML Sitemap Guide: Include Only URLs You Stand Behind
What yousee.dk already does well
Practices fewer than half of Telecommunications & Internet peers use.
- DNSSEC signedDNSSEC delegation (DS record) present.13% of peers
- Nameservers spread across providersNameservers spread across more than one operator.16% of peers
- Referrer-Policy setReferrer-Policy present.33% of peers
What we saw
- Homepage checked
- https://yousee.dk/
- Homepage response
- HTTP 200
- TLS
- TLSv1.2
- Certificate
- SSL Corporation, 197-day validity, expiring 2027-02-28
- DNS operators
- 4 self-run or other nameserver domains
- HSTS
- max-age 180 days
- DMARC policy
- p=reject
- Homepage HTML
- 439 KB, br
- Images on homepage
- 33 (svg 21, png 6, 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 12
- HSTS kept for at least a year
- TLS 1.3 negotiated
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- security.txt published
- HTTP/2 negotiated
- HTTP/3 advertised
- Static files cached for 30 days or more
- XML sitemap discoverable
- Reachable over IPv6
- Structured data present
- Social preview image set
Observed 19
- HTTP requests move to HTTPS
- Certificate has more than 14 days left
- DNSSEC signed
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTML compressed
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- Canonical URL declared
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
- Nameservers spread across providers
Own yousee.dk?
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: yousee.dk. This profile covers configuration only.