Website speed directly impacts how people experience your site. A slow page drives visitors away, lowers your search rankings, and hurts conversions.
PageSpeed Insights is a free tool from Google that shows exactly how your site performs and what’s slowing it down.
It breaks complex data into clear scores and actionable recommendations.
In this guide, you’ll learn how to use PageSpeed Insights step by step, understand your results, and fix the issues that matter most.
What Is PageSpeed Insights?
PageSpeed Insights is a free performance testing tool from Google that analyzes how fast your web page loads and how well it performs for users, then gives you a clear report with a score and specific recommendations you can act on immediately.
It runs on Google Lighthouse, which is the same auditing engine built into Chrome DevTools, meaning the results are based on real, industry-standard performance checks used by developers worldwide.
When you test a page, you’ll see separate results for mobile and desktop because Google simulates different devices and network speeds—mobile tests are stricter and usually slower since they reflect real-world conditions like smaller screens and weaker connections, while desktop tests assume faster hardware and internet.
The report also includes two types of data that you need to understand: lab data and field data.
Lab data is generated in a controlled test environment and helps you debug issues quickly with consistent results, while field data comes from real users visiting your site (collected in the Chrome User Experience Report) and shows how your page actually performs in the real world over time.
Together, these insights help you identify both technical problems and real user experience issues so you can prioritize fixes that make the biggest impact.
How to Access PageSpeed Insights
Go to the PageSpeed Insights Website
Start by opening your browser and going to the official PageSpeed Insights tool at https://pagespeed.web.dev.
You don’t need to sign up or install anything, which makes it quick to use from any device. The homepage is simple and focused, with a single input field where you’ll run your test.
Enter Your Website URL
Copy the full URL of the page you want to test and paste it into the input box.
Be precise here—test the exact page you care about, not just your homepage, because performance can vary across different pages.
For example, blog posts, product pages, and landing pages often behave differently.
Click “Analyze”
Once your URL is entered, click the “Analyze” button to start the test.
The tool will begin scanning your page using Google Lighthouse, checking things like loading speed, performance, and best practices.
This step is automatic, so there’s nothing else you need to configure.
Wait for the Report to Generate
The analysis usually takes a few seconds, depending on your page size and connection speed.
After it finishes, you’ll see a full report with scores, key metrics, and specific recommendations.
This report is your starting point for improving performance, so take a moment to review it before making changes.
Understanding Your PageSpeed Score
Your PageSpeed score is a quick snapshot of how well your page performs, but it should be used as a guide—not the final judgment.
Google calculates this score based on several performance metrics, then combines them into a number from 0 to 100.
Score Ranges Explained
- 90–100 (Good):
Your page is performing well. It loads fast, responds quickly, and provides a smooth user experience. You may still see minor suggestions, but nothing critical is holding your site back. - 50–89 (Needs Improvement):
Your site is functional but has clear areas that need optimization. Visitors may notice slower load times or delays. Fixing key issues in this range can lead to noticeable improvements in both user experience and SEO. - 0–49 (Poor):
Your page has serious performance problems. It likely loads slowly, feels unresponsive, or shifts content while loading. These issues can drive users away and negatively impact your rankings.
The Score Isn’t Everything
It’s important to understand that the score alone doesn’t tell the full story.
A perfect 100 doesn’t guarantee a great user experience, and a lower score doesn’t always mean your site is unusable.
Focus on the actual metrics and recommendations behind the score, especially Core Web Vitals, because they reflect how real users experience your site.
Key Metrics Explained (Core Web Vitals)
Core Web Vitals are the most important metrics in PageSpeed Insights because they measure how real users experience your site.
Instead of focusing only on load time, they look at speed, responsiveness, and visual stability.
Improving these metrics has a direct impact on user satisfaction and search rankings.
Largest Contentful Paint (LCP)
Largest Contentful Paint measures how long it takes for the main content of your page to fully load and become visible to the user.
This is usually a large image, heading, or content block that appears above the fold. If this element loads slowly, users feel like the page is lagging, even if other parts load faster.
A good LCP score is 2.5 seconds or less, which means users can quickly see the most important part of your page.
To improve LCP, focus on faster hosting, optimized images, and reducing heavy scripts that delay rendering.
Interaction to Next Paint (INP)
Interaction to Next Paint measures how quickly your site responds when a user interacts with it, such as clicking a button, tapping a link, or typing into a form.
It replaced First Input Delay (FID) because it gives a more complete view of responsiveness across the entire page, not just the first interaction.
A good INP score is 200 milliseconds or less, which ensures your site feels smooth and responsive.
Slow INP usually comes from heavy JavaScript or long processing tasks that block the browser, so reducing unused scripts and improving code efficiency can make a big difference.
Cumulative Layout Shift (CLS)
Cumulative Layout Shift measures how stable your page layout is while it loads.
It tracks unexpected movements, like buttons shifting, images jumping, or text moving around, which can frustrate users and cause accidental clicks.
A good CLS score is 0.1 or lower, meaning the layout remains stable as the page loads.
Layout shifts often happen when images or ads don’t have set dimensions or when content loads late, so defining sizes for media and avoiding dynamic layout changes helps keep your page visually stable.
Other Important Metrics
While Core Web Vitals are the main focus, PageSpeed Insights also shows additional metrics that help you understand exactly where your site slows down.
These metrics break down different parts of the loading process so you can pinpoint issues more accurately.
First Contentful Paint (FCP)
First Contentful Paint measures how long it takes for the first visible content to appear on the screen, such as text, an image, or a background element.
This is the moment users know your page is actually loading. A fast FCP creates a strong first impression and reduces the chance of users leaving early.
Aim for 1.8 seconds or less. If your FCP is slow, focus on reducing render-blocking resources like large CSS or JavaScript files and improving server speed.
Time to First Byte (TTFB)
Time to First Byte measures how quickly your server responds after a user requests your page. It tracks the time from the initial request to the first piece of data being received.
A slow TTFB usually points to server-related issues such as poor hosting, unoptimized databases, or a lack of caching.
A good target is under 800 milliseconds. Improving TTFB often involves upgrading hosting, enabling caching, and optimizing backend performance.
Total Blocking Time (TBT)
Total Blocking Time measures how much time the browser is blocked by long tasks, usually caused by heavy JavaScript.
During these blocks, users cannot interact with the page, which makes the site feel unresponsive. TBT is closely related to responsiveness and directly impacts metrics like INP.
A good TBT score is under 200 milliseconds. To improve it, reduce unused JavaScript, split large scripts into smaller chunks, and delay non-essential code.
Speed Index
Speed Index shows how quickly the visible parts of your page are displayed during loading. Instead of focusing on a single moment, it looks at how smoothly content appears over time.
A lower Speed Index means users can see most of the page faster, which improves perceived performance. Aim for 3.4 seconds or less.
You can improve this by optimizing images, prioritizing above-the-fold content, and reducing heavy resources that delay rendering.
Lab Data vs Field Data
What Is Lab Data (Simulated Tests)
Lab data is created in a controlled testing environment using Google Lighthouse.
It simulates how your page loads on a specific device and network, usually a mid-range mobile phone with a slower connection.
This makes results consistent and easy to compare across tests.
Lab data is best for debugging because it shows detailed performance metrics and highlights exact issues, such as render-blocking resources or heavy scripts.
Since it runs on demand, you can test changes immediately and see how your fixes impact performance.
What Is Field Data (Real User Data)
Field data comes from real users who have visited your site, collected through the Chrome User Experience Report.
It reflects actual performance across different devices, locations, and network conditions over time.
This data focuses on Core Web Vitals and shows how your site performs in real-world scenarios, not just in a test environment.
If your field data is poor, it means real users are experiencing slow or unstable pages, which can affect SEO and user engagement.
Why Both Matter
Lab data helps you identify and fix problems quickly, while field data confirms whether those fixes improve the real user experience.
You should use lab data for testing and troubleshooting, then rely on field data to measure long-term performance.
Focusing on both ensures you’re not just optimizing for test scores, but actually improving how your site performs for real visitors.
How to Read the Opportunities Section
The Opportunities section in PageSpeed Insights shows you specific actions that can improve your page speed.
Each item highlights a problem and suggests a fix, along with an estimate of how much faster your page could load if you resolve it.
This section is one of the most useful parts of the report because it tells you exactly where to focus.
What “Opportunities” Means
Opportunities are performance issues that are slowing down your page. They are prioritized based on impact, so the items at the top usually offer the biggest improvements.
Instead of guessing what to fix, you can follow these suggestions step by step and see measurable results.
Common Examples You’ll See
- Eliminate Render-Blocking Resources
This means some CSS or JavaScript files are stopping your page from loading quickly. These files load before the page can display content. Fix this by deferring non-critical scripts or loading CSS more efficiently. - Properly Size Images
Large images slow down your page, especially on mobile. This suggestion appears when images are bigger than they need to be. Resize and compress images to match their display size. - Reduce Unused CSS/JS
Your site may be loading code that isn’t actually used on the page. This adds unnecessary weight and slows things down. Removing unused CSS and JavaScript reduces file size and improves load time.
Understanding Estimated Savings
Each opportunity includes an estimated time saving, such as “Save 1.2 seconds.” This shows how much faster your page could load if you fix that issue.
Use this as a priority guide—start with the opportunities that offer the highest savings to get the biggest performance gains quickly.
Diagnostics Section Explained
The Diagnostics section provides deeper insights into your page’s performance.
Unlike Opportunities, which focus on direct fixes, Diagnostics highlights underlying issues and best practices that affect how your site loads and behaves.
This section helps you understand why your page may be slow, even if the impact isn’t always shown as a clear time saving.
What Diagnostics Tell You
Diagnostics give you technical details about how your page is built and delivered. It looks at things like JavaScript execution, DOM size, caching, and third-party code.
These insights help you spot inefficiencies that may not be obvious but still affect performance.
Think of this section as a guide to improving overall site quality, not just speed.
Common Warnings and What They Mean
- Avoid Large DOM Size
Your page has too many elements, which can slow down rendering and increase load time. Simplify your layout where possible. - Reduce JavaScript Execution Time
Your browser is spending too much time processing JavaScript. This often leads to slow interactions. Minimize or defer heavy scripts. - Minimize Main-Thread Work
The main thread is overloaded with tasks, causing delays in loading and interaction. Break up long tasks and reduce unnecessary processing. - Avoid Excessive Third-Party Code
External scripts like ads, trackers, or widgets can slow down your site. Only keep what is essential.
How to Prioritize Fixes
Start by focusing on diagnostics that directly impact user experience, such as heavy JavaScript or large DOM size.
Then move to issues caused by third-party tools, since these can often be reduced or removed.
Use this section alongside Opportunities to decide what to fix first—prioritize changes that improve both speed and usability for the biggest overall impact.
Passed Audits
The Passed Audits section shows all the checks your page has successfully met, meaning those areas are already optimized and not causing performance or best practice issues.
Each passed audit confirms that a specific part of your site—such as image optimization, proper caching, or efficient code usage—is working as expected according to Google’s standards.
While it may be tempting to ignore this section and focus only on problems, it still plays an important role because it tells you what not to change or break while optimizing other areas.
This helps you avoid unnecessary edits that could harm performance or introduce new issues.
It also gives you a clear baseline of what’s already done right, so you can focus your time on fixing weak areas instead of guessing.
In many cases, reviewing passed audits can also reveal patterns, showing you which optimization techniques are already working well across your site, making it easier to apply the same approach to other pages.
Step-by-Step: Improving Your Score
Improving your PageSpeed score comes down to fixing the biggest performance issues first. Follow these steps in order to get the fastest results with the least effort.
1. Optimize Images
Images are often the largest files on a page, so optimizing them gives immediate speed gains.
Start by converting images to modern formats like WebP or AVIF, which provide high quality at smaller file sizes.
Then compress your images to reduce their weight without noticeable quality loss.
Also, make sure images are not larger than the space they occupy on the page, as oversized images waste bandwidth and slow down loading.
2. Enable Caching
Caching stores parts of your website so they don’t need to be reloaded every time a user visits.
Browser caching allows returning visitors to load your site faster by saving static files like images, CSS, and JavaScript on their devices.
Server-side caching reduces the work your server has to do by serving pre-built versions of your pages instead of generating them from scratch each time.
Together, these methods significantly reduce load times and server strain.
3. Minify CSS, JavaScript, HTML
Minification removes unnecessary characters like spaces, comments, and line breaks from your code without affecting how it works.
This reduces file sizes and helps your pages load faster. Smaller files mean quicker downloads and less processing time for the browser.
Many tools and plugins can handle this automatically, making it an easy and effective optimization step.
4. Use a CDN
A Content Delivery Network (CDN) stores copies of your site on servers around the world.
When a user visits your site, the CDN delivers content from the server closest to their location.
This reduces distance, lowers latency, and speeds up loading times.
It also helps handle traffic spikes and improves reliability by distributing the load across multiple servers.
5. Reduce Server Response Time
Server response time affects how quickly your page starts loading. Slow hosting, unoptimized databases, or heavy server processes can delay this.
Choose a reliable hosting provider with good performance, and keep your database clean by removing unused data and optimizing tables.
Enabling caching and reducing unnecessary backend tasks will also help your server respond faster and improve overall site speed.
Mobile vs Desktop Results
When you run a test in PageSpeed Insights, you’ll see separate scores for mobile and desktop, and in most cases, the mobile score will be lower because the test simulates real-world conditions like slower internet speeds, weaker devices, and limited processing power.
Mobile users often rely on cellular networks and mid-range phones, which means your site has to work harder to load quickly and respond smoothly, especially if it includes large images, heavy scripts, or complex layouts.
Desktop results, on the other hand, assume faster connections and more powerful hardware, so performance issues are less noticeable.
This is why Google focuses heavily on mobile performance when ranking sites, as the majority of users now browse on mobile devices.
To improve your results, you should follow a mobile-first approach, which means designing and optimizing your site for mobile users first, then scaling up for desktop.
Focus on reducing file sizes, simplifying layouts, minimizing scripts, and ensuring fast loading on smaller screens, because if your site performs well on mobile, it will almost always perform even better on desktop.
Common Mistakes to Avoid
Chasing a Perfect 100 Score
A score of 100 looks great, but it’s not always practical or necessary. Trying to reach a perfect score can lead to unnecessary changes that don’t improve real performance.
Some factors, like third-party scripts or design choices, may slightly lower your score but still provide value to users.
Instead of aiming for perfection, focus on getting your site into the “good” range and fixing issues that have a clear impact on speed and usability.
Ignoring Real User Experience
A high score doesn’t always mean your site feels fast to visitors. Users care about how quickly content appears, how smooth interactions are, and whether the layout stays stable.
Always pay attention to Core Web Vitals and field data, because they reflect real-world usage. If your site feels slow or unstable, that matters more than what the score says.
Over-Optimizing with Too Many Plugins/Tools
Adding too many optimization plugins or tools can actually slow your site down or cause conflicts. Each plugin adds extra code, which increases load time and complexity.
Instead, use a small number of well-chosen tools that handle multiple optimizations efficiently.
Keep your setup simple, test changes one at a time, and remove anything that doesn’t provide clear value.
Best Tools to Use Alongside PageSpeed Insights
- Google Lighthouse (Chrome DevTools)
Built directly into Chrome, Lighthouse lets you run performance tests from your browser without needing external tools. It provides detailed audits similar to PageSpeed Insights, along with insights on performance, accessibility, and best practices. It’s especially useful for testing changes locally before pushing them live. - GTmetrix
GTmetrix offers in-depth performance reports with clear visuals and timelines that show exactly how your page loads. It helps you identify bottlenecks like large files or slow scripts and allows you to test from different locations and devices. - WebPageTest
WebPageTest gives advanced testing options, including multiple test runs, filmstrip views, and waterfall charts. It’s ideal for deeper analysis when you want to see how your page loads step by step and diagnose complex performance issues. - Pingdom
Pingdom is simple and beginner-friendly, providing easy-to-understand performance summaries. It’s useful for quick checks and ongoing monitoring, helping you spot performance drops without diving into complex data.
How Often Should You Test Your Site?
You should test your site regularly to catch performance issues early and keep your speed consistent, especially after any updates or changes, such as installing new plugins, switching themes, adding new features, or updating content, because even small changes can affect load time and user experience.
It’s a good practice to run a test immediately after making changes so you can quickly spot and fix any problems before they impact visitors.
Beyond that, set a simple monitoring schedule, such as testing your site weekly or monthly, depending on how often you update it, to ensure performance stays stable over time.
Regular testing helps you notice gradual slowdowns that might not be obvious at first, such as growing page sizes or accumulating unused code.
You should also track your results over time instead of relying on a single test, as this allows you to see trends, measure improvements, and understand how changes affect performance in the long run.
Final Thoughts
PageSpeed Insights is not just about chasing a high score, but it’s about understanding what’s slowing your site down and fixing what truly impacts user experience.
Focus on the metrics and recommendations that matter, not just the number.
Keep testing and improving your site over time, especially after changes, to maintain fast and reliable performance.
Start now by running a test on your site and applying the fixes that will make the biggest difference.
FAQs
Is PageSpeed Insights accurate?
Yes, it’s reliable, but it combines simulated tests (lab data) and real user data (field data). Use both for a complete picture.
Why does my score change?
Scores vary due to network conditions, server performance, updates, and real user data fluctuations.
What is a good PageSpeed score?
A score of 90 or above is considered good, but focus more on Core Web Vitals than the number.
Does PageSpeed affect SEO?
Yes, page speed and Core Web Vitals are ranking factors and impact user experience.
How can I fix issues quickly?
Start with high-impact fixes like optimizing images, enabling caching, and reducing unused CSS/JavaScript.