linktr.ee

Readiness by lane

Green: linktr.ee. Thin bar: Business Tools peer median.

Priority fixes for linktr.ee

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   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.

   85% of Business Tools peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS Guide for Website Owners

2. 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 Fastly: Add the header in VCL or a header rule as described in Fastly's HSTS guide.

   45% of Business Tools peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · 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.

   61% of Business Tools peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

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.

   46% of Business Tools peers do this.

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

What linktr.ee already does well

Practices fewer than half of Business Tools peers use.

• Content Security Policy presentContent-Security-Policy present.28% of peers
• Referrer-Policy setReferrer-Policy present.28% of peers
• Modern image formats in useWebP or AVIF images detected.42% of peers

What we saw

Homepage checked

https://linktr.ee/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-11-27

CDN or edge

Fastly

Platform or framework

Next.js

DNS operators

Amazon Route 53

DMARC policy

p=reject

Homepage HTML

527 KB, gzip

Images on homepage

70 (svg 11, webp 7, avif 1)

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 Business Tools sites

• airdroid.com69
• fareharbor.com70
• infolinity.com70
• proprofs.com71
• ysense.com70

Business Tools readiness benchmark