Performance
What a fast site is actually worth
A speed score is not a trophy. It is the time a person waits before your page shows them anything. Google measures that wait on real visits, publishes the numbers it considers acceptable, and says plainly that its ranking systems use them. This page shows what those numbers are, what this site scores, and how to check any of it yourself in a minute.
What this site scores
Our own home page, run through Google’s PageSpeed Insights. Same tool, same profiles we use on every site we build and on every competitor we publish.
| Profile | Speed score | Largest paint | Page weight |
|---|---|---|---|
| Phone | 99 / 100 | 1.58 s | 623 KB |
| Desktop | 100 / 100 | 0.36 s | 710 KB |
PageSpeed Insights, median of five runs, measured 9 September 2026. Put eweb-studios.com into pagespeed.web.dev and you run the same test we did. A single run bounces by a few points on Google’s own machines, which is why we publish the median of five and the date.
Why Google measures this at all
Google publishes three numbers it calls Core Web Vitals: how long until the main content appears, how quickly the page answers a tap, and how much the layout jumps while it loads. Its thresholds for “good” are public, and they are measured on real visits, at the 75th percentile - so the slowest quarter of your visitors still counts.
Main content appears
under 2.5 s
Largest Contentful Paint
Answers a tap in
under 200 ms
Interaction to Next Paint
Layout shift stays under
0.1
Cumulative Layout Shift
Thresholds published by Google at web.dev.
“Core Web Vitals are used by our ranking systems.”
That is Google’s own sentence, and it is the whole reason we measure before and after every build. But it is only half of what they say, and the other half is the part most agencies leave out:
“Google Search always seeks to show the most relevant content, even if the page experience is sub-par.”
“There is no single signal. Our core ranking systems look at a variety of signals that align with overall page experience.”
So we will not tell you that a fast site puts you first. It does not. Speed is what decides the case when several pages answer the same question equally well - and it is what stops you paying for clicks that leave before the page draws.
Both sentences are quoted from Google’s page experience documentation, read 9 September 2026.
What that looks like in your market
We ran the same test on the sites currently ranking for web design in 10 US cities: 31 sites in all. Their median speed score is 62 out of 100. Their median main content appears in 6.77 seconds, against Google’s 2.5 second threshold - 28 of the 31 are over it, and the slowest takes 35.4 seconds.
These are the agencies selling websites in your city. The site they built for themselves is the work sample. It is worth opening two or three of them on your phone before you sign anything - not because we say so, but because that is exactly what your customer does.
How we hold a site at these numbers
Nothing here is a trick, and none of it is bolted on afterwards. Pages ship as static files, so a visitor waits on one file rather than on a database. Fonts and images come from the same server as the page. Scripts wait until the text has been drawn instead of competing with it. Anything below the first screen loads when the reader gets close to it. Analytics wait for the first tap or scroll.
Then it is measured, before and after, and the numbers go in the handover document with the date on them. A site that is fast on launch day and slow six months later was never built right; that is why we re-measure monthly and publish what we find.
Check ours before you believe any of it
Open pagespeed.web.dev, paste eweb-studios.com, and read the score Google gives you. Then paste the site of whoever else is quoting you. That comparison takes two minutes and tells you more about how someone builds than any portfolio page, ours included.