bio.site

Readiness by lane

Green: bio.site. Thin bar: Website Builders peer median.

Priority fixes for bio.site

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

1. Priority 1 · Enable

   robots.txt published

   Observed: No robots.txt file was returned at the site root.

   Why it matters: robots.txt is where crawlers look first for crawl rules and sitemap locations. Without it, they assume everything is open.

   What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

   89% of Website Builders peers do this. Limit: Only the standard location was requested, once, at the time of the check.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

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

   26% of Website Builders peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

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

4. Priority 4 · Accelerate

   Offscreen images lazy-loaded

   Observed: The homepage had 74 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   61% of Website Builders peers do this.

   Guide: Lazy Loading Without Broken Pages

What bio.site already does well

Practices fewer than half of Website Builders peers use.

• Nameservers spread across providersNameservers spread across NS1 and Squarespace DNS.5.3% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.34% of peers

What we saw

Homepage checked

https://bio.site/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-04

Platform or framework

Next.js

DNS operators

NS1, Squarespace DNS

DMARC policy

p=reject

Homepage HTML

83 KB, gzip

Images on homepage

74 (webp 74)

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

• carrd.com62
• linkcloud.ai65
• lit.link67
• sfl.gl71
• straw.page62

Website Builders readiness benchmark