A website may look attractive and work well, but that does not always mean it performs well. Some pages take too long to display their main content, buttons respond slowly, or images move around while loading. These problems can affect how visitors use your website.
But how can you find out what is causing these issues?
Google PageSpeed Insights is a free tool that helps website owners and developers measure page performance and identify areas that need improvement. It provides useful information about loading speed, responsiveness, visual stability, and technical issues affecting the user experience.
In this guide, we will explain how to use PageSpeed Insights, understand its reports, identify common performance problems, and apply practical methods to improve your website.
What Is Google PageSpeed Insights?
Google PageSpeed Insights is an online tool developed by Google to analyse the performance of individual web pages on desktop and mobile devices.
When you enter a website URL, the tool generates a report containing performance scores, Core Web Vitals information, and recommendations for improving the page.
It uses Lighthouse to generate laboratory performance data. When sufficient real-user data is available, it also provides field data from the Chrome User Experience Report (CrUX).
This means you can understand both how a page performs in a controlled test and how real visitors experience it.
Why Is Website Performance Important?
Website performance affects more than just loading time. It influences how visitors interact with your content and whether they can complete important actions.
For example, imagine a customer opening your service page to enquire about your business. If the page takes too long to load or the enquiry button does not respond immediately, the customer may leave.
Here are some reasons why website performance matters:
- Better User Experience: Visitors can access information without unnecessary waiting.
- Mobile Experience: Optimised pages are easier to use on smartphones and slower network connections.
- Improved Engagement: Smooth navigation encourages visitors to explore other pages.
- Better Conversions: Responsive forms, buttons, and page elements make it easier for users to contact your business.
- Search Performance: Google uses Core Web Vitals as part of its page experience evaluation, although good scores alone do not guarantee higher rankings.
A well-performing website helps visitors complete their activities without unnecessary delays.
How to Perform a PageSpeed Insights Test
You can check your website performance without installing additional software.
Follow these steps to generate a report.
Step 1: Open Google PageSpeed Insights
You will find a field where you can enter the URL of the page you want to analyse.
Step 2: Enter Your Website URL
Copy the complete URL of your webpage and paste it into the testing field.
You can test different pages separately, such as:
- Homepage
- Service pages
- Blog articles
- Contact page
- Product pages
- Landing pages
Testing individual URLs is important because the homepage and internal pages may have completely different performance issues.
Step 3: Start the Analysis
Click the Analyse button and wait for the test to complete.
Google PageSpeed Insights will generate separate reports for mobile and desktop performance.
Step 4: Compare Mobile and Desktop Results
Review both reports instead of checking only the desktop score.
Mobile devices may experience slower loading because of limited processing power, network conditions, and different screen sizes.
A page that performs well on desktop may still have problems on mobile.
Step 5: Review the Recommendations
Scroll through the report and examine the performance opportunities and diagnostics.
Each recommendation explains a possible issue and provides information that can help developers fix it.
Do not try to fix every warning without understanding its impact. Start with problems that affect the main content and user interactions.
Understanding the Google PageSpeed Insights Report
The report contains several sections. Understanding these measurements helps you decide which improvements are necessary.
1. Performance Score
The Performance Score gives an overall indication of how well a page performs in Lighthouse testing.
Google PageSpeed Insights generally classifies scores as follows:
- 90–100: Good
- 50–89: Needs Improvement
- 0–49: Poor
The score is calculated using several performance metrics, not just the total time required to load a page.
A low score does not always mean that the entire website is poorly developed. It may be caused by a few specific problems, such as a large hero image or excessive JavaScript.
Focus on understanding the individual metrics rather than trying to achieve a perfect score.
2. Largest Contentful Paint (LCP)
Largest Contentful Paint measures how long it takes for the largest visible content element to appear on the screen.
This may be a banner image, a large heading, or another major content element.
A slow LCP can happen because of:
- Large image file sizes
- Slow server response
- Render-blocking CSS
- Unnecessary JavaScript execution
- Delayed loading of the main image
How to improve LCP:
- Compress and resize the main image.
- Improve server response time.
- Avoid lazy loading the main LCP image.
- Prioritise important above-the-fold resources.
- Reduce unnecessary CSS and JavaScript.
Good LCP target: 2.5 seconds or less.
3. Interaction to Next Paint (INP)
Interaction to Next Paint measures how quickly a webpage responds visually after a visitor interacts with it.
For example, when someone clicks a navigation menu, opens a dropdown, or submits a form, the page should respond without noticeable delay.
Poor INP can be caused by:
- Heavy JavaScript execution
- Long-running browser tasks
- Too many event listeners
- Complex third-party scripts
- Inefficient frontend code
How to improve INP:
- Break long JavaScript tasks into smaller tasks.
- Remove unnecessary event listeners.
- Reduce unused JavaScript.
- Avoid excessive third-party scripts.
- Optimise click, form, and menu interactions.
Good INP target: 200 milliseconds or less.
4. Cumulative Layout Shift (CLS)
Cumulative Layout Shift measures unexpected movement of visible elements while a webpage loads.
For example, you may try to click a navigation link, but an image loads above it and pushes the link downward.
This makes the website difficult to use.
Common reasons include:
- Images without defined dimensions
- Advertisements loading without reserved space
- Web fonts changing text layout
- Dynamically inserted content
- Elements moving after CSS loads
How to improve CLS:
- Define width and height for images.
- Reserve space for advertisements and embedded content.
- Use suitable font-display settings.
- Avoid inserting content above existing elements.
- Maintain consistent layouts during loading.
Good CLS target: 0.1 or less.
Practical PageSpeed Optimization Techniques
After understanding the report, the next step is to fix the problems affecting your website.
Here are some useful PageSpeed optimization techniques developers can apply.
1. Optimise Website Images
Images often contribute a large amount of page weight, especially on websites with banners, portfolios, and service galleries.
Uploading large images without resizing them can increase loading time.
To improve image performance:
- Convert suitable images into WebP or AVIF formats.
- Resize images according to their display dimensions.
- Compress images without noticeable quality loss.
- Use responsive images for different screen sizes.
- Avoid loading unnecessary high-resolution images.
For example, if an image appears at 500 pixels wide, uploading a 3000-pixel image may create unnecessary loading overhead.
2. Minify CSS and JavaScript
CSS controls the appearance of your website, while JavaScript manages interactive features.
Large files containing unused code and unnecessary formatting can increase download and processing time.
Minification removes unnecessary characters without changing the intended functionality.
Developers should:
- Minify CSS files.
- Minify JavaScript files.
- Remove unused CSS.
- Remove unnecessary JavaScript.
- Avoid loading duplicate libraries.
After making these changes, test your website to ensure that menus, sliders, forms, and other features still work correctly.
3. Eliminate Render-Blocking Resources
Some CSS and JavaScript files prevent the browser from displaying important content immediately.
This can delay the appearance of the main section of your webpage.
You can address this by:
- Identifying critical CSS.
- Loading non-critical JavaScript with defer where appropriate.
- Using async for independent scripts.
- Removing unnecessary stylesheets.
- Avoiding excessive external resources.
Do not apply async or defer blindly. Scripts that depend on one another may stop working if their loading order changes.
4. Enable Browser Caching
Browser caching allows frequently used website resources to be stored on a visitor's device.
When someone returns to your website, the browser may reuse previously downloaded images, stylesheets, and JavaScript files instead of requesting everything again.
To improve caching:
- Configure suitable Cache-Control headers.
- Set appropriate expiry periods for static resources.
- Use file versioning when assets are updated.
- Apply caching to images, fonts, CSS, and JavaScript.
This can reduce repeated downloads and improve the experience for returning visitors.
5. Improve Server Response Time
Sometimes the main problem is not the frontend design. The server may take too long to generate and deliver the webpage.
Common causes include:
- Poor hosting resources
- Slow database queries
- Inefficient backend code
- Missing server-side caching
- Excessive database operations
- High server workload
For Laravel websites, developers should review database queries, controllers, middleware, application caching, and backend processes.
Improving server response time can help important page content appear sooner.
6. Reduce Unnecessary Plugins and Third-Party Scripts
Chat widgets, analytics tools, tracking scripts, social media integrations, and external libraries can increase browser workload.
Some websites continue loading scripts even when the related feature is no longer used.
Review your website integrations and remove outdated tools.
Where possible, load non-essential scripts only when required. This helps reduce unnecessary network requests and JavaScript execution.
7. Use Lazy Loading Correctly
Lazy loading allows images and other supported resources to load when they are close to entering the visible screen area.
This is useful for blog images, portfolios, and content placed further down a page.
For example:
<img src="service-image.webp"
alt="Website development services"
width="600"
height="400"
loading="lazy">
However, avoid applying lazy loading to the main hero image or other important LCP elements. These resources should be prioritised.
8. Use a Content Delivery Network
A Content Delivery Network (CDN) distributes copies of eligible website resources across multiple servers.
When visitors access your website, the CDN can deliver supported files from a server closer to their location.
This can reduce network delays, especially when your website serves visitors from different geographical regions.
Choose a CDN based on your website requirements, hosting environment, and traffic volume.
What Are the Common PageSpeed Insights Warnings?
While testing your website, you may see several warnings under Opportunities and Diagnostics.
Here are some common examples and what they mean.
| PageSpeed Warning | What It Means |
|---|---|
| Properly size images | Images are larger than their displayed dimensions require |
| Serve images in next-gen formats | Images could use more efficient formats |
| Eliminate render-blocking resources | Some resources delay initial rendering |
| Reduce unused JavaScript | Unnecessary JavaScript is being downloaded |
| Reduce unused CSS | Unused styles increase page resource size |
| Enable text compression | Text resources are not compressed efficiently |
| Avoid enormous network payloads | The total downloaded page resources are too large |
| Reduce initial server response time | The server takes too long to respond |
| Avoid large layout shifts | Page elements move unexpectedly during loading |
Not every warning requires immediate attention. Review the affected resource and determine whether the suggested change will improve actual user experience.
How to Prioritise Website Performance Optimization
Trying to fix all PageSpeed warnings at once can waste development time.
Instead, identify the issues that have the greatest impact on your website.
A practical order is:
High Priority
- Improve server response time.
- Fix slow LCP.
- Optimise large images.
- Reduce excessive JavaScript.
- Resolve major interaction delays.
Medium Priority
- Remove render-blocking resources.
- Improve browser caching.
- Reduce unused CSS.
- Optimise font loading.
- Configure image dimensions.
Ongoing Maintenance
- Review third-party scripts.
- Monitor mobile performance.
- Check page weight after new updates.
- Retest important landing pages.
This approach makes website performance improvement more manageable.
Google PageSpeed Insights vs GTmetrix: What Is the Difference?
Both tools help developers identify website performance problems, but they provide different types of information.
| Feature | Google PageSpeed Insights | GTmetrix |
|---|---|---|
| Main Purpose | Website performance and user experience analysis | Detailed page loading analysis |
| Performance Score | Lighthouse score | Performance and structure grades |
| Core Web Vitals | Lab data and available real-user field data | Relevant Lighthouse metrics and available field data |
| Waterfall Chart | Not available in the same format | Available |
| Resource Analysis | Opportunities and diagnostics | Detailed request-level analysis |
| Testing Devices | Mobile and desktop | Depends on available test configuration |
| Best Use | Understanding page performance and Core Web Vitals | Investigating individual resource loading issues |
Using both tools can provide a better understanding of website performance.
PageSpeed Insights helps you review performance measurements and recommendations, while GTmetrix provides additional information about how individual resources are loaded.
How Often Should You Perform Website Performance Testing?
Website performance can change whenever you add new features, update plugins, upload images, or modify your website design.
Regular testing helps you identify problems before they affect more visitors.
Consider testing your website:
- After launching a new webpage.
- After changing hosting providers.
- After installing new plugins or scripts.
- After redesigning important pages.
- After making major CSS or JavaScript changes.
- During regular website maintenance.
Always compare results using similar testing conditions. This makes it easier to understand whether your changes have improved performance.
Conclusion
Google PageSpeed Insights is a useful tool for understanding how your website performs and identifying technical issues that affect visitors. However, checking the score alone is not enough. You need to understand the recommendations, identify the actual causes, and apply suitable improvements.
Start with important areas such as image optimisation, JavaScript execution, server response time, and Core Web Vitals. After making changes, test the same pages again to measure the results.