First screen takes longer than 3 seconds
Half of mobile visitors leave without waiting. You pay for this traffic with ads but never see it in your enquiries.
// Services
The site loads slowly — and silently loses customers
We find what exactly is slowing the site down and remove it. With before-and-after measurements visible in Google PageSpeed and in Search Console.
- Free measurement and a list of causes — on the day you get in touch
- From $400 per project, delivery in 3–10 days
- If the agreed result is not reached, we refund the money
When it is time to do this
Search Console complains
In the Core Web Vitals report pages are marked as "needs improvement" or "poor". This is a direct ranking factor.
PageSpeed shows less than 50
On mobile the score is in the red zone. Usually it is heavy images, a dozen plugins and third-party scripts.
The layout jumps while loading
Content shifts, people miss the button. Google counts this as CLS and lowers the page's score.
Advertising gets more expensive
Google Ads lowers the quality score for a slow landing page — you pay more per click than competitors with the same offer.
The store is slow in the catalogue
The filter page thinks for several seconds on every click, and people leave before they reach the product.
Why site speed costs money
Load speed affects the business in two ways at once. The first is obvious: a person on a phone does not wait — by various measurements about half of visitors leave a page that loads longer than three seconds. If you bring this traffic with ads, you pay for every one of them.
The second way is less visible. Since 2021 Google has taken Core Web Vitals into account — three metrics describing a real user's experience: LCP (when the main content appeared), CLS (how much the layout jumped) and INP (how fast the page responds to actions). These data are collected from real visitors of your site, not from a lab test, and they affect positions in the results.
Advertising is a separate matter. Google Ads calculates a landing page quality score, and speed is part of it. A slow page means a higher cost per click for the same offer. So you pay twice: you lose part of the visitors and overpay for those who got through.
What usually slows things down
Heavy images
A 4 MB photo straight from the camera where 150 KB in WebP would do. The most common cause and the cheapest to fix.
A dozen plugins
Each drags its own CSS and JS onto every page, even where it is not used.
Third-party scripts
Chats, pixels, review widgets — they load synchronously and block the page from rendering.
No caching
The server assembles the same page from scratch every time.
Slow hosting
Server response time over a second — there is no point optimising further until you move.
Fonts
Several weights from an external source, which make the text appear with a delay.
How we work
- 01
Free measurement
We look at the site in PageSpeed, in Search Console and by hand. We tell you what exactly is slowing it down and how much it can realistically be sped up. On the day you get in touch.
- 02
We agree on the result
We fix the target numbers before the work starts: what mobile score and which Core Web Vitals we are to reach.
- 03
We remove the causes
Images, scripts, caching, fonts, database queries — one by one, with a measurement after each step. 3–10 days.
- 04
Before-and-after measurements
We show not only the PageSpeed score but the real time to the first screen. A report with screenshots.
- 05
A month of monitoring
Core Web Vitals are collected from real users and do not update immediately. For a month we watch until the numbers in Search Console turn green.
What it costs
The price depends on what exactly is slowing things down. The measurement is free — after it we name the exact figure.
Quick package
$150
one-time
When one obvious thing is slowing the site down: images, cache, fonts.
- Image optimisation and WebP
- Caching and compression
- Before and after measurements
- Report with explanations
Delivery: 2–3 days
Measure my sitepopular
Full optimisation
from$400
one-time
The most common format: we work through every cause and reach the green zone.
- Everything in the quick package
- Scripts and third-party widgets
- Core Web Vitals: LCP, CLS, INP
- Database query optimisation
- A month of monitoring
- No result — money back
Delivery: 3–10 days
Speed up my siteStore
from$900
one-time
Catalogues with filters, thousands of products and heavy pages.
- Catalogue and filter optimisation
- Database queries and indexes
- Caching of dynamic pages
- Cart and checkout speed
- A month of monitoring
Delivery: from 2 weeks
Discuss the storeIf the measurement shows that the main cause is the hosting, we will be the first to say so. Optimising code on a server with a two-second response time is wasted work: first the move, then the optimisation.
Frequently asked questions
The quick package — $150 for 2–3 days, if one obvious thing is slowing things down. Full optimisation — from $400, delivery in 3–10 days. Stores with a catalogue — from $900. We name the exact figure after the free measurement.
We fix the target numbers before the work starts, after the measurement — when it is already clear what exactly is slowing things down. If the agreed result is not reached, we refund the money. Promising 90+ before looking at the site would be dishonest: on some systems the ceiling is lower.
We work on a copy and check every step separately. Before rolling out to the live site we make a backup. If something stops working, we restore it as it was and look for another way.
Yes, and it is the most common case. We look at which plugins are actually used, which duplicate each other, and which drag their scripts onto every page for no reason. Often half of them can be removed without losing functionality.
We will say so right after the measurement. If the server response time is over a second, optimising the code is pointless — first the move. We can do the migration ourselves; it is separate work.
PageSpeed shows two different data sets: a lab test (run fresh every time, so it jumps) and field data from real users over 28 days (updated slowly). We go by the field data — that is what Google takes into account.
Core Web Vitals are calculated over 28 days of real traffic, so after the fixes the numbers in Search Console do not change immediately. Usually the first shifts are visible in two to three weeks, the full picture in a month to a month and a half.
Measure my site
Start a project