sfl.gl

Readiness by lane

Green: sfl.gl. Thin bar: Website Builders peer median.

Priority fixes for sfl.gl

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

1. Priority 1 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   Why it matters: A sitemap helps search engines find new and updated pages, especially on large or frequently updated sites.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

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

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

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

   On Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

   26% of Website Builders peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Cloudflare: Add the header with a response header transform rule.

   42% of Website Builders peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Enable

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

   53% of Website Builders peers do this.

   Guide: Structured Data Basics for Website Owners

What sfl.gl already does well

Practices fewer than half of Website Builders peers use.

• Reachable over IPv6IPv6 address published.26% of peers
• HTTP/3 advertisedHTTP/3 advertised.29% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.34% of peers

What we saw

Homepage checked

https://sfl.gl/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

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

CDN or edge

Cloudflare

Platform or framework

Next.js

DNS operators

Cloudflare

HSTS

max-age 180 days, includeSubDomains, preload

DMARC policy

p=reject

Homepage HTML

136 KB, br

Images on homepage

20 (svg 5, webp 5)

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

• linkcloud.ai65
• lit.link67
• neocities.org73
• squarespace.com74
• wfolio.ru74

Website Builders readiness benchmark