lit.link

Readiness by lane

Green: lit.link. Thin bar: Website Builders peer median.

Priority fixes for lit.link

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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 Next.js: Add the header in the headers() option of next.config.js for all routes.

   26% of Website Builders peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. 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.

   71% of Website Builders peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

3. Priority 3 · Enable

   At most one redirect to the homepage

   Observed: The homepage was reached after 2 redirects.

   What to do: Point every alternate address (http, www or apex, old paths) straight to the final URL in a single redirect.

   97% of Website Builders peers do this.

   Guide: Technical SEO Audit: A Practical Owner’s Guide

4. Priority 4 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   34% of Website Builders peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

What lit.link already does well

Practices fewer than half of Website Builders peers use.

• HTTP/3 advertisedHTTP/3 advertised.29% of peers
• Referrer-Policy setReferrer-Policy present.29% of peers
• X-Content-Type-Options: nosniffnosniff header present.39% of peers

What we saw

Homepage checked

https://lit.link/

Homepage response

HTTP 200, after 2 redirects

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-11-28

CDN or edge

Google edge

Platform or framework

Next.js

DNS operators

Xserver/Value-Domain DNS

DMARC policy

p=quarantine

Homepage HTML

175 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

Compare with other Website Builders sites

• bio.site62
• linkcloud.ai65
• neocities.org73
• sfl.gl71
• wfolio.ru74

Website Builders readiness benchmark