Skip to content
Familok

What we measure

Familok turns a website measurement into a building. To build it, the address you enter has to go to a few places. Here's where it goes, what we keep and for how long.

Last updated: 1 November 2026.

Google PageSpeed Insights does the measuring

Google PageSpeed Insights fetches and measures the site. Our server, not your browser, sends it the addresses of the pages you picked (five at most). We measure the phone version first, and the desktop version only if you ask for it.

The full-report link opens PageSpeed Insights directly in your browser, where Google's own terms apply.

Our bot suggests the floors

To suggest floors, our server fetches just three things from the measured site: robots.txt, the sitemap and the home page HTML. It always starts from that site's own addresses and, if the site redirects elsewhere, follows up to five redirects. It identifies itself as FamilokBot/1.0, with a link to this note (Polish version). We don't keep the fetched files.

If you run a site and would rather keep our bot out, two lines in robots.txt will do it:

User-agent: FamilokBot
Disallow: /

We then skip the sitemap and the HTML and measure no floors. Google PageSpeed Insights can still measure the ground floor, the page you start from, but that page is fetched by Google, not by our bot.

The website address

We cut the parameters (everything after “?”) and the fragment (everything after “#”) off the address. Only this shortened address goes any further: into the measurement, the result link and the cache.

What we keep, and for how long

We don't keep results for good. A summary of each page's result is kept for up to 24 hours in an Upstash Redis database (EU region, Frankfurt), so the same page isn't measured twice. It holds the window states, a few metrics, the measurement type and date, and the Lighthouse version. The address itself is not in it. So if you measure the same page and version (phone or desktop) again within those 24 hours, you'll see the same result with the same date.

Each entry is stored under a SHA-256 hash of the page address and the measurement settings. A hash doesn't hide the address: anyone who knows the address can compute the same hash and find the entry.

While a measurement is running, we also store a short lock under the same kind of hash, so two people don't measure the same page at once. It lasts less than 2 minutes.

A shared counter makes sure we stay within the request limit for Google. It stores only random IDs and request times, for up to 24 hours, with no website addresses and no IP addresses.

It's our server that writes to Upstash, not your browser, and your IP address doesn't go there.

The result link and the poster

A result link carries the measurement data in the address itself: the home page address, the floor paths, the window states, the metrics and the measurement date. Anyone you send it to can see them. There's nothing in it about the person who ran the measurement, though. Opening a result from the link doesn't touch our database.

The result page is put together on the server, so the whole link, measurement data included, may end up in the hosting provider's technical logs (more on those below). The r parameter in that link contains the measured domain and the page paths. It is signed, so it can't be forged, but it isn't encrypted.

Your browser draws the poster, and it never reaches our server.

Hosting

Familok runs on Vercel, and our server functions run in Frankfurt (region fra1). Like any hosting provider, Vercel keeps technical request logs, which include, among other things, the page address with its parameters, your IP address and your browser name. Vercel keeps them briefly, for up to 1 day, and on Familok's side only the author, Michał Janiec, can access them. Our code doesn't read, store or hash your IP address.

Nor do we write the addresses you enter, page addresses or IP addresses to our own logs.

Vercel's firewall (WAF) limits how many measurement requests can come from one IP address. That's what it needs your IP address for.

GEO mode

After the measurement you can switch to GEO mode. FamilokBot then fetches more from the site: the HTML of the chosen pages (five at most), robots.txt, the sitemap and /llms.txt. It handles redirects the same way as when it suggests floors.

It reads robots.txt first and skips any pages blocked there for FamilokBot.

We check the fetched HTML without running the page's scripts, and without AI. GEO mode sends no requests to Google.

We don't store GEO results on the server or in a database. They stay only in your open browser tab until you reload it, and they don't go into the result link or onto the poster.

GEO mode has its own request limit, separate from the one for Google PageSpeed Insights measurements.

Visit statistics

We count visits with Vercel Web Analytics, which, according to Vercel, works without cookies. We strip parameters and fragments from every page-view address, so neither result links nor addresses entered for measurement reach the statistics. To turn statistics off in this browser, open any Familok page with ?va=off at the end (?va=on turns them back on). We remember this choice in your browser's storage, if it's available.

The mjaniec.it link in the footer carries ref=familok. All it says is that the visit came from Familok, with no measured address and no results.

How the building is made

An algorithm draws the building from the measurement results, without AI. The same result always gives the same building.

Each result is a single Google PageSpeed Insights measurement from one day, and the next one may show slightly different numbers.

Personal data

Familok doesn't ask for your name, your email address or an account.

Your IP address and browser name may count as personal data. Vercel sees them in its technical logs (kept for up to 1 day) and when its firewall (WAF) limits requests from one IP address.

The same can apply to the measured site's address if it points to a specific person, for example a sole trader's website.

Data related to the measurement is processed by:

We've set our server functions and the Upstash database to the Frankfurt region. That's only our setting, though. We don't promise that the providers never process data outside the European Economic Area.

For questions about personal data, write to kontakt@mjaniec.it.

Contact

Questions about this page? Email kontakt@mjaniec.it.