Google PageSpeed Insights Plugin for WordPress

How Do You Check Google PageSpeed Insights in WordPress?

You check a page's Google PageSpeed Insights score by entering its URL at pagespeed.web.dev, or from inside WordPress with a plugin that calls the PageSpeed API. WP Adminify's Google PageSpeed addon runs the test in your dashboard, saves your mobile and desktop scores over time, and lets you analyse any URL without leaving wp-admin. Use it alongside our WordPress performance optimization guide to fix what the report flags, and see the full WordPress performance toolkit.

Benefits of the Pagespeed Insights for WordPress

Are slow web pages making it hard for you to reach your traffic goals? With the help of the Google Pagespeed Insights plugin, you can identify and solve the issues yourself. Experience a better UI and identify your pagespeed issue.

Individual report for Mobile & Desktop

You can analyze full page-speed reports for both mobile and desktop devices. This report will be saved as history in our plugin. It’s a great advantage for you to access detailed history reports whenever you need.

Google Pagespeed Test for Mobile

Google Pagespeed Test for Desktop

Google Pagespeed History Page

Whenever you search for any webpage speed, it will be listed on your history page. After you do some modifications to compare the present pagespeed with before, you can access the history page to check the previous page speed.

Unlimited history for Google Pagespeed

Automatic save when you check any pagespeed

Analyze Any Webpage Speed

Not only your website, but you can also check any webpage's speed. You have the freedom to test data from any website. Just copy your desired page URL and paste it inside the page speed test URL field.

Support pagespeed test for internal and external URLs

Saves data for any external URL

Remove Google Pagespeed history

Keeping too much history can be annoying to you. You can remove your history that you don’t need in the future. It will help you to clean your history page so that you can access your necessary page speed history easily.

One click delete

Prompt final permission before you delete

Check the Report for existing saved data

If you have searched any pages, they will be stored in your history. After fixing some issues on your page, you can compare the previous speed history with the new history. It will help you to get a better idea of what’s already fixed and what needs to be fixed.

Check your previous performance report

Compare with your present data

What Do PageSpeed Insights Scores Actually Mean?

A PageSpeed Insights report gives you two separate verdicts. The big 0 to 100 number is a Lighthouse lab score, simulated in a controlled test. The Core Web Vitals assessment above it is field data from real Chrome visitors. A WordPress site can pass Core Web Vitals and still score 62, because the two measure different things.

Field data and lab data measure different visits

Field data comes from the Chrome User Experience Report, a rolling 28 day sample of real visits to your site, scored at the 75th percentile so one fast visitor cannot hide a slow experience for everyone else. Lab data comes from a single Lighthouse run on Google's hardware. That is why the two disagree so often: the lab run is one simulated visit on a throttled connection, while the field data is thousands of real ones on real phones and real networks. Trust the field data for how your WordPress site actually performs, and use the lab score as the diagnostic that tells you what to fix.

The three Core Web Vitals Google grades

Largest Contentful Paint (LCP) measures how long the main content takes to appear, and Google wants it under 2.5 seconds. Interaction to Next Paint (INP) measures how quickly the page responds to a click or tap, with a 200 millisecond threshold. Cumulative Layout Shift (CLS) measures how much the layout jumps while loading, and should stay under 0.1. On WordPress, LCP is usually the hero image or a slider, INP is usually heavy JavaScript from plugins, and CLS is usually ads, embeds, or a web font swapping in late.

What counts as a good score

90 to 100 is green, 50 to 89 is orange, and anything under 50 is red. Mobile scores are always lower because Lighthouse throttles CPU and network to imitate a mid tier Android phone on a slow 4G connection. A realistic target for a content heavy WordPress site is 90 or above on desktop and 50 or above on mobile, with all three Core Web Vitals passing. Chasing a perfect 100 on mobile usually costs more than the ranking benefit is worth.

What PageSpeed Insights Flags Most Often on WordPress Sites

The same handful of audits come back on almost every WordPress install, and each one traces to a familiar cause. Reading the report against the list below turns a wall of warnings into a short queue of actual work. Our WordPress performance optimization guide covers each fix in depth.

Render blocking resources and unused CSS or JavaScript

Every active plugin queues its own stylesheet and script, and page builders load their full asset bundle on pages that use none of it. Lighthouse counts those bytes twice, once as render blocking and once as unused. Deferring non critical scripts, loading CSS only where a plugin is actually used, and removing the emoji, embed, and block library assets a site never touches will move the score more than any other single change.

A slow server response time

Time to First Byte sits ahead of everything else in the waterfall, so a slow host caps your score no matter what you optimise on the front end. Shared hosting without page caching, an oversized options table with heavy autoloaded data, and uncached admin AJAX traffic are the usual culprits. If the admin side feels slow too, the reasons a WordPress admin gets slow overlap heavily with the reasons the front end does.

Images that hold back LCP

The largest element on most WordPress pages is an image, so image handling decides LCP. Serve WebP or AVIF, size the file to the container rather than uploading a 4000 pixel original, preload the hero image, and make sure lazy loading is switched off for anything above the fold. Lazy loading the LCP image is one of the most common self inflicted score problems on WordPress.

Track the number after each fix, not just before

Any of these changes can help on one template and do nothing on another, which is why a single score is worth so little on its own. Running the test from inside the dashboard and keeping the result means you can compare this week against last week per page. The page speed history view stores each run against the post it came from.

Why run PageSpeed Insights inside WordPress?

Google's own tool at pagespeed.web.dev tests one URL at a time and remembers nothing. You paste a link, read a score, fix something, paste the link again, and the earlier score is gone. That is fine once. It is useless when you are trying to answer the only question that matters after an optimisation pass: did this actually help, or did it just feel faster?

Running the same Lighthouse test from inside the dashboard changes two things. Every result is stored against the post or page it came from, so you get a history rather than a snapshot, and you can test any page from the list you are already looking at instead of copying URLs into another tab. Scores still come from Google, so the numbers match what you would see on their site.

Google PageSpeed Insights for WordPress - FAQs