Does Website Speed Affect Google Rankings?
Website speed can affect Google rankings, but a perfect performance score does not guarantee better positions. Discover what matters and how to improve your existing website.
Yes, website speed can affect Google rankings. Google confirms that Core Web Vitals, which measure loading performance, responsiveness and visual stability, are used by its ranking systems. However, speed is only part of the picture. A fast website still needs useful, relevant content to compete in search results.
For a business with an existing website, this raises a practical question: how much time and money should you spend making it faster?
The answer depends on what is slowing it down, how that affects your visitors and whether other problems also need attention.
This guide explains the relationship between website speed and SEO, what Google’s measurements mean and how to decide which improvements are worth making.
How does website speed affect SEO?
Website performance matters in two different ways: how Google evaluates the experience your pages provide, and how easily visitors can use your website.
These are connected business concerns, but they should be measured separately.
Google’s ranking systems use Core Web Vitals
Google explicitly states that Core Web Vitals are used in ranking. It also says that strong scores do not guarantee top positions, and that relevant content can rank well despite a weaker page experience.
There is no published formula that translates a speed improvement into a particular number of ranking positions.
For example, reducing a page’s loading time does not entitle it to move from position ten to position five. The result depends on the search query, competing pages and the other factors involved.
You can read this directly in Google’s guidance on page experience.
Performance also affects the customer journey
Imagine someone opening your website to check whether you provide emergency plumbing in their town.
If your main message appears promptly, your service area is clear and the telephone button works immediately, they can move towards contacting you.
If they face an empty screen, a frozen menu or a page that jumps while they try to tap, you have introduced obstacles before the conversation begins.
Removing those obstacles is worthwhile even when rankings remain unchanged. Measure the outcome through completed enquiries, bookings or sales, alongside search visibility.
What are Core Web Vitals?
Core Web Vitals are three measurements of real website experience.
They look beyond whether a page eventually finishes loading. They also consider when the main content appears, how quickly the page responds and whether its layout moves unexpectedly.
Largest Contentful Paint: when does the main content appear?
Largest Contentful Paint, usually shortened to LCP, measures when the largest visible image or text block appears within the initial viewing area.
On a business website, this could be a large introductory photograph or a prominent heading.
A good LCP is 2.5 seconds or less.
LCP is not the time required for every image, script and background request to finish. It focuses on a major piece of visible content.
Interaction to Next Paint: does the page respond promptly?
Interaction to Next Paint, or INP, measures responsiveness to interactions such as clicks, taps and keyboard input.
A good INP is 200 milliseconds or less.
Think of tapping a navigation menu and waiting for it to open. The page might look ready, but the delay makes it feel unresponsive.
Cumulative Layout Shift: does the layout stay steady?
Cumulative Layout Shift, or CLS, measures unexpected movement of visible page content.
A good CLS is 0.1 or less.
A familiar example is a button moving just as you try to tap it because an image above it has appeared.
These definitions and targets are explained in Google’s Web Vitals guide.
The thresholds are assessed at the 75th percentile of recorded experiences, with mobile and desktop considered separately. For each metric, the aim is for at least 75% of recorded experiences to meet its good threshold. This prevents a few excellent visits from disguising consistently poor experiences for other visitors. See how Google defines the Core Web Vitals thresholds.
Is a PageSpeed Insights score a Google ranking score?
No. A performance score out of 100 is a diagnostic result, not a prediction of where your website will rank.
PageSpeed Insights presents two useful types of information:
- Field data: measurements from eligible real Chrome users, where enough data is available.
- Lab data: a simulated Lighthouse test that helps identify technical problems.
The Lighthouse performance score belongs to the lab test. Real-user measurements reflect different devices, connections and visits over a trailing 28-day period.
A website can therefore receive a strong lab score while its real visitors still experience problems. The reverse can also happen.
Check whether the field report describes the individual URL or the wider website origin. PageSpeed Insights may show origin-level information when a specific page lacks sufficient data.
Google explains these distinctions in its PageSpeed Insights documentation.
When discussing an upgrade with a developer, ask for the measurements behind the headline score. “We improved mobile LCP on your main service pages” is more informative than “Your website is now 98.”
How fast should a business website load?
Use the Core Web Vitals targets above as your starting point, then test whether visitors can complete their actual tasks comfortably.
For a service business, those tasks might include:
- Understanding what you do.
- Checking the areas you cover.
- Reading about a particular service.
- Finding a telephone number.
- Completing an enquiry form.
- Booking an appointment.
A page that displays its main content promptly but has an unreliable booking form still needs work.
Equally, a lightweight contact page does not prove that a photograph-heavy portfolio performs well.
Set priorities around the pages that attract potential customers and the actions that matter to your business.
How to check whether your website is too slow
You can begin with free tools and a short, structured review.
1. Test several important pages
Start with your homepage, your main service page, a popular article and your contact or booking page.
If you run an online shop, include product and category pages.
Testing several page types helps reveal whether the problem affects a shared template or a particular feature.
For example, every service page might load slowly because they share the same oversized banner. Alternatively, only the gallery page may struggle.
2. Review mobile and desktop separately
Do not assume a website performs well for customers because it feels fast on your office computer.
Try it on your phone using a mobile connection. Open it as a new visitor and follow a realistic journey from a service page to an enquiry.
Pay attention to what happens before and after interacting with menus, forms and cookie controls.
3. Check Google Search Console
If your website is connected to Search Console, review its Core Web Vitals report.
The report groups similar URLs, which can help identify problems affecting multiple pages. It also separates mobile and desktop experiences.
Some smaller websites have insufficient data for useful reporting. Missing data should not be interpreted as either a pass or a failure.
Google explains the report and its limitations in its Search Console Core Web Vitals documentation.
4. Record a baseline
Before making changes, save the date, tested URLs and relevant results.
Also record the business measures you already track, such as organic search clicks and completed enquiries.
Without a baseline, it becomes difficult to distinguish a measurable improvement from a website that simply looks newer.
Which website speed improvements should you prioritise?
Begin with the cause of the delay. Installing an optimisation tool without diagnosing the problem can add complexity while leaving the main issue unresolved.
Make important images easier to load
Ask your developer to check the size, format and delivery of the image responsible for LCP.
The main image should be discoverable promptly and should not be delayed by inappropriate lazy loading.
Reduce unnecessary JavaScript
Review scripts used for widgets, tracking, animations and interactive features.
Remove unused code and investigate long-running tasks that prevent the browser from responding promptly.
Reserve space for images and embedded content
Give content predictable dimensions so that it does not push the page around as it appears.
This is particularly useful for banners, videos and other embedded elements.
Investigate slow server responses
Check whether hosting, caching or server-side processing delays the initial page response.
These are among the priorities covered in Google’s practical Core Web Vitals improvement guide.
For a business owner, the most useful next step is a prioritised list. Ask for each proposed change to include the affected pages, the expected benefit, the implementation cost and any functionality that needs retesting.
Should you improve speed or write better content first?
Treat this as a question of the biggest current obstacle.
Consider three common situations.
Your website is fast but does not explain your services
You may have a beautifully efficient website that gives visitors little useful information.
Perhaps your service pages never explain who the service is for, what the process involves or which locations you cover.
In this situation, spending heavily on a tiny performance gain would be difficult to justify before improving the pages themselves.
Your content is useful but the website is difficult to use
Your website may answer customers’ questions clearly, yet make people wait to read those answers or struggle to contact you.
Here, a performance review is a sensible priority. Your existing content may already provide a good foundation.
Both the content and the website need attention
Older websites often have several connected problems: unclear navigation, dated service information, slow templates and awkward mobile layouts.
A coordinated upgrade may be more practical than commissioning disconnected fixes over several months.
Ask for a proposal that separates the problems and explains how each will be addressed. This makes it easier to judge value and avoid paying for a visual redesign that leaves the underlying issues unresolved.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
Does WordPress make a website slow?
WordPress should not be diagnosed as the problem simply because it is the platform your website uses.
A useful audit examines the actual implementation: theme, plugins, images, hosting, caching and external services.
For an existing WordPress website, ask:
- Which specific files or features create the delay?
- Does the problem occur across every page?
- Can it be fixed within the current theme?
- Which plugins are still necessary?
- Will the proposed changes affect editing or essential functionality?
- What ongoing maintenance will be required?
These questions are more useful than a blanket claim that all WordPress websites need replacing.
If a few targeted changes solve the main problems at a reasonable cost, repairing the existing website may be the right decision.
Can an Astro website help improve performance?
Astro is a framework designed to support content-focused websites.
Its islands architecture allows most of a page to be delivered as HTML, with client-side JavaScript added to the components that need interactivity. This can help reduce unnecessary browser work. The approach is explained in the Astro islands documentation.
For a business website built around service pages, articles and case studies, this can provide a useful foundation.
However, the finished implementation still matters. Images, fonts, integrations and design choices all need attention.
At Afterworks, we use Astro when rebuilding existing business websites. We can use your current website as the starting point, develop an improved version and show you what has changed.
The aim is to make the decision concrete: you can review the design and the performance findings, rather than trying to imagine the result from a proposal alone.
A preview can demonstrate lab performance. Real-user performance needs to be measured after launch, once sufficient visitors have used the new website.
Should you repair or replace a slow website?
A slow website does not automatically need a complete rebuild.
Repair is worth considering when:
- The design still represents your business well.
- Visitors can navigate the website easily.
- Your content remains useful and accurate.
- The main performance problems have identifiable fixes.
- The website remains practical to maintain.
Replacement deserves consideration when:
- Important templates are difficult or expensive to improve.
- Mobile usability needs extensive work.
- Your services and business direction have changed.
- Routine edits are unnecessarily difficult.
- Several major problems would need separate projects to resolve.
Request a comparison of both options, including ongoing costs and the work needed to preserve existing content and functionality.
A rebuild should solve a clear business problem. “Newer technology” on its own is not a sufficient explanation.
How should you measure success after making improvements?
Agree on success measures before work starts.
Separate them into three groups:
- Performance: loading, responsiveness and layout stability on important pages.
- Search visibility: relevant impressions, organic clicks and landing-page performance.
- Business outcomes: qualified enquiries, completed bookings or sales.
This avoids treating a better test score as the entire result.
Retest the same URLs under comparable conditions. Then check that forms, menus, booking systems and tracking still work.
Review real-user data over time rather than expecting historical reports to change immediately.
When analysing search performance, record other changes made during the same period. New content, altered titles, seasonal demand and a redesigned navigation can complicate the picture.
If rankings improve after a wider website upgrade, it may be impossible to attribute the change to speed alone. Report the improvement honestly without inventing a precise cause.
Questions to ask a developer about website speed and SEO
Before agreeing to work, ask for clear answers to these questions:
- Which pages are currently underperforming?
- Are the findings based on lab tests, real-user data or both?
- What is causing the main delays?
- Which changes should happen first?
- Can the current website be improved economically?
- What evidence supports a recommendation to rebuild?
- How will essential functions be tested?
- What will the before-and-after report include?
- Which results can be demonstrated before launch?
- How will performance be monitored afterwards?
A useful proposal should connect technical changes to the experience your customers receive.
It should also distinguish between improvements the developer can deliver and search outcomes that nobody can guarantee.
Frequently asked questions about website speed and Google rankings
Can a slow website still rank highly?
Yes. Google says relevant content can appear prominently even when its page experience is weaker. Improving speed remains worthwhile, but it does not replace answering the searcher’s question well.
Will a perfect PageSpeed score put my website first on Google?
No. A perfect test result is not a first-place ranking guarantee. Use the report to identify and diagnose performance problems, then assess it alongside content quality and business results.
Do I need to rebuild my website to make it faster?
Not necessarily. Request an audit first. A specific image, script or template problem may be fixable without replacing the whole website.
Should I only test my homepage?
No. Include the pages people enter through search, especially important service, product and article pages. Test the pages involved in completing an enquiry or purchase as well.
How quickly will better website speed improve rankings?
There is no guaranteed timetable, and rankings may not change. Technical improvements can be visible in fresh tests before they are fully represented in historical real-user reports.
Is website speed worth improving if my rankings stay the same?
It can be. A website that makes it easier to read, navigate and enquire may serve your business better without attracting additional search traffic. Track completed customer actions to understand the practical effect.
Find out what is slowing down your existing website
If your website feels slow, begin with evidence: which pages struggle, what causes the problem and what it would take to improve them.
You may need a focused repair. You may benefit from a wider rebuild. The right choice should become clearer once you can compare the work involved and the expected result.
Afterworks helps businesses improve and replace existing websites using Astro. Our approach starts with what you already have, creates a version you can review and explains the improvements in a clear report.
Want to see what a faster, clearer version of your website could look like? Get in touch with Afterworks and share your existing website address.
