Short answer
The short version: we work from real-user data where it exists, fix causes in order of impact, test every change before release and never promise a score or a ranking. Quotes are free, in writing and in US dollars.
About speed and Core Web Vitals
Core Web Vitals are three measurements of real-world experience: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness and Cumulative Layout Shift for visual stability. Each has a published threshold for good, judged at the 75th percentile of page loads [1]. The questions below cover what that means for your site in practice.
About working with us
Most projects start with a free first review by email, followed by a fixed-price audit and a written quote for fixes. You get one named contact and a short written update at the end of each stage. The process page describes each stage, and the pricing page explains how quotes are built.
All questions and answers
What is website speed optimization?
Finding what makes pages slow to appear, slow to respond or jumpy while loading, and fixing those causes. Most of the work involves images, scripts, fonts, caching and server response time.
What are Core Web Vitals?
Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. Google's good thresholds are 2.5 seconds, 200 milliseconds and 0.1. Our Core Web Vitals guide explains each one.
Will speed work improve my Google rankings?
It can help, but nobody can promise it. Google says Core Web Vitals are used by its ranking systems and also that it shows the most relevant content even when page experience is sub-par. See what Google says about speed and SEO.
Can you get my PageSpeed score to 100?
We do not promise scores. Lab scores vary between runs and are not what Google uses for Core Web Vitals. We aim for good field data on the pages that matter.
Why do PageSpeed Insights and Search Console show different things?
PageSpeed Insights shows a lab test of one URL plus field data, while Search Console groups many URLs by real-user experience. Our field and lab data guide explains the difference.
How long does a project take?
We plan for one to two weeks for an audit and three to six weeks for an audit plus fixes on a typical small business site. Field data then needs about four weeks to reflect the changes.
Who will I deal with?
One named contact handles your project from first review to follow-up. First contact is by email; calls can be arranged once a project is under discussion.
What access do you need?
For an audit, Search Console access and read access to the site often suffice. For fixes, we need access to whatever is being changed. We agree a safe way to share it; please never send passwords by email.
Do you work on Shopify, WordPress and WooCommerce?
Yes, along with custom sites. For other platforms we check first what can be changed, because some hosted builders limit access to code and server settings.
Will my site break?
Changes are made on a staging copy where possible, tested against the features they could affect and released in small groups so anything unexpected can be reversed quickly.
Can my own developer make the fixes?
Yes. Audit reports are written so any developer can act on them, and we can review their changes before release.
How much does it cost?
Each project is quoted in writing after a free first review. Our cost guide collects published market figures if you want a sense of typical ranges first.
Do you offer ongoing help?
Yes, through performance monitoring: scheduled checks with a short written note each time, monthly or quarterly.
Do you only work with US businesses?
Our guides and pricing are written for the United States, and we quote in US dollars. If you are elsewhere, get in touch and we will tell you honestly whether we are a good fit.
Sources
Opened and checked on November 3, 2026.
- Web Vitals, web.dev (Google Chrome team). Primary documentation, last updated October 31, 2024.