Short answer
Start with a speed audit if you do not yet know what is slowing your site. If you already know the problem, for example a heavy store theme or a slow Largest Contentful Paint, you can go straight to the service that targets it.
How the services fit together
Website speed problems rarely have a single cause. A slow home page might combine an oversized hero image, a font that blocks rendering, three marketing tags that compete for the main thread and a server that takes a second to send the first byte. Fixing only one of those can leave the page feeling much the same. That is why the services below are arranged around the order in which the work normally happens: understand, fix, then keep it that way.
Google's own guidance groups the most effective improvements by metric. For loading, it recommends making the main image discoverable in the HTML and using a CDN to improve server response. For responsiveness, it recommends yielding to the main thread and avoiding unnecessary JavaScript. For stability, it recommends setting explicit sizes on content and keeping pages eligible for the back/forward cache [1]. Our services follow the same split.
Understand the problem
Speed audits are the starting point for most sites. We look at the real-user data Google collects through the Chrome UX Report, run controlled lab tests on your key templates, and read the code that loads on them. You receive a written report with each finding, why it matters and a ranked list of fixes with rough effort. The audit stands on its own: you can hand it to your own developer if you prefer.
Fix what matters most
- Core Web Vitals optimization targets the three metrics Google uses to describe loading, responsiveness and visual stability, on the templates that carry most of your traffic.
- Image and script optimization covers the two biggest sources of page weight and main-thread work: oversized images and JavaScript that loads earlier than it needs to.
- Caching and CDN setup deals with how quickly your server answers and how well repeat visits reuse files the browser already has.
- Technical cleanup removes code that no longer earns its place: unused CSS, abandoned tags, duplicate libraries and render-blocking files.
Platform-specific work
Some problems are tied to the platform. WordPress speed work focuses on themes, plugins, page caching and the database. E-commerce speed work deals with product images, app scripts, filters and the parts of a store that must never be cached, such as the cart and checkout. Both start from the same audit method, so the findings are comparable.
Keep it fast
Performance monitoring exists because speed decays. A new chat widget, a plugin update or a redesigned banner can undo months of work in an afternoon. Monitoring means someone checks field data and key templates on a schedule and tells you, in writing, when something slips and why.
What we do not offer
We do not sell promised rankings, promised scores or "speed plugins" that promise results without looking at your site. We also do not run paid advertising or general SEO campaigns. If an audit shows that your problem is outside our scope, such as a hosting plan that cannot be fixed with configuration, we will say so and explain the options.
Not sure where to start? The free speed project planner asks twelve questions and produces a text brief you can send to us or to any developer.
How pricing works across services
Each service is quoted in writing after a short review of your site, in US dollars and before work starts. The pricing page explains what drives the quote and what is included. If you want to understand typical market rates first, the cost guide collects published figures with their sources.
Questions about our services
Do I need an audit before any fixes?
Not always. If you already know the cause, for example a 4 MB hero image, we can quote the fix directly. For most sites an audit saves money because it stops effort going into changes that move nothing.
Can you work with my existing developer?
Yes. Our reports are written so another developer can act on them, and we can review their changes before release if that helps.
Which platforms do you work on?
We work with WordPress, WooCommerce, Shopify and hand-coded sites. For other platforms we check what can be changed before quoting, because some hosted builders limit access to code and server settings.
Sources
Opened and checked on November 3, 2026.
- The most effective ways to improve Core Web Vitals, web.dev. Primary documentation (cites HTTP Archive and Chrome data), last updated October 31, 2024.