flat.io

Readiness by lane

Green: flat.io. Thin bar: Design & Content Creation peer median.

Priority fixes for flat.io

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

1. Priority 1 · Accelerate

   Modern image formats in use

   Observed: The homepage had 46 images and none used WebP or AVIF.

   Why it matters: WebP and AVIF are typically much smaller than JPEG or PNG at similar quality, and images are often the heaviest part of a page.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   On Nuxt: Nuxt Image can output WebP and AVIF.

   56% of Design & Content Creation peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

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.

   37% of Design & Content Creation peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   43% of Design & Content Creation peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   29% of Design & Content Creation peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What flat.io already does well

Practices fewer than half of Design & Content Creation peers use.

• security.txt publishedsecurity.txt with a contact found.9.1% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.41% of peers
• Framing restrictedFraming controls present.48% of peers

What we saw

Homepage checked

https://flat.io/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 89-day validity, expiring 2027-01-17

Platform or framework

Nuxt

DNS operators

Amazon Route 53

DMARC policy

p=reject

Homepage HTML

157 KB, gzip

Images on homepage

46 (png 100, svg 6)

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 Design & Content Creation sites

• diy-artclub.com75
• photoroom.com76
• vistaprint.in75
• webcamtoy.com75
• xtool.com76

Design & Content Creation readiness benchmark