LCP
Largest Contentful Paint
How long until the main thing on screen appears. Usually your hero image or headline. This is the metric most WordPress sites fail, and the one where the biggest wins are available.
Good: under 2.5sPoor: over 4s
WordPress Speed Optimization
Visitors leave before a slow page finishes painting, and Google notices. I find what is actually causing it on your site, fix the real bottlenecks, and show you the before and after in Core Web Vitals. No rebuild unless you genuinely need one.
Measured on real Core Web Vitals, not just a lab score
What Gets Measured
PageSpeed Insights gives you a score out of 100. Google does not rank on that score. It uses Core Web Vitals collected from real Chrome visitors, which is why a site can show 95 in a lab test and still fail in the field. These are the three that matter.
LCP
How long until the main thing on screen appears. Usually your hero image or headline. This is the metric most WordPress sites fail, and the one where the biggest wins are available.
INP
How quickly the page responds when someone taps or clicks. Replaced First Input Delay in 2024. Heavy JavaScript from stacked plugins is the usual culprit.
CLS
How much the page jumps around while loading. Caused by images without dimensions, late-loading fonts and injected banners. Cheap to fix and very noticeable to visitors.
The Usual Suspects
In roughly the order I find them. Notice that only one of these is about hosting, which is where most people start.
Installed, activated, and left on defaults. Minification, deferral and critical CSS all switched off. Extremely common, and the single fastest win available.
Page builders and addon packs load their assets on every page whether that page uses them or not. Removing what is not needed often halves the payload.
A 3000px JPEG serving as the largest element above the fold. Wrong format, wrong dimensions, not preloaded. This alone can account for seconds of LCP.
Google Fonts pulled from a third party with no display rule, so text is invisible until the font arrives. Hosting them locally with a swap rule fixes it.
Fifteen plugins where six would do, several loading scripts sitewide for a feature used on one page. Every one adds queries, assets and update risk.
Genuinely a factor, but usually not the main one. I will tell you honestly if hosting is your bottleneck rather than selling you a migration you do not need.
Why Site Speed Matters
Speed is one of the few things that touches everything at once: what visitors think of you, how far Google trusts you, and how many people actually get as far as your contact form. Here is what a faster site changes.
Most visitors decide whether to wait in the first couple of seconds. A faster first paint keeps people who would otherwise hit back before your page even appeared.
Speed does not bring you more visitors on its own. It stops you losing the ones you already paid for, which is usually the cheaper win.
Core Web Vitals are a confirmed ranking factor. They are not the biggest one, but between two similar pages the faster one has the advantage.
Most of your traffic arrives on a phone, often on patchy mobile data. A page that feels fine on your office wifi can be painful on a 4G connection in a car park.
If you run Google Ads, every click that bounces on a slow landing page is money spent for nothing. Landing page experience also feeds into what you pay per click.
Nobody thinks "this server is under-resourced". They think the business looks amateur. Speed is the first impression you never get to explain.
Faster responses let search engines get through more pages in the time they allocate you, so new content gets found and indexed sooner.
Fixing layout shift means buttons stay where people aim. Fewer mis-taps, fewer people giving up on a form halfway through.
Most small business sites in most industries have never had a speed pass. It is one of the few advantages still sitting there unclaimed.
Why Plugins Aren't Enough
Nearly every slow site I audit already has a caching plugin installed. LiteSpeed Cache, WP Rocket, W3 Total Cache, something. It is activated, page caching is on, and every other setting is untouched.
That is the difference between owning a tool and using it. Minification, JavaScript deferral, critical CSS, unused CSS removal, font display rules, image dimensions, preloading the right hero asset. None of that happens by default, and some of it will break your site if switched on blindly, which is why defaults are conservative.
The work is knowing which settings apply to your particular build, testing each one, and checking nothing broke. That is most of what you are paying for.
What's Included
Every item below is done by hand on your site and checked afterwards. Nothing here is a plugin switched on and left at its defaults.
Every image resized to what the layout actually needs and converted to WebP. Width and height added so the page stops jumping while they load.
The one image that decides your LCP gets found and preloaded, so the browser starts fetching it immediately instead of discovering it late.
Page caching, browser cache headers and object caching configured for your specific host and theme, then tested. Not a generic preset.
Stylesheets combined and minified, unused rules removed, and critical CSS generated so the page can render before the rest arrives.
Non-essential scripts deferred or delayed until interaction, unused scripts removed, and everything retested so nothing breaks.
Google Fonts pulled onto your own server with a swap rule, so text appears immediately instead of waiting on a third party.
Every active plugin reviewed for what it loads and where. Anything earning nothing gets removed or replaced with something lighter.
Old post revisions, expired transients and orphaned tables cleared out, so queries run against a smaller, tidier database.
A CDN configured so your images, CSS and scripts are served from a server near your visitor rather than from one location.
Every redirect mapped and the unnecessary hops removed, so no request takes three round trips to reach the page it wanted.
Dimensions set on images, embeds and ad slots so nothing moves once it loads. This is the cheapest Core Web Vital to fix and the most obvious to visitors.
The same pages measured before and after on both mobile and desktop, with a written note of what changed and what to watch.
The Process
Every change is tested on a staging copy before it touches your live site, and the same pages are measured before and after so the difference is verifiable rather than claimed.
Step 01
Measure your key pages on mobile and desktop, pull field data from Search Console where it exists, and identify what is actually blocking the render. A score is not a diagnosis.
Step 02
Caching configured properly, minification and deferral enabled and tested, emoji and query strings dealt with, font display rules set. Usually the largest single improvement, and the lowest risk.
Step 03
Hero image identified and preloaded, everything converted to WebP at correct dimensions, width and height attributes added to stop layout shift, below-fold images lazy loaded.
Step 04
Critical CSS generated, unused CSS removed, plugin-by-plugin review of what loads where, and addon widgets replaced with core equivalents or a few lines of CSS where sensible.
Step 05
Same pages re-measured, every template checked for visual regressions, and a written summary of what changed and why. Field data takes about 28 days to catch up, and I will tell you what to watch.
Proof
Before selling this service I ran it on my own site. You can check these numbers yourself right now: put shahzadishaq.site into PageSpeed Insights and compare. I would rather you did that than take my word for it.
Measured with Google PageSpeed Insights on the homepage, desktop. Lab data, not field data rather than field data, since this site is too new for Chrome UX Report coverage.
Questions
In rough order of how often I find it: a caching plugin installed but never configured, unused CSS and JavaScript loading on every page, an oversized hero image, render-blocking third-party fonts, and plugin sprawl. Hosting matters but is usually not the main cause. An audit tells you which applies to your site rather than guessing.
No, and chasing 100 is usually a waste of money. Google ranks on Core Web Vitals collected from real Chrome users, not the lab score PageSpeed Insights shows. A site can score 95 in the lab and still fail in the field. Getting LCP, INP and CLS into the green on real visitor data is the goal.
It depends entirely on what is wrong, which is why I audit before quoting. Sites where caching was never configured typically see the largest improvement, because you are switching on work that was already paid for. Sites already well optimized see less. I would rather show you the audit findings than promise a number I cannot support.
Usually not. Hosting becomes the bottleneck once everything else is sorted, and most sites are nowhere near that point. If your server response time is genuinely the limiting factor I will say so and recommend options, but I do not resell hosting so there is nothing in it for me either way.
Yes, and it is a large share of this work. Builders are not inherently slow; stacked addon plugins, per-widget styling and untemplated pages are. Consolidating styles into globals, removing addons that earn nothing, and configuring caching properly usually gets a builder site comfortably into the green.
Some settings can, which is exactly why caching plugins ship conservative defaults. Aggressive JavaScript deferral and unused CSS removal are the two that most often cause visual breakage. I test changes on a staging copy first and check every template before anything reaches your live site.
A typical audit and fix runs three to seven days depending on site size and how much needs testing. The measurable lab improvement is immediate. Field data in Search Console takes around 28 days to reflect the change, because it is a rolling average of real visits.
Largest Contentful Paint is how long until the biggest visible element finishes loading, usually your hero image or headline. It fails most often because the hero image is oversized and not preloaded, or because stylesheets and fonts block rendering before the browser gets to it. Both are fixable without touching your design.
Probably, gradually. New plugins, new images uploaded at full size, a theme update that changes how assets load. That is the honest case for a care plan, but you can also just re-measure quarterly yourself. I will show you where to look so you are not dependent on me for it.
Most of this work is on sites built by someone else, often years ago. I do not need the original developer or documentation. If the build has structural problems that cap how fast it can get, I will tell you that up front rather than taking payment for a ceiling you cannot pass.
Next Step
No form-filling marathon. Send the link and I will run it, tell you the three things costing you the most, and give you an honest view on whether it is worth paying anyone to fix. Reply within 24 hours.
Typical reply time: under 24 hours
WordPress developer & SEO specialist from Bahawalnagar, Pakistan, serving businesses and agencies worldwide.
Available for remote projects
© 2026 Shahzad Ishaq. Built with WordPress in mind, designed to convert.