Case studies · Stackwillow

stackwillow.com, our own site

Before we build for clients, we build for ourselves. How our own site is made, with every claim one you can check in your browser.

Illustration · what your browser shows

The facts, and how to check them

Cookies before you consent
0
Developer tools › Application › Cookies. The list for stackwillow.com is empty.
Third-party requests
0
Developer tools › Network, then reload. Every request goes to stackwillow.com.
Content Security Policy
Own origin only
Network › the page request › Response headers › content-security-policy: default-src 'self'.
Scripts
1 (theme switch, under 2 KB)
Network › filter JS. Only theme.js loads; the menu and FAQ work without JavaScript.
Fonts
Self-hosted
Network › filter Font. Every font file comes from stackwillow.com, none from Google Fonts.
Mobile Lighthouse score
Published at launch
Measured on the live site at launch and posted here with the date and the raw report.

How it’s made

What we built

01

Static pages on a global edge

Built with Astro into plain HTML and served by Cloudflare, so pages load fast with no server to attack.

02

Security headers on every response

HSTS, a strict Content Security Policy, X-Frame-Options, nosniff, Referrer-Policy and Permissions-Policy.

03

Checked at every build

The build fails if any inline script or style slips in, and type checks and linting run on every change.

Want a site built like this? Start with a free quote.

Tell us what you need. We reply within one business day with a plan. Your written quote follows after first contact.

After you write: call notes the same day, then your written quote after our call.