Fast for every visitor. Light on your website.

We measure Sairo the way browsers do. Here are the numbers, what they mean for the people who visit you, and how to check them yourself.

Four categories, two devices, one dated run.

The homepage on 7 September 2026, measured with Lighthouse 12.8. Ninety and above is green in every category. The phone run is the demanding one: it emulates a mid-range device on a slow connection.

Phone

Mid-range Android, slow 4G connection, processor four times slower than a laptop.

Performance
Accessibility
Best practices
SEO

Desktop

Laptop-class device on a fast connection.

Performance
Accessibility
Best practices
SEO

Lighthouse scores move a few points between runs and with the distance from our servers. These are single runs, not the best of several.

The numbers behind the scores.

Scores summarise; these are the measurements that produce them, from the same phone run.

Total Blocking Time: 10 msHow long the page keeps a phone from responding to a tap while it loads. Anything under 200 ms counts as good.
Cumulative Layout Shift: 0Nothing on the page moves after it appears, so a tap lands where you aimed it.
Largest Contentful Paint: 2.6 sWhen the hero image is fully on screen over a simulated slow 4G connection.
The whole homepage: 344 KB28 requests, every one of them to sairo.app. No trackers, no ad scripts, no font service.
The HTML itself: 23 KBBuilt ahead of time and compressed with brotli, so the page arrives as one small response.
The widget on your website: 15 KBThe compressed script your site loads. Its budget is 50 KB uncompressed, checked on every build.

The same discipline applies to the script you install. It is small, it waits for your page, and it stays out of your layout.

Measure a chatbot's effect on your siteCompare your pages before and after installation.Add Sairo to your websiteThe snippet, where it goes, and what to check.

Loads asynchronously after your page, so it never blocks your content or your own scripts.
Keeps its styles inside Shadow DOM. It does not restyle your site, and your stylesheet cannot break it.
Sits in a fixed corner as a launcher, so nothing on your page moves when it appears.
Talks only to sairo.app. No ad networks, no analytics beacons, no third-party fonts.
About 15 KB compressed, budgeted at 50 KB uncompressed and measured on every build.

How the site stays fast.

No tricks aimed at the test. Each of these makes the page lighter for a real visitor, and the score follows.

Built before anyone asks

Every public page is generated as static HTML when we release, not when you visit. The server sends a finished page instead of assembling one per request.

Nothing from third parties

The typeface is self-hosted, there are no analytics tags or tracking pixels, and the content security policy only permits sairo.app. Your visit is a conversation with one server.

Icons as shapes, not libraries

The site draws its icons from the exact path data it needs. That replaced a 204 KB icon library with 29 KB of shapes on every page.

A 3D assistant that waits its turn

Phones get a still image of the assistant, captured from the scene itself. Desktops load the WebGL model only after the page is ready and the browser is idle.

Cached and compressed

Versioned assets are cached for a year and images for a month. Responses use brotli over HTTP/2 and HTTP/3, so repeat visits cost almost nothing.

Accessible by design

A 100 on Lighthouse accessibility is the floor. Keyboard navigation, visible focus, screen reader labels and reduced-motion support are part of every component. Our accessibility approach.

What changed on 7 September 2026.

We publish these numbers because we did the work in the open. A performance pass that day moved the homepage on a phone from an unpredictable score to a consistently green one.

Homepage on a phone, before and after
Measure	Before	After
Lighthouse performance	62 to 92, depending on the run	95
Total Blocking Time	110 ms to 2,650 ms	10 ms
Speed Index	5.3 s	3.7 s
Bytes over the wire	645 KB in 34 requests	344 KB in 28 requests
JavaScript	340 KB	143 KB
HTML	48 KB, built per request	23 KB, built ahead of time
Lighthouse SEO	92	100
Back/forward cache	Not eligible	Eligible

Check it yourself.

Nothing here needs our word for it. Any of these gives you an independent reading in about a minute.

Run PageSpeed Insights
Google's hosted Lighthouse, from Google's own network. Open the report for sairo.app (opens in a new tab)
Run Lighthouse from a terminal
The same engine on your own machine, with the report opened in your browser when it finishes.
```
npx lighthouse https://sairo.app/ --view
```
Use Chrome DevTools
Open the Lighthouse panel, choose Mobile, and analyse the page. Your device, your connection and your distance from our servers all move the result a little, which is normal.

Questions people ask about these numbers.

Why do the scores change between runs?

Lighthouse simulates a slow connection and a slower processor, then measures real timing on the machine running it. Background work, network conditions and distance from our servers each move the result by a few points. We publish one dated run rather than the best of several.

Will adding Sairo slow my website down?

It adds one asynchronous script of about 15 KB compressed that loads after your page. Its launcher is fixed in a corner, so it causes no layout shift, and its styles stay inside Shadow DOM. Measure your own pages before and after installation with the same tool; our guide on measuring chatbot performance explains how.

Is this field data or lab data?

Lab data. The scores come from Lighthouse runs on the date shown, not from aggregated visitor measurements. We measure again after significant changes and update the date on this page.

See what your website can answer.

Try a sample, review the result, and decide what comes next.

Try your website Talk about a rollout