Page speed is how quickly a web page loads and becomes usable for a visitor. Google measures it through Core Web Vitals — Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS) — and a fast page keeps visitors on your site, supports your rankings and turns more traffic into enquiries. You can improve it by compressing images, caching, removing heavy scripts and using good hosting.
I’m Hamza Zahid, an SEO specialist in Karachi, and page speed is one of the most common problems I find when I audit websites for businesses in Pakistan and the UK. A beautiful website that takes too long to load on a mobile connection quietly loses customers every day. The good news is that most page speed problems come from a handful of causes, and you can fix many of them without rebuilding your site.
In this guide I’ll explain what page speed means, how Google measures it, how to test your own pages and the exact steps I follow to make websites faster.
Page speed is not a single number. It describes several moments in the loading process: when the first content appears, when the main content is visible, when the page responds to taps and clicks, and whether elements jump around while loading.
It matters for three reasons:
Google groups its main page speed and usability metrics under Core Web Vitals. These are the thresholds Google describes as “good” on web.dev:
| Metric | What It Measures | Good | Needs Improvement | Poor |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | How fast the main content loads | 2.5 s or less | 2.5 – 4 s | Over 4 s |
| INP (Interaction to Next Paint) | How quickly the page responds to input | 200 ms or less | 200 – 500 ms | Over 500 ms |
| CLS (Cumulative Layout Shift) | How much the layout jumps while loading | 0.1 or less | 0.1 – 0.25 | Over 0.25 |
Google assesses these at the 75th percentile of real visits, so most of your visitors need a good experience, not just people on fast Wi-Fi.
Before fixing anything, measure. These are the tools I use:
Always test your important pages separately — homepage, service pages, blog posts and product pages — because each template has different problems. Test on mobile first, since that is where page speed issues hurt most. You can read more about choosing tools in my guide to SEO tools.
This is the order I follow when I improve page speed for a client website. Start at the top, because the early steps usually give the biggest wins.
Large images are the most common cause of slow pages I see. Resize images to the size they actually display at, convert them to WebP or AVIF, and compress them. Add width and height attributes so the browser reserves space and the layout doesn’t shift. Lazy-load images below the fold, but never lazy-load the main hero image, because that delays LCP.
Page caching serves a ready-made copy of your page instead of building it on every visit. On WordPress, plugins such as LiteSpeed Cache (on LiteSpeed servers) or WP Rocket handle this. Browser caching lets returning visitors reuse files they already downloaded.
Page builders, sliders, chat widgets, pop-ups and tracking tags all add code. Remove plugins you don’t use, delay non-essential scripts until after the page loads, and minify CSS and JavaScript. This step usually has the biggest effect on INP.
If your server is slow to respond, every other metric suffers. Choose reliable hosting with servers close to your audience, keep PHP updated, and consider a CDN so visitors in Pakistan, the UK or anywhere else get files from a nearby location.
Custom fonts can block text from showing. Limit the number of font families and weights, host fonts locally where possible, and use font-display: swap so text appears immediately.
Reserve space for images, videos, ads and embeds. Avoid inserting banners above existing content after the page loads. These small fixes usually bring CLS into the good range.
After each change, test again in PageSpeed Insights. Real-user data in Search Console updates over a 28-day window, so give it time before judging the result. I include this monitoring in every SEO audit I run.
Most of my clients use WordPress, so here are the quick wins I apply first:
If you want to go further, my on-page SEO checklist covers how speed fits with titles, headings and content.
Before any new page goes live on a client site, I run through this short checklist. It takes a few minutes and prevents most problems from reaching real visitors:
Page speed is one part of technical SEO, and it works best alongside the other parts. A fast page that Google can’t crawl, or that answers the wrong search intent, still won’t rank. A slow page with excellent content may still rank, but it will lose visitors who give up before it loads. That’s why I never treat speed as a separate project. When I audit a website, I look at crawling and indexing, content quality, internal links and structured data together, then prioritise the fixes that affect the most important pages. If you’ve already added structured data, my schema markup guide explains how to keep it lightweight so it doesn’t slow your pages down.
Yes. Page experience signals, including Core Web Vitals, are part of Google’s ranking systems. They are not more important than relevant, helpful content, but they can help when competing pages are similar.
In PageSpeed Insights, a lab score of 90 or above is considered good. More important is passing Core Web Vitals in real-user data: LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less.
Mobile devices have less processing power and often slower connections, so heavy images and JavaScript hurt them more. PageSpeed Insights also simulates a slower mobile device, which makes problems more visible.
Yes. Slow servers increase the time to first byte, which delays everything else. Good hosting, server-level caching and a CDN usually improve page speed noticeably.
Lab tests update immediately, but the Core Web Vitals report in Search Console uses real-user data collected over 28 days, so it can take a few weeks to reflect your fixes.
If your website feels slow or is failing Core Web Vitals, I can find the exact causes and fix them without breaking your design. Take a look at my technical SEO services, or contact me to talk about your page speed and SEO goals.
WhatsApp us