What we are known for
Website speed and Core Web Vitals
Speed is not a finishing touch we apply at the end. It is a decision made at every step, and it is the one we care about most.
Google measures three things about how your page feels to a real visitor. LCP is how long until the main content appears. INP is how quickly the page answers a tap. CLS is how much the layout jumps around while it loads. Together they are the Core Web Vitals, and they come from real Chrome users, not from a test.
That last point is the one most agencies miss. A green score in a lab tool means the page was fast once, on a good connection, in a data centre. The number that counts is collected from people on a mid range Android phone on mobile data in the middle of the day.
So we measure the way the field measures. Median of several runs against the live site with a warm cache, checked at real device profiles, and then compared against the field data once it accumulates.
What the work covers
Included in every speed & core web vitals project.
An honest audit first
We run the site the way Google does and hand you the actual numbers before quoting any work. Sometimes the fix is two hours. We would rather tell you that.
LCP: find the element, then fix it
Usually a hero image or a web font. We size it correctly, serve it in a modern format, preload it, and remove whatever was blocking it in front.
Cut the JavaScript
Unused code is the most common cause of a slow phone experience. We read the bundle, remove what nothing imports, and split what only some pages need.
Defer third party embeds
Maps, chat widgets and video players are heavier than the rest of the page put together. We mount them only when a visitor scrolls near them, which routinely saves several hundred kilobytes.
Stop the layout jumping
Reserved space for images, ads and banners so text does not shift under a thumb that is already moving toward a link.
Keep it fast after launch
A budget in the build so a future change that adds weight fails the check rather than quietly shipping.
No themes, no page builders, no plugin stacks
Every site written from scratch, starting from almost nothing and adding only what the pages need. The whole speed recipe is published, not kept secret.
Read the recipe →AI, used properlyWe use AI to go faster, not to decide
It writes the mechanical parts. It never chooses the architecture, the performance budget, or a single fact about your business. Everything is reviewed by the person who will maintain it.
Where we draw the line →Questions
Asked often enough to answer here.
If yours is not here, the general questions page covers how we work, or you can just ask.
Why does my PageSpeed score change every time I run it?
Because a single run measures the network and the server that day as much as it measures your site. We have seen the same page score 70 and 97 on identical files. Take the median of three to five runs against the live site, and warm the cache first, or you are grading the CDN.
Does a perfect score mean better rankings?
Not directly. Core Web Vitals are a small ranking factor, and content still decides most of it. The real gain is that fewer people leave before the page appears. A visitor who never sees the page cannot become a customer, and that shows up in enquiries long before it shows up in rankings.
Can you speed up a site you did not build?
Yes, and a good share of our work is exactly that. WordPress, Shopify, Wix and custom builds all have known failure patterns. We start with an audit so you can see what is possible before committing to anything.
How fast should a page be?
Google's good threshold is LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1, measured at the 75th percentile of real visits. We aim comfortably under those so a bad network day still passes.
Related work we do
All 16 servicesCustom web development
Websites written from scratch for one business, rather than a theme bent into shape until it almost fits.
Next.js development
The framework we reach for first, and the one we know well enough to know when it is the wrong answer.
Bun and Node.js backends
The part nobody sees, which is exactly why it has to be right.
Want this for your business?
Tell us what you have now and what is not working. We will tell you what we would do and what it would cost.