The proof vault
Most agencies say fast. We publish the measurements. Everything on this page comes from Google PageSpeed Insights API runs we archived as raw JSON, with dates, or from Google Search Console. If we cannot measure it, it does not appear here.
- 98 to 100 PageSpeed, measured
- 2 live builds, 2 more staged for launch
- 204-page sitemap, verified in Google Search Console
- Every build gated, every site monitored 24/7
Every chip is a verified fact. Hover one for its source, or see the full proof.
Official PageSpeed Insights results
Measured with the Google PageSpeed Insights API (Lighthouse 13.4.0) on July 8, 2026 (UTC). Raw JSON responses archived in the Villex Web audit vault, PSI_Proof_July2026. Scores of 90 and above sit in Google’s top band; these runs measured 98 to 100.
| Page | Device | Performance | FCP | LCP | CLS | Measured | Raw proof |
|---|---|---|---|---|---|---|---|
| villexweb.com home | Mobile | 98 / 100 | 0.9 s | 2.4 s | 0 | 2026-07-08 UTC | View JSON → |
| villexweb.com home | Desktop | 99 / 100 | 0.3 s | 0.8 s | 0 | 2026-07-08 UTC | View JSON → |
| villexweb.com industry page (home services) | Mobile | 98 / 100 | 1.1 s | 2.4 s | 0 | 2026-07-08 UTC | View JSON → |
| villexweb.com industry page (home services) | Desktop | 100 / 100 | 0.3 s | 0.4 s | 0.001 | 2026-07-08 UTC | View JSON → |
| villexco.com home (our in-house build) | Mobile | 100 / 100 | 1.1 s | 1.3 s | 0 | 2026-07-08 UTC | View JSON → |
| villexco.com home (our in-house build) | Desktop | 100 / 100 | 0.2 s | 0.3 s | 0 | 2026-07-08 UTC | View JSON → |
Tool: Google PageSpeed Insights API, engine Lighthouse 13.4.0. Each row is one archived run; the timestamp is the run’s own fetchTime. The View JSON link on every row opens the exact, unedited Google API response behind that score, so you can read the performance score, the FCP, LCP, and CLS audits, and the fetch timestamp yourself. You can also re-run any of these pages live at pagespeed.web.dev and compare.
What each metric actually means
These are Google’s own measurements of how a page feels to a real person. Here is each one without the jargon.
Google’s overall speed grade for a page. 90 and above is rated "good", the top band. Most template and builder sites score far below that on mobile; our archived runs sit between 98 and 100.
How long until the first text or image appears. It answers the visitor’s first question: is this site working? Under 1.8 seconds is rated good; our archived runs measure 0.2 to 1.1 seconds.
How long until the main content of the page is visible. This is the number Google uses to judge whether a page feels fast. Under 2.5 seconds is rated good; every archived run is at or under 2.4 seconds.
How much the page jumps around while loading. A score of 0 means nothing moves under your finger, ever. Five of our six archived runs measure exactly 0; the sixth measures 0.001, and anything under 0.1 is rated good.
The gates every build must pass
Scores like these are not a one-time stunt. They are the output of automated checks that run on every single build, and a monitor that never sleeps. A build that fails a gate cannot deploy, full stop.
A script checks every generated page against strict weight budgets, including every rendered image. If anything is oversized, the build fails and cannot deploy. Speed is enforced by machine, not by good intentions.
Every animated element must sit inside a choreography group, and every page must render its full content even if scripts never load. The build fails if either rule is broken, so motion can never hide your content.
An always-on monitor confirms each live site is reachable, loads within budget, and has not drifted from its performance baseline. If something degrades, we know before you do.
Google Search Console
Submitted and discovered, verified July 7, 2026. This is our own site data, nothing sensitive to hide. The most inspectable proof is the sitemap itself:
Open our live sitemapThese are lab measurements run on Google infrastructure. Mobile runs simulate a mid-range phone on a slow mobile connection; desktop runs simulate a desktop computer on broadband. Field data (what real visitors experience) accumulates in Google CrUX as traffic grows.
So these numbers prove the engineering is right; they are not a guarantee of your business results. We are a young studio, and we would rather show you six dated measurements than a wall of claims you cannot verify.
Live from our monitoring database
The figures in this section are not written into the page. Your browser reads them from the Villex web-ops database when the page loads, and the read time is printed underneath. Google Search Console figures are pulled into that database by an automated job once a day; the uptime counts are one database row per automated check.
One of the properties below is a client, published anonymously: no name, no domain, and the anonymity is enforced in the database itself, not just on this page. The others are our own. If the live read fails, this section says so and shows nothing rather than quietly serving you yesterday's number.
This block is being read live from the Villex web-ops connector. If it still says this after a moment, the read did not complete, and no figures will be shown in its place: we do not keep a copy of these numbers in the page.
The archived PageSpeed measurements higher up this page do not depend on this read. Every one of them links its own raw Google API response.
Reading from the Villex web-ops connector.
Sources, so you can hold us to them. Search figures: Google Search Console, pulled by the ga-gsc-runner job on a daily schedule (03:40 UTC) into command_os.engine_connector_authorization. Uptime figures: The Villex uptime monitor, one row per automated check in command_os.engine_property_check_result. Both are exposed to this page through one read-only view, web_ops_public_proof, which contains no client name and no client domain.
What we are not claiming. The search window is a rolling 28 days ending at the last sync, so it is not comparable to a 90 day figure, and we do not store a history, so there is no trend line here to draw. Google Search Console data lags real time by two to three days. The uptime counts start the day the monitor started logging and say so. These are one set of properties over a short window: evidence of the work, not a guarantee of the same result for your business.
Want numbers like these on your site?
Send us your current site and we will measure it the same way, for free, and show you exactly where it stands and what we would fix.