Developer reacting to a passing score after work to improve Core Web Vitals on WordPress

WordPress Speed Optimization: How I Improved Core Web Vitals for Client Sites

by with No Comment Case Studieswordpresswordpress speed optimization

To improve Core Web Vitals on WordPress, fix the three things that actually break scores on this platform specifically: bloated page builders slowing Largest Contentful Paint, third-party scripts delaying Interaction to Next Paint, and unstyled image placeholders causing layout shift. I’ve fixed all three across multiple client sites, and the pattern repeats almost every time.

A lot of “Core Web Vitals” advice online is generic enough to apply to any website. That’s the problem. WordPress has its own specific failure points — Elementor widgets, WooCommerce scripts, page-builder CSS — and fixing those requires knowing where WordPress actually breaks, not just installing a caching plugin and hoping.

Here’s what I actually check, in the order I check it, based on real client work.

What Are Core Web Vitals, and Why Do They Matter on WordPress?

Core Web Vitals are three metrics Google uses to measure real user experience: Largest Contentful Paint (loading speed), Interaction to Next Paint (responsiveness), and Cumulative Layout Shift (visual stability). According to Google’s own web.dev documentation, a page needs LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1 to count as “good.”

That data doesn’t come from a lab test. It comes from the Chrome UX Report, which Google’s Chrome team describes as real-user data collected from actual Chrome visitors over a rolling period. That distinction matters, because a site can look fast in a quick PageSpeed test and still fail in Search Console if real visitors on slower connections or older phones experience something different.

WordPress makes this harder than a hand-coded site because so much of the front end comes from third parties — themes, plugins, page builders — each adding its own scripts and styles you didn’t write yourself.

Why Does LCP Break So Often on WordPress Sites?

Largest Contentful Paint usually fails for one of two reasons on WordPress: an oversized hero image, or a page builder wrapping that image in layers of unnecessary CSS before it can render.

I start every audit by checking what element counts as the LCP target, using Chrome DevTools rather than guessing. Nine times out of ten, it’s a hero image or heading that’s loading late because it’s buried under render-blocking CSS from the theme or builder.

The fix isn’t just “compress the image,” though that helps. It’s compressing the image, marking it for priority loading, and stripping out the CSS layers a builder adds around it that delay rendering. I’ve covered the image side of this in more depth in my guide to WordPress image optimization — this article focuses on the parts that guide doesn’t cover.

Why Is Interaction to Next Paint the Hardest One to Fix?

INP is the metric most WordPress sites fail, and it’s also the one generic speed guides handle worst. It measures how quickly a page responds after a visitor clicks, taps, or types — not how fast the page loads, but how fast it reacts.

On WordPress, INP problems almost always trace back to JavaScript. Page builders load their own JS bundles. Plugins add more. Analytics and chat widgets add even more. Each one competes for the browser’s main thread, and every millisecond that thread is busy is a millisecond your visitor’s tap goes unanswered.

Here’s what I actually do differently: instead of removing plugins one at a time and re-testing (which takes forever), I use Chrome’s Performance panel to find the specific long tasks blocking the main thread, then trace each one back to its source script. That tells me exactly which plugin or builder feature to defer or replace, instead of guessing and hoping removal helps.

What Causes Layout Shift on WordPress Sites?

Cumulative Layout Shift is usually the easiest fix once you find the cause. On WordPress, it’s almost always one of these: images without defined width and height attributes, web fonts loading late and reflowing text, or ads and embeds injecting content after the page has already rendered.

Setting explicit dimensions on images and using font-display: swap correctly handles most of it. The embeds and ad-injection cases need a reserved space in the layout before the content loads, so the page doesn’t jump when it finally does.

The Diagnostic Order I Actually Use

Most guides tell you to “run PageSpeed Insights and fix the red items.” That’s not wrong, but it’s incomplete, because PageSpeed’s lab data and your real Search Console field data often disagree — and field data is what actually affects rankings.

Here’s my actual order:

  1. Check Search Console’s Core Web Vitals report first, since it reflects real visitors over 28 days, not a single test run
  2. Confirm the exact LCP element in DevTools rather than assuming it’s the hero image
  3. Profile main-thread activity to find INP-blocking scripts, not just plugin count
  4. Fix layout shift last, since it’s usually the fastest win and doesn’t need real-user data to diagnose

That order matters because fixing things in the wrong sequence wastes hours chasing a lab score that doesn’t match what real visitors experience.

A Nuance Most Articles Skip: Mobile and Desktop Score Differently

Google evaluates Core Web Vitals separately for mobile and desktop. A site can pass comfortably on desktop and still fail on mobile, since most real traffic is mobile and mobile devices have less processing power for JavaScript-heavy pages.

I always test both separately before telling a client their site “passes.” A desktop-only pass is a false sense of security when the majority of their visitors are on phones.

[INSERT: a specific client site here — before/after LCP or INP numbers, what plugin or builder element was the actual cause, and how long the fix took]

Common Mistakes That Waste Time and Money

  • Installing every “speed” plugin at once. Stacking caching, minification, and lazy-load plugins together often creates conflicts that cause new problems instead of solving old ones.
  • Chasing a perfect lab score instead of fixing field data. A 100/100 PageSpeed score means little if Search Console still shows real visitors failing INP.
  • Ignoring mobile entirely. Desktop-only testing hides the actual problem most visitors experience.
  • Removing plugins blindly. Without profiling which script actually blocks the main thread, removal is guesswork that might fix nothing.

Should You Fix This Yourself or Hire Someone?

If your site fails one metric slightly, a good caching plugin and image compression might get you there yourself. If you’re failing INP specifically, or failing across multiple pages with different causes, that usually needs someone profiling the actual scripts — not another round of plugin installs.

Before you spend on a full rebuild, it’s worth getting a realistic sense of what a proper speed audit and fix actually costs for your site’s specific problems. My website cost calculator gives you a starting estimate before you commit to anything.

Frequently Asked Questions

What are good Core Web Vitals scores for WordPress?
Google considers a page “good” when Largest Contentful Paint is under 2.5 seconds, Interaction to Next Paint is under 200 milliseconds, and Cumulative Layout Shift is under 0.1, measured across real visitor data at the 75th percentile.

Why does my WordPress site fail Interaction to Next Paint?
INP usually fails because of JavaScript from page builders, plugins, or third-party widgets competing for the browser’s main thread. Profiling long tasks in Chrome DevTools identifies the exact script causing the delay.

Does Elementor hurt Core Web Vitals?
Elementor can slow down Core Web Vitals if a page uses many nested sections and widgets, since each adds its own CSS and JavaScript. A leaner page structure and deferred non-critical scripts significantly reduce this impact.

Do Core Web Vitals affect Google rankings?
Yes, but as a supporting signal rather than the primary factor. Google’s own documentation confirms Core Web Vitals are part of its ranking systems, though content quality and relevance still carry more overall weight.

How long does it take to fix Core Web Vitals on WordPress?
Simple fixes like image optimization and layout shift corrections can take a few hours. Diagnosing and fixing INP issues caused by scattered JavaScript across plugins and builders often takes several days of profiling and testing.

Can I improve Core Web Vitals without a developer?
Basic improvements like a caching plugin, image compression, and font-loading fixes are doable yourself. Diagnosing INP issues from multiple plugin scripts usually requires someone who can profile main-thread activity directly.

Want Your Site’s Real Numbers Checked?

If you’re not sure which metric is actually failing on your site, or why, message me on WhatsApp and I’ll take a real look before you spend money guessing. Start the conversation here.

Developer performing WordPress image optimization by comparing WebP and AVIF file sizes on screen

WordPress Image Optimization: WebP vs AVIF (2026)

by with No Comment Client Resourceswordpresswordpress speed optimization

Quick answer: WordPress image optimization in 2026 comes down to one practical choice: serve AVIF where possible, with WebP as a fallback, since WordPress has supported both natively since version 6.5. AVIF typically produces files 30 to 50% smaller than WebP at the same visual quality. However, the format alone won’t fix a slow site if your images arrive oversized in the first place.

I get asked “should I use WebP or AVIF” constantly, usually by someone who’s already read three conflicting blog posts. Here’s the actual answer, without the fluff.

What Changed: Native AVIF Support in WordPress 6.5

For years, using AVIF on WordPress meant installing a plugin just to upload the file. That changed with WordPress 6.5, released in March 2024, which added native AVIF support directly in core. According to WordPress’s own developer documentation, AVIF images can be up to 50% smaller than JPEGs while maintaining the same image quality, and they also support a wider color range and sharper detail in high-contrast areas.

That matters because it means you no longer need third-party tools just to get AVIF working. If your hosting environment supports it, you can upload and use AVIF files exactly like a JPEG or PNG, right out of the box.

WebP vs AVIF: Which One Actually Wins?

Neither format is universally “better” — they solve slightly different problems, and the right choice depends on your setup.

AVIF wins on raw compression. It produces smaller files at equivalent visual quality, which directly helps your Largest Contentful Paint score, since images are usually the heaviest element on a typical page. The trade-off is slightly slower encoding and marginally less universal support, though browser coverage is now strong across every major browser.

WebP wins on simplicity and encoding speed. It’s been the default recommendation for years, has near-universal browser support, and works reliably across every hosting environment without configuration headaches.

For most small business sites, the practical answer is: use AVIF where your hosting supports it, and fall back to WebP automatically for the small percentage of cases where it doesn’t. You get the best compression available without leaving anyone behind.

Do You Need a Plugin, or Does WordPress Handle This Natively?

WordPress core handles the basics — uploading and displaying both formats. What it doesn’t do automatically is convert your entire existing image library, or intelligently serve AVIF to supporting browsers while falling back to WebP for others.

That’s where a plugin still earns its place. Image optimization plugins handle bulk conversion of your existing media library, automatic compression on upload, and format negotiation based on what each visitor’s browser supports. Native support removed the barrier to entry. It didn’t remove the value of a good optimization workflow.

The Fallback Strategy That Actually Works

The safest approach for any WordPress site is layered fallback: AVIF first, WebP second, JPEG as the final safety net. This is typically handled through the HTML <picture> element or through a plugin that manages content negotiation automatically.

This matters because AVIF support, while broad, still isn’t universal across every browser and email client that might render your images. A proper fallback means no visitor ever sees a broken image, regardless of what they’re using to view your site.

The Mistake I See Constantly

Here’s the part most format comparisons skip entirely: format choice matters far less than image dimensions. I regularly find WordPress sites serving a 4000-pixel-wide AVIF file into a 600-pixel-wide content area. That’s still a bloated file, just in a fancier wrapper.

Resizing images to the actual dimensions they’ll display at matters more than the format debate. A properly sized JPEG will often outperform an oversized AVIF. Get both right, and the gains compound. We covered this same underlying issue from a broader speed angle in our guide on why your website is slow, where image weight consistently shows up as the top offender.

A Quick Setup Checklist

Before you touch a single format setting, resize your images to their actual display dimensions. Then confirm your hosting environment supports AVIF processing, since not every shared host does. Finally, set up automatic WebP fallback so no visitor sees a broken image regardless of browser.

If your current media library is already full of oversized, unoptimized originals, sorting that out properly usually takes more than flipping one plugin setting. Our Core Web Vitals optimization service includes exactly this kind of image audit as part of a full performance pass.

Frequently Asked Questions

Does WordPress support AVIF natively?
Yes. WordPress added native AVIF support in version 6.5, released in March 2024. You can upload and use AVIF files directly, provided your hosting environment supports the format.

Is AVIF better than WebP for WordPress?
AVIF generally produces smaller file sizes at equivalent visual quality, often 30 to 50% smaller than WebP. WebP remains a strong, simpler choice with slightly broader legacy compatibility.

Do I still need a plugin if WordPress supports AVIF and WebP natively?
Often yes, for bulk-converting existing images and automatically serving the right format to each visitor’s browser. Native support handles single uploads well but not full-library optimization.

What’s more important: image format or image size?
Image dimensions matter just as much, if not more, than format choice. An oversized image in a modern format is still a bloated file that slows your page down.

Will switching image formats improve my Google rankings?
Indirectly, yes. Smaller images improve load speed and Core Web Vitals scores, which are factored into page experience and can support better rankings on competitive queries.

Does my hosting provider need to support AVIF specifically?
Yes. Your server’s image processing library needs AVIF support for WordPress to generate and serve AVIF files properly, so it’s worth confirming with your host before relying on it.

If your media library is dragging your site down and you’re not sure where to start, that’s a quick thing to fix properly. Message me on WhatsApp and I’ll take a look at what’s actually slowing your images down.

Mobile user tapping impatiently on a phone as mobile page speed causes a slow-loading site

Mobile Page Speed: Why 53% of Visitors Leave in 3s

by with No Comment Client Resourceswordpress speed optimization

Quick answer: Mobile page speed directly determines whether visitors stay long enough to see your offer. Google’s own research found that 53% of mobile visits are abandoned if a page takes longer than 3 seconds to load. For a small business site, that means over half your paid traffic or search clicks could leave before your content even renders.

That stat gets thrown around a lot, often without context. Let’s actually unpack where it comes from and what it means for a real small business site — not just a scary headline.

Where the 53% Stat Actually Comes From

This number traces back to Google’s own research, and Google still cites it directly in its current AdSense help documentation for publishers trying to improve mobile revenue. It’s not a recycled marketing claim from a random blog.

The original study also found that sites loading within 5 seconds saw meaningfully better engagement than slower ones — including longer sessions and lower bounce rates. The core finding has held up because the underlying human behavior hasn’t changed: people on phones are impatient, and they have alternatives one tap away.

Why Mobile Users Are Less Patient Than Desktop Visitors

Mobile browsing usually happens in shorter bursts, often while someone’s multitasking, standing in line, or searching for something urgent. That context matters more than people realize.

A desktop visitor researching your services at their office chair tolerates a slower load. A mobile visitor searching “plumber near me” while standing in a flooding kitchen does not. That’s why mobile page speed carries more weight for conversion than desktop speed, even though both matter for rankings.

The Revenue Math Behind Three Seconds

Here’s where this stops being an abstract statistic and starts being a business problem. If half your mobile traffic bounces before your page finishes loading, you’re paying for clicks — through ads or SEO effort — that never even see your homepage.

Related research from Akamai found that even a 100-millisecond delay can reduce conversion rates by roughly 7%. Stack a few seconds of slow load time on top of that, and the compounding effect on lead generation gets serious fast.

That’s the part small business owners underestimate. It’s not “my site feels a bit slow.” It’s “I’m losing paying customers before they see my pricing page.”

What’s Actually Realistic for a Small Business Website?

I’ll be honest here, because a lot of speed advice pretends every site can hit a 1-second load time with a few tweaks. That’s not always realistic, especially for content-heavy or image-heavy sites like real estate listings or portfolios.

A more honest goal for most small business sites is getting under 3 seconds on mobile, consistently, across your key pages — not just your homepage. That threshold is where the abandonment data shows the steepest cliff. Getting faster than that helps, but the biggest single win is clearing that 3-second mark in the first place.

Fixing Mobile Speed: What Actually Works

Mobile speed problems usually trace back to the same handful of causes: oversized images not resized for mobile screens, render-blocking scripts, and server response times that don’t account for slower mobile connections.

We covered these causes in more depth in our guide on why your website is slow, including the specific fixes for each one. The short version for mobile specifically: prioritize what loads first, since mobile visitors judge your site by what appears in the first second or two, not the fully loaded page.

The Mistake That Makes Mobile Speed Worse

A common mistake is testing speed only on desktop, then assuming mobile performs similarly. It rarely does. Mobile connections are slower, devices are less powerful, and the same page that loads fine on your office laptop can crawl on a mid-range phone over 4G.

Always test mobile performance separately, using Google’s own mobile testing tools, rather than trusting how fast your site feels on your own desktop connection.

Should You Prioritize Mobile Speed Over Desktop?

For most small businesses today, yes. Mobile traffic makes up the majority of search visits for local and service-based businesses specifically. If your analytics show mobile as your dominant traffic source, mobile speed deserves the first attention, not an afterthought after desktop looks good.

If you’re unsure where your site currently stands, our Core Web Vitals optimization service starts by measuring exactly where mobile visitors are losing patience with your site.

Frequently Asked Questions

Where does the “53% of visitors leave in 3 seconds” statistic come from?
It comes from Google’s own mobile speed research, which the company still references directly in its current AdSense publisher guidance for improving page performance.

Does mobile page speed matter more than desktop speed?
For most businesses relying on mobile search traffic, yes. Mobile visitors are generally less patient and more likely to have alternatives immediately available.

What’s a realistic mobile load time goal for a small business site?
Getting consistently under 3 seconds on mobile across your key pages is a realistic and meaningful goal, since that’s where abandonment increases sharply.

Can a slow mobile site really affect my conversion rate that much?
Yes. Research shows even a 100-millisecond delay can reduce conversions by around 7%, so several seconds of slow load time compounds that effect significantly.

How do I test my website’s actual mobile speed?
Use Google’s mobile-specific testing tools like PageSpeed Insights, which simulate real mobile network conditions rather than relying on desktop performance.

What’s the biggest cause of slow mobile page speed?
Oversized, unoptimized images are typically the biggest cause, since they take longer to download and render on slower mobile connections.

If your mobile visitors are bouncing before they see what you offer, that’s worth fixing before you spend more on ads or SEO. Message me on WhatsApp and I’ll take a real look at where your mobile speed is losing you customers.

Developer discussing green web design and how a faster website affects carbon footprint

Green Web Design: Does a Faster Site Cut Carbon?

by with No Comment Client Resourceswordpress speed optimization

Quick answer: Green web design does reduce a website’s carbon footprint, but the effect is smaller and more indirect than most marketing claims suggest. A faster, lighter site transfers less data, which means less energy used across servers and networks. The bigger wins come from hosting choices and overall data volume, not any single design trick.

I’ll say this upfront, because it matters: a lot of “green hosting” marketing overstates what your individual website actually changes. That doesn’t mean the underlying idea is wrong. It means the honest version of this story is less dramatic than the sales pitch.

How Digital Carbon Emissions Actually Work

Every page load moves data through three layers: the device viewing it, the network carrying it, and the server hosting it. Each layer uses electricity, and electricity, depending on the grid it comes from, produces carbon emissions.

Global data centre electricity consumption reached roughly 415 terawatt-hours in 2024, about 1.5% of total global electricity use, according to the International Energy Agency. That number is growing fast, driven largely by AI workloads rather than ordinary websites. Your small business site is a rounding error in that total — but the underlying mechanics of “lighter page equals less energy” still apply at scale.

Does a Faster Website Really Reduce Carbon Footprint?

Yes, mechanically, it does. A lighter page transfers fewer bytes. Fewer bytes means less server processing, less network transmission, and less energy pulled from the grid per visit.

Here’s the part worth understanding, though: the relationship isn’t 1-to-1 with what most carbon calculators imply. A single visitor’s individual page load produces a tiny, almost immeasurable amount of emissions. The real impact compounds only at scale — thousands or millions of visits across many optimized (or unoptimized) sites.

That’s exactly why the fixes overlap so heavily with ordinary performance work. Reducing page weight, compressing images, and cutting unnecessary scripts don’t just improve load time. For example, they cut the actual data your server and network have to move for every visitor. We covered these same technical fixes from a pure speed angle in our guide on why your website is slow, and the overlap here isn’t a coincidence — lighter pages are both faster and lower-emission by the same mechanism.

Where Green Web Design Claims Get Overstated

Some agencies market “carbon-neutral websites” as if switching hosting alone solves the problem. That’s misleading, because hosting is only one variable, and green hosting certificates don’t always mean what they imply.

Many “green” hosts buy renewable energy certificates (RECs) to offset their grid usage rather than running on 100% renewable power directly. That’s a legitimate practice, but it’s not the same as your site literally running carbon-free. If a provider can’t explain clearly how their green claim works, treat it skeptically.

The honest framing is this: green web design is a genuine, measurable improvement at the margins. It’s not a silver bullet, and no single website redesign will meaningfully move a global emissions number. Don’t let anyone sell you otherwise.

The Business Case Beyond Sustainability

Here’s where I take a stronger stance: even if you don’t care about carbon at all, every fix that makes a site “greener” also makes it faster and cheaper to run. Smaller images mean lower bandwidth costs. Fewer scripts mean better Core Web Vitals scores, which affect both rankings and conversions.

If you’re already working on speed for the metrics that directly move rankings, our guide on how to improve Core Web Vitals covers the technical thresholds Google actually measures. The sustainability angle rides along for free.

Practical Steps for a Genuinely Lighter Website

Start with images, since they’re typically the single heaviest resource on most pages. Compress everything, use modern formats like WebP, and avoid loading full-resolution photos where a smaller version works fine.

Cut unused plugins, scripts, and fonts next. Every unnecessary script your visitors download adds both load time and energy cost, even if the individual impact feels small.

Choose hosting with genuine renewable commitments, and verify the claim rather than taking a badge at face value. A quick look at whether the provider publishes actual energy sourcing data tells you more than a green logo on their homepage.

Is This Something Small Businesses Should Actually Prioritize?

For most small business owners, I’d frame it this way: prioritize speed and performance for the business reasons — conversions, rankings, user experience. Treat the carbon reduction as a genuine, welcome side effect, not the primary reason to invest in it.

If sustainability matters to your brand specifically, say a wellness or eco-conscious business, it’s a legitimate story to tell customers. Just tell it accurately, with real numbers, rather than vague “carbon-neutral” claims that don’t hold up to scrutiny.

Frequently Asked Questions

Does a faster website actually reduce carbon emissions?
Yes, mechanically. A faster, lighter website transfers less data, which reduces the energy used by servers and networks per visit, though the individual impact per visitor is very small.

Is green hosting the same as carbon-neutral hosting?
Not always. Many “green” hosts buy renewable energy certificates to offset grid usage rather than running entirely on renewable power, which is a meaningful but different claim.

How much CO2 does an average website produce per visit?
Estimates vary by source and methodology, generally ranging from under half a gram to a few grams of CO2 per page view, depending largely on page weight and hosting energy source.

What’s the single biggest factor in a website’s carbon footprint?
Page weight, primarily driven by unoptimized images, is typically the largest factor, since heavier pages require more data transfer and processing per visit.

Should small businesses prioritize green web design over speed optimization?
Not separately. The two overlap almost entirely, since the fixes that reduce page weight for speed also reduce the data footprint driving emissions.

Are carbon-neutral website claims trustworthy?
Some are, but verify the specifics. A credible claim should explain exactly how emissions are measured and offset, not just display a badge without supporting detail.

If you want a website that’s genuinely lighter, faster, and easier on both your visitors and your hosting bill, that’s exactly the kind of build I focus on. Message me on WhatsApp and we can talk through what a leaner, better-performing site would look like for your business.

Small business owner waiting for a slow website to load and checking possible causes

Why Is My Website Slow? Causes & Real Fixes (2026)

by with No Comment Client Resourceswordpress speed optimization

Quick answer: Your website is slow, most likely, because of unoptimized images, bloated plugins or themes, weak hosting, or too many third-party scripts running at once. These four causes explain the vast majority of slow small business sites I’ve audited. The fix usually isn’t one big change — it’s finding which of these is doing the most damage on your specific site.

Everyone assumes their slow site has one dramatic cause. In practice, it’s almost always a stack of smaller problems, each adding a second here and half a second there.

The Most Common Reasons a Website Is Slow

1. Images That Are Too Large

This is the single biggest culprit, and it’s not close. Images typically account for roughly 40 to 50% of total page weight, according to HTTP Archive’s Web Almanac, and often more on image-heavy sites like online stores or portfolios.

A single 4-megabyte hero photo, straight out of a phone camera, can undo every other optimization on your site. Compressing images and using modern formats like WebP usually delivers the fastest visible improvement of any single fix.

2. Cheap or Shared Hosting

Hosting is invisible until it isn’t. Shared hosting plans put your site on a server with hundreds of other sites, all competing for the same limited resources.

That’s fine during quiet traffic. It falls apart the moment your site gets a traffic spike, or the server it shares gets hit by someone else’s bad plugin. Upgrading hosting is rarely the fun answer, but it’s often the most effective one for sites that stay slow no matter what else gets fixed.

3. Plugin and Theme Bloat (WordPress Specifically)

WordPress makes it dangerously easy to install plugins. Every plugin adds code that has to load, even on pages that don’t use its features.

I regularly find WordPress sites running 25-plus plugins, half of which are inactive holdovers from a redesign nobody cleaned up. Each one adds weight. Removing unused plugins, and replacing heavy page builders with lighter alternatives, often speeds up a site more than any single “speed plugin” can.

4. Custom Fonts and Font Loading Issues

Custom fonts look great and load slower than you’d expect, especially when a site loads four or five font weights it never actually uses. Limiting font variations, and using WOFF2 format, cuts this weight down significantly.

5. Too Many Third-Party Scripts

Chat widgets, analytics tools, ad pixels, review plugins — each one adds a script your browser has to download and run before the page finishes loading. Most sites accumulate these over time without anyone auditing what’s still necessary.

The average site now ships nearly 500KB of JavaScript, and that number keeps climbing year over year. Cutting scripts you no longer use is one of the easiest wins available, because it requires no design changes at all.

6. No Caching or CDN

Without caching, your server rebuilds every page from scratch for every visitor. Without a content delivery network, visitors far from your hosting server experience real latency, since data has to travel farther to reach them.

Both fixes are relatively cheap and often make a bigger difference than people expect, especially for visitors outside your hosting provider’s home region.

How to Actually Test Your Site’s Speed

Before fixing anything, test what’s really happening. Google’s PageSpeed Insights and Search Console both give free, real data on where your specific site is losing time.

If you want the deeper technical breakdown of what “good” actually means for these scores, our guide on how to improve Core Web Vitals covers the exact thresholds Google measures against.

The Mistake That Undoes Every Other Fix

Here’s where I’ll be blunt: installing a “speed optimization” plugin without fixing the actual cause is the most common mistake I see. It caches a bloated page instead of fixing the bloat.

That approach papers over the problem temporarily. The moment cache clears, or a new visitor hits an uncached page, the underlying slowness is right back. Fixing root causes — image size, unused plugins, hosting capacity — outlasts any caching band-aid.

A Quick Self-Check Before You Call Anyone

Run your homepage through PageSpeed Insights and note your image and JavaScript weight in the report. If either looks unusually heavy compared to the rest of your page, you’ve likely found your biggest lever.

Check your plugin list next. If you don’t recognize what a plugin does or haven’t touched its settings in over a year, it’s worth investigating whether you still need it.

When It’s Time to Bring in Help

Some fixes, like compressing a handful of images, are genuinely DIY-friendly. Others — hosting migrations, script auditing, or diagnosing why a specific template underperforms — benefit from someone who’s done it repeatedly and knows what to check first.

If your site’s speed problem has resisted a few obvious fixes already, our Core Web Vitals optimization service starts by identifying exactly which of these causes is actually responsible, instead of guessing.

Frequently Asked Questions

Why is my website slow even though I have good internet?
Your own connection speed doesn’t affect how fast your website loads for visitors. Slowness usually comes from server-side issues like heavy images, weak hosting, or excess scripts, not your personal internet.

What’s the single biggest cause of a slow website?
Unoptimized images are typically the biggest cause, often accounting for 40 to 50% of total page weight on a given page.

Does having too many plugins slow down a WordPress site?
Yes. Every active plugin adds code that loads on your pages, even if a visitor never uses that feature. Removing unused plugins is one of the most effective speed fixes available.

Will a caching plugin fix a slow website?
Caching helps, but it doesn’t fix the underlying cause. If your images or scripts are the real problem, caching only masks the slowness temporarily.

How do I check why my specific website is slow?
Use Google PageSpeed Insights or Search Console. Both show a breakdown of what’s loading slowly on your actual site, rather than generic advice.

Should I upgrade my hosting to fix a slow website?
If your site stays slow despite fixing images, plugins, and scripts, hosting is often the remaining bottleneck, especially on cheap shared hosting plans.

If you’ve tried the obvious fixes and your site is still dragging, it’s worth having someone actually diagnose it instead of guessing. Message me on WhatsApp and I’ll tell you what’s really slowing you down.

Developer working to improve Core Web Vitals scores shown on a laptop performance dashboard

How to Improve Core Web Vitals in 2026

by with No Comment Client Resourceswordpress speed optimization

Quick answer: To improve Core Web Vitals in 2026, you need to hit three thresholds at the 75th percentile of real visitors: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. Most sites fail because of unoptimized images, heavy scripts, or unstable layouts — not because of some hidden technical mystery.

I run these audits regularly, and the pattern repeats across almost every small business site I look at. The fixes aren’t exotic. They’re just skipped.

What Are Core Web Vitals, Exactly?

Core Web Vitals are three metrics Google uses to measure real user experience on your site. They cover loading speed, responsiveness, and visual stability — the three things that quietly decide whether a visitor sticks around.

Largest Contentful Paint (LCP) measures how fast your main content appears. Interaction to Next Paint (INP) measures how quickly your page responds when someone taps or clicks. Cumulative Layout Shift (CLS) measures whether your layout jumps around while loading.

Here’s the detail most articles gloss over: Google doesn’t grade your best-case load time. It grades the 75th percentile of your actual visitors over a rolling window, using real Chrome data rather than a single test run. That means a fast site on your own laptop can still fail if enough real users, especially on mobile, have a slower experience.

The 2026 Thresholds You Actually Need to Hit

To count as “good,” your site needs LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1 — all three, not just one or two.

Anything above 4 seconds LCP, 500 milliseconds INP, or 0.25 CLS lands in the “poor” range, which is where rankings and conversions both take a hit. The middle band, “needs improvement,” is where most small business sites actually sit — technically passable, but leaving performance on the table.

One thing worth knowing if you’ve researched this before: INP replaced an older metric called First Input Delay in 2024. If you’re reading advice that still mentions FID, it’s outdated. INP is stricter, because it measures every interaction on the page, not just the first click.

Why This Actually Matters for Your Business, Not Just Rankings

Core Web Vitals get filed under “SEO stuff,” but that undersells them. They’re a direct measure of whether your site keeps or loses a visitor in the first few seconds.

A slow, jumpy page doesn’t just rank worse. It converts worse, because visitors bounce before they see your offer, your pricing, or your contact form. That’s the real cost — lost leads, not just lost search position. We covered this same pattern from a different angle in our piece on cheap website hidden costs, where slow load times quietly bleed conversions long after launch.

The Three Mistakes That Wreck Each Metric

LCP problems usually come from unoptimized hero images, slow server response times, or render-blocking scripts loading before the main content. Compressing images and using proper image formats fixes most of this.

INP problems show up when a page has too much JavaScript running on the main thread. Every click waits in line behind code the browser is still processing. Reducing unnecessary scripts, especially third-party trackers and widgets, usually helps the most.

CLS problems happen when images, ads, or embedded content load without reserved space, pushing everything else down the page. Setting explicit width and height on media elements is the simplest fix, and it’s the one people skip most often.

None of these are exotic problems. They’re common, repeatable, and fixable — which is exactly why I get frustrated seeing sites launch without anyone checking for them.

DIY Tools vs. a Real Audit

Google’s own PageSpeed Insights and Search Console give you a genuinely useful starting point, and they’re free. They’ll tell you which pages fail and roughly why.

Where DIY tools fall short is prioritization. A report might flag ten issues, but only two or three are actually moving your p75 score. Chasing every warning wastes time on fixes that don’t change your real-world rating, according to Google’s own measurement documentation on how field data is calculated. That’s usually where a professional audit earns its cost — identifying which fixes matter and which are noise. If you’d rather skip the guesswork, our Core Web Vitals optimization service starts with exactly that kind of prioritized diagnosis.

How Long Does It Take to See Results?

Once fixes are live, Google needs a rolling 28-day window of real user data before your score fully updates. That’s not a bug — it’s how field data works, since a single fast test doesn’t represent every visitor’s experience.

That said, you’ll often see PageSpeed Insights lab scores improve immediately after a fix, even before the field data catches up. Don’t panic if your Search Console report still shows red for a few weeks after launch.

Frequently Asked Questions

What are good Core Web Vitals scores in 2026?
Good scores are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1, measured at the 75th percentile of real visitors.

Do Core Web Vitals actually affect Google rankings?
Yes, though as one signal among many. They matter more directly for conversions, since slow or unstable pages cause visitors to leave before taking action.

What’s the fastest way to improve Core Web Vitals?
Start with image compression for LCP, reducing third-party scripts for INP, and setting fixed dimensions on media for CLS. These three fixes address the most common failures.

How long does it take for Core Web Vitals scores to update after a fix?
Google uses a rolling 28-day window of real user data, so field data typically takes a few weeks to fully reflect a fix, even though lab tools may show improvement sooner.

Is FID still part of Core Web Vitals?
No. Interaction to Next Paint (INP) replaced First Input Delay (FID) in March 2024. Any current guidance should reference INP, not FID.

Can I check my Core Web Vitals for free?
Yes. Google PageSpeed Insights and Search Console both report Core Web Vitals data at no cost, though they don’t prioritize which fixes matter most for your specific site.

If your site’s already showing yellow or red in Search Console, that’s worth a proper look before it costs you more leads. Message me on WhatsApp and I’ll tell you honestly what’s actually worth fixing first.

Small business owner budgeting website maintenance cost while working on a laptop

Website Maintenance Cost: What to Budget For in 2026

by with No Comment Client Resourceswebsite Cost Calculatorwordpresswordpress speed optimization

Quick answer: Website maintenance cost for a small business typically runs $95 to $195 a month in 2026 for full-service care — updates, security, backups, and basic support. Bare-bones automated plans start around $20 to $50 a month, while agency-level or e-commerce maintenance can climb past $500. The right number depends on your platform and how much risk you’re willing to carry yourself.

Launching a website feels like the finish line. It isn’t. That’s the part most first-time site owners get wrong, and it’s an expensive assumption to carry for a year.

What Does “Website Maintenance” Actually Include?

Maintenance isn’t one task. It’s a stack of smaller ones that quietly protect your investment.

At minimum, it covers software and plugin updates, security monitoring, regular backups, and uptime checks. A more complete plan adds speed optimization, broken-link checks, content edits, and priority support when something breaks.

Here’s the part that surprises people: a $29-a-month plan and a $195-a-month plan are rarely the same service with a different price tag. The cheap one usually covers automated updates and backups only. Everything else — real security response, human support, performance work — gets left out.

Realistic Website Maintenance Cost by Platform

Your platform changes the math more than most guides admit.

WordPress sites generally cost more to maintain because the plugin ecosystem needs constant attention. Expect $50 to $200 a month for a small business site handled by a freelancer, or higher with an agency managing security and performance actively.

Wix and other hosted builders bundle some maintenance into the platform subscription itself, since hosting, backups, and core security are handled centrally. That said, content updates, SEO adjustments, and custom features still require paid support.

E-commerce sites, on either platform, cost more to maintain because there’s more at stake. Payment processing, inventory syncing, and higher security requirements push monthly costs toward $300 to $500 or beyond.

For most small business websites without e-commerce, $95 to $195 a month is a realistic, sustainable number. That’s enough to cover real security response and a few hours of support monthly, without paying for enterprise-level coverage you don’t need.

If you haven’t built your site yet and are still weighing what the initial build should cost, our guide on small business website cost covers that groundwork first.

What Happens If You Skip Maintenance?

This is where I’ll be direct: skipping maintenance doesn’t save money. It defers a cost, usually with interest.

Outdated plugins and themes are the most common way small business sites get compromised. Legitimate, otherwise healthy websites get infected without the owner even knowing until traffic drops or a customer reports a warning. Google’s own Safe Browsing data confirms this pattern directly — sites are often infected without the knowledge of the website owner, which is exactly why silent, ongoing monitoring matters more than a one-time cleanup.

Once a site is flagged as unsafe, recovery isn’t quick. You’re paying for malware removal, security hardening, and — if rankings dropped — the SEO work to recover visibility that took months to build in the first place. That bill is almost always higher than a year of maintenance would have cost.

We covered a related version of this problem in our piece on cheap website hidden costs — maintenance neglect is one of the clearest examples of a cost that hides until it’s expensive.

DIY Maintenance vs. Hiring It Out

Some business owners handle updates themselves, and for a very simple site, that can work. It requires time, though, and a comfort level with backend systems most owners don’t have or want.

The real cost of DIY isn’t zero. It’s your time, plus the risk of missing something critical during a busy month. A missed update right before a known vulnerability gets exploited is exactly how small business sites get hacked.

Hiring it out removes that risk and that time cost. For most business owners, paying $95 to $195 a month for someone else to own this responsibility is a reasonable trade, not an unnecessary expense.

What a Reasonable Maintenance Plan Should Include

Before signing anything, check for four things: how often updates happen, whether backups are stored off-site, what the response time looks like for urgent issues, and whether basic content edits are included or billed separately.

Vague answers to any of these usually mean gaps you’ll discover later, at the worst possible time.

Frequently Asked Questions

How much does website maintenance cost per month for a small business?
Most small businesses pay $95 to $195 a month for full-service maintenance covering updates, security, backups, and basic support. Bare-bones automated plans run $20 to $50 a month but offer far less protection.

What’s included in a typical website maintenance plan?
A standard plan includes software and plugin updates, security monitoring, regular backups, uptime checks, and some level of support for fixes or small content edits.

Is website maintenance really necessary, or can I skip it?
Skipping maintenance increases the risk of security breaches, broken functionality, and slow performance. Fixing a compromised or broken site later almost always costs more than ongoing maintenance would have.

Does WordPress cost more to maintain than Wix?
Generally, yes. WordPress requires more active plugin and security management, while hosted platforms like Wix handle some core maintenance within the subscription itself.

Can I do website maintenance myself instead of paying for it?
Yes, for a simple site, if you’re comfortable with backend systems and can commit consistent time. The trade-off is your own time and the risk of missing a critical update.

How much does it cost if a website gets hacked from lack of maintenance?
Costs vary, but malware removal, security hardening, and SEO recovery after a hack typically exceed a full year of standard maintenance, especially if rankings were affected.

If you’d rather not track updates, backups, and security yourself, that’s exactly the kind of ongoing work I handle for clients. Message me on WhatsApp and we can figure out a maintenance plan that actually fits your site.