FREE TOOL
WordPress Speed Test
Run a real test through the Google PageSpeed Insights API. You will see real-user field data where Google has it, alongside Lighthouse lab data, kept clearly separate.
How This WordPress Speed Test Works
This free tool sends the URL you enter to Google’s PageSpeed Insights API. Google analyses the public page using a simulated mobile or desktop environment and returns performance information.
The test does not make changes to your website. It only reads publicly available data and presents the results in a clear format.
For the best result, enter the complete HTTPS address:
How to Use the Tool
- Enter the full website or page URL.
- Select Mobile or Desktop.
- Click Run Speed Test.
- Review the performance score, loading metrics and diagnostic findings.
Testing both Mobile and Desktop is recommended because a page may perform differently across devices.
Understanding the Results
Performance Score
The Lighthouse performance score ranges from 0 to 100. A higher score generally indicates better performance during that specific test.
Scores may vary because of server load, caching, network conditions, advertisements and third-party scripts. Focus on repeated issues rather than a single test result.
Largest Contentful Paint
LCP measures how quickly the largest visible page element loads. This is often a hero image, featured image or large heading section.
Large images, slow hosting and render-blocking resources can increase LCP.
First Contentful Paint
FCP measures when the first visible content appears. Slow server responses, stylesheets, scripts or fonts may delay this metric.
Cumulative Layout Shift
CLS measures visual stability. A low score means page elements remain stable instead of moving unexpectedly while the page loads.
Images without dimensions, advertisements and late-loading fonts can cause layout shifts.
Total Blocking Time
TBT measures how long the browser is blocked by heavy JavaScript tasks during the Lighthouse test.
Too many plugins, tracking scripts or page-builder assets can increase blocking time.
Field Data vs Lab Data
Field data represents eligible real Chrome-user experiences collected by Google over time.
New or low-traffic websites may show:
No real-user data available
This is not an error. It usually means Google does not yet have enough eligible traffic data for that page or domain.
Lab data comes from a single simulated Lighthouse test. It is useful for identifying technical problems, but it does not represent every visitor.
What Should You Fix First?
Start with the issues that have the greatest effect on loading and usability:
- Compress and resize large images
- Review render-blocking CSS and JavaScript
- Improve hosting and server response time
- Enable appropriate page caching
- Remove unnecessary plugins and scripts
- Reserve space for images, embeds and advertisements
- Retest after each meaningful change
Avoid changing several performance settings at the same time. Make one improvement, clear the relevant cache and run the test again.
Test Limitations
A speed test is a snapshot. Results can vary because of server conditions, cache state, network behaviour and third-party services.
The findings are provided for diagnosis and should not be applied blindly. Performance changes should be tested carefully to avoid breaking important website features.
Only test websites that you own or are authorised to analyse.
Frequently Asked Questions
Does this tool modify my website?
No. It only analyses the public URL and displays information returned by Google.
Why is my mobile score lower?
Mobile testing uses more restricted simulated hardware and network conditions, so performance issues may be more noticeable.
Is a score of 100 required?
No. A fast, stable and useful website is more important than chasing a perfect score.
Why does the score change?
Temporary server load, caching and third-party scripts can cause small differences between tests.
When should I test again?
Retest after changing your theme, plugins, hosting, caching, advertisements, images or tracking scripts