Page Speed Checker

The Page Speed Checker runs Google’s Lighthouse test on any page, for mobile or desktop, and turns the results into plain language: a score out of 100, the Core Web Vitals that matter for real visitors, and the fixes that would save the most time.

Why page speed matters

A slow page loses people. Visitors on mobile data, which is most visitors in Pakistan, often give up if nothing appears in the first few seconds. Slow pages also convert worse: fewer sign-ups, fewer sales, fewer clicks on ads and affiliate links.

Google uses page experience signals, including Core Web Vitals, as part of how it ranks pages. Speed alone will not lift a weak page to the top, but between two similar pages, the faster one has an advantage, and visitors stay longer on it.

How to use the checker

1. Paste the page address, like https://example.com/blog/post/. Test your most important pages, not only the home page.

2. Choose Mobile or Desktop. Start with Mobile. It uses a slower simulated phone and network, which is closer to how many real visitors browse.

3. Press Test speed and wait 20 to 40 seconds while Google loads the page.

4. Read the score and the six metrics.

5. Work through the top fixes, starting with the one that saves the most time.

Understanding the score

The score is a lab test: one simulated visit on a fixed device and network. It changes a little between runs because of network conditions and server load. Test a few times and look at the trend.

The metrics in plain words

In real-world data, Google measures responsiveness with INP (Interaction to Next Paint). The lab test cannot click like a real person, so TBT is the closest lab measure: lower TBT usually means better INP.

Lab data vs field data

For popular pages, Google also has field data: real measurements from Chrome users who visited the page over the last 28 days. When it exists, the tool tells you. Field data is what Google uses for ranking signals, so it matters more than the lab score. If your lab score is low but field data is good, real visitors are fine. If field data is poor, fix it even if the lab score looks acceptable.

The most common fixes

Images that are too large

The number one cause of slow pages. A 4 MB phone photo used as a 800 pixel wide image wastes almost all its bytes. Resize images to the size they are shown, compress them, and use modern formats like WebP. In WordPress, an image optimisation plugin can do this automatically.

Slow server response

If server response time is high, the server takes too long before anything happens. Turn on page caching, reduce heavy plugins, and consider better hosting with a data centre near your visitors. Check where your server is with the Hosting Checker.

Render-blocking CSS and JavaScript

Files loaded in the page head stop the browser from showing anything until they finish. Defer non-essential scripts, remove unused plugins, and let your caching plugin combine or delay scripts carefully. Test after each change, because aggressive script delays can break features.

Too much JavaScript

Sliders, chat widgets, popups, tracking codes and heavy page builders add up. Each one can block the page for hundreds of milliseconds on a phone. Remove what you do not need.

Layout shifts

The page jumps when images load without set sizes, when ads push content down, or when web fonts swap in late. Give images width and height, reserve space for ads, and preload your main font.

Web fonts

Loading several font families and weights from outside servers costs time. Use one or two fonts, host them on your own site, and use font-display: swap.

A sensible order of work

1. Turn on page caching and check server response time improves.

2. Compress and resize images, starting with the biggest one above the fold.

3. Remove plugins and scripts you do not need.

4. Fix layout shifts by setting image and ad sizes.

5. Fine tune script loading and fonts.

6. Test again on mobile and compare.

About the free quota

The speed test uses Google’s free PageSpeed Insights service. Without an API key, all sites share a small free quota, so during busy times you may see a “busy” message. Website owners using this theme can add a free Google API key in the theme settings to give their site its own quota.

Speed tips for WordPress sites

• Choose a lightweight theme. Themes that load many fonts, sliders and animations on every page start slow before you add any content.
• Use a caching plugin that matches your server. On LiteSpeed servers, LiteSpeed Cache is usually the best choice.
• Limit page builders to pages that really need them. Plain block editor pages are much lighter.
• Delete unused plugins, do not just deactivate them, and avoid plugins that load scripts on every page for a feature used on one page.
• Lazy load images and videos below the fold. WordPress lazy loads images by default; make sure your hero image is not lazy loaded.
• Replace embedded videos with a thumbnail that loads the player only when clicked.
• Keep PHP updated in your hosting panel. Newer PHP versions are faster.

Speed for visitors in Pakistan

Many visitors in Pakistan browse on mid-range Android phones over 4G or shared Wi-Fi, where speed varies a lot during the day. A page that loads in one second in a city office can take several seconds in a mountain valley. Practical steps that help most:

1. Host close to your audience, or use a CDN with servers in the region.

2. Keep the first screen light: one compressed hero image, a heading and text.

3. Avoid autoplay videos and large background videos.

4. Test on mobile mode here, and on a real phone using mobile data.

Do not chase a perfect 100

Going from 40 to 85 makes a huge difference for visitors. Going from 92 to 100 often costs hours and removes useful features for almost no real benefit. Aim for green Core Web Vitals and a score in the 80s or 90s on mobile, then spend your time on content.

Track progress over time

Write down the mobile score and the main metrics for your five most important pages today. After each improvement, test again and note the change. Over a few weeks you will see which fixes matter on your site. Google Search Console also has a Core Web Vitals report that groups your pages by real user experience, which is the best long-term view.

Frequently asked questions