Start a project Speed is not a feature added at the end. It is the framework choosing what to send — and what it refuses to send is what makes the site harder to break.
Measured with Lighthouse 13.5.0 on mobile against the live sites, not a staging build. Each score below is the median of four runs across all six production sites. Lab scores move a point or two between runs, so read them as a range rather than an exact number.
A framework runtime is downloaded by every visitor before the page can finish working, whether or not the visitor needs it. That is a few hundred kilobytes, on the slowest connection in the room, before anyone reads a word.
It is also an attack surface. A publishing component carries a history of vulnerabilities that only get exploited when the visitor’s browser runs code the page never needed. Sending less is both the fast path and the safe one.
01
Astro renders to plain HTML at the edge and ships no framework runtime to the visitor. The three scripts the BrightSmile page loads total 2.4 KB compressed. Everything else the page needs is already in the HTML, which is why it renders before the network has finished thinking about it.
02
HTTPS, HSTS for two years, nosniff, a referrer policy and a full content security policy are set in the Worker rather than left to a plugin. One function at a single choke point, so a cached hit and a cache miss both get them — a site that sends them only on the happy path looks configured and is not.
03
Google ranks on speed as a signal, not a bonus. The screenshot here is the desktop run: 100 for performance, accessibility, best practices and SEO, a 1.2s largest paint, zero blocking time and no layout shift. On an emulated phone — slow 4G, a Moto G Power — BrightSmile reads 98–99 across four runs, and that is the number I quote, because it is the screen your patients are actually on.
The audit is repeatable — Lighthouse will run the same check against your site at any time, and you are welcome to. If the numbers on this page ever stop matching the live sites, that is my problem, not yours.
Open the PageSpeed report itself Check this homepage's live score