Restaurant owner reviewing restaurant website mistakes on a tablet with a developer during online ordering setup

Restaurant Website Mistakes That Cost You Orders

by with No Comment Client Resources

Quick answer: The restaurant website mistakes that cost you online orders most often come down to slow mobile load times, a menu that’s a PDF instead of real text, and checkout flows that force too many steps. Fix those three, and most restaurants see direct orders climb because customers stop bouncing to a delivery app instead.

I’ve rebuilt online ordering for restaurants in Denmark, moving them off clunky third-party checkout screens onto their own WordPress and WooCommerce sites. The pattern repeats almost every time. It’s rarely the food or the brand that loses the order. It’s the five seconds between a hungry customer tapping “order” and giving up.

Why Does This Even Matter When Delivery Apps Exist?

Because direct orders are worth more, and customers actually prefer them when the experience works. According to a 2024 Paytronix industry report, guests order 35% more items per check when ordering directly from a restaurant compared to third-party marketplaces, and mobile app orders carry 45% higher lifetime value than web orders.

Customers aren’t loyal to Uber Eats or DoorDash out of preference, either. A HungerRush consumer survey found that 67% of people are at least sometimes deterred from third-party apps because of the added fees, and more than half said they’d order directly instead, depending on the website experience.

That “depending on” is doing a lot of work. If your restaurant website mistakes push customers away, they default right back to the app you’re trying to avoid.

Mistake One: A Menu Trapped Inside a PDF

This is still shockingly common. A restaurant uploads their printed menu as a PDF, links it from the homepage, and calls the website done. On mobile, that means pinching, zooming, and scrolling sideways just to read a burger description.

Search engines can’t read PDF menus well either, so you lose local search visibility for dish names people actually search. A menu built as real, structured HTML text loads instantly, displays cleanly on any phone, and gets indexed by Google for searches like “best butter chicken near me.”

Mistake Two: Slow Mobile Load Times

Most restaurant browsing happens on a phone, often while someone is standing outside deciding where to eat. Google’s own research found that 53% of mobile visitors abandon a page that takes longer than three seconds to load. For a hungry customer with three other tabs open, three seconds might be generous.

Heavy, uncompressed food photography is usually the culprit. High-resolution hero images look great on a designer’s laptop but crawl on a spotty 4G connection. Every restaurant site should run through a speed check before launch, not after complaints start.

I offer a dedicated Core Web Vitals optimization service for exactly this reason — restaurant sites are some of the worst offenders because everyone wants beautiful food photos, but nobody wants to compress them properly.

Mistake Three: Checkout That Asks for Too Much

Every extra field between “select item” and “confirm order” is a chance for someone to give up. Account creation before ordering, mandatory phone verification, or a five-step address form all add friction a delivery app simply doesn’t have.

For a WooCommerce-based ordering system, that usually means enabling guest checkout, auto-filling saved addresses for returning customers, and keeping the entire flow to three screens or fewer: menu, cart, payment. I built exactly this kind of streamlined checkout for Express Pizzeria in Denmark, migrating them off a clunky third-party system onto a direct WooCommerce setup.

Mistake Four: No Real-Time Order Status

Customers who order through Uber Eats get a live map and a countdown timer. Customers who order through a restaurant’s own site often get… nothing, just a confirmation email and silence. That gap makes a direct order feel riskier, even when the food arrives just as fast.

You don’t need a full delivery-tracking app to fix this. A simple order status page — received, preparing, ready for pickup, out for delivery — closes most of the trust gap without custom engineering.

Mistake Five: Hiding the Order Button

Some restaurant homepages bury the “Order Online” button under a hero video, a reservations widget, and three carousel slides before it appears. On mobile, that means scrolling past everything else just to start an order. If ordering is your main revenue driver, that button belongs above the fold, on every page, not just the homepage.

What This Actually Costs a Restaurant

Run the math on your own numbers. If your average ticket is $28 and your site loses even 15 orders a week to abandonment, that’s over $21,000 a year walking straight to a delivery app instead of your kitchen. Multiply that by however many of these mistakes are stacking on top of each other, and the number gets uncomfortable fast.

That’s the real argument for fixing this now rather than “eventually.” Every week a slow, cluttered ordering page stays live is a week of direct revenue quietly leaking to a platform that takes 15-30% off the top.

Frequently Asked Questions

What’s the single biggest restaurant website mistake that costs orders? Slow mobile load time tends to cause the most damage, since more than half of mobile visitors leave a page that takes longer than three seconds to load.

Should restaurants avoid third-party delivery apps entirely? No, third-party apps still reach new customers effectively. The goal is building a direct ordering site strong enough that repeat customers order there instead, since direct orders are worth more per ticket.

Does a PDF menu really hurt SEO? Yes, because search engines can’t easily read or index dish names inside a PDF, which means your restaurant misses local search traffic for specific menu items.

How fast should a restaurant website load on mobile? Aim for under three seconds. Beyond that point, abandonment rates climb sharply according to Google’s own mobile performance research.

Do customers actually prefer ordering directly from a restaurant? Many do, when the experience is smooth. Surveys show a majority of consumers are open to ordering directly instead of through an app, largely to avoid added fees.

Is guest checkout important for restaurant ordering sites? Yes. Forcing account creation before a first order is one of the fastest ways to lose a hungry, impatient customer at checkout.

If your restaurant’s website is quietly pushing orders toward apps instead of keeping them for you, that’s usually fixable in a focused rebuild, not a total overhaul. Message me on WhatsApp and I’ll take a look at what’s actually costing you orders.

Business owner setting up multi-currency support WooCommerce dashboard on a laptop

How to Add Multi-Currency Support to WooCommerce

by with No Comment Client Resources

Quick answer: Adding multi-currency support to WooCommerce means letting shoppers see and sometimes pay in their own currency instead of just yours. The easiest route in 2026 is WooPayments’ built-in switcher, which supports 135 currencies for free. For more control over rounding, rates, or checkout currency, a dedicated plugin like Aelia or FOX Currency Switcher does more.

I get this request constantly from clients selling to the US, UK, and EU at once. A Danish restaurant client only needed one currency. A store selling digital products worldwide needed six. The setup looks similar either way, but the decision behind it isn’t.

Why Bother With Multi-Currency at All?

Showing a price in dollars to a shopper in Germany creates friction, even if the conversion math is simple. They have to stop, calculate, and trust that your number is accurate. That tiny pause is often enough to lose the sale.

Research from currency-conversion providers consistently links local pricing display to higher trust and better conversion, because shoppers no longer need to guess. It’s not a huge technical lift either — WooCommerce made this easier in 2024 when it expanded WooPayments across Spain, Italy, France, and Germany and added native multi-currency support covering 135 currencies, according to TechRadar’s coverage of the rollout.

That’s the real starting point for most stores now: check what’s already built in before installing anything new.

Option One: WooPayments’ Native Currency Switcher

If you already use WooPayments as your payment gateway, you likely have multi-currency support sitting unused in your dashboard. It lets shoppers browse and check out in whichever currency they select, while you continue receiving settlement in your base currency.

Here’s what it includes:

  • Prices convert automatically using rates pulled from a live exchange rate API
  • A currency switcher widget you can place in your header, footer, or sidebar
  • Rounding controls, so converted prices don’t end up looking like $19.73 instead of $19.99
  • A fallback currency, so shoppers whose currency isn’t enabled still see something sensible, usually your default

Setup takes maybe fifteen minutes. Go to WooCommerce → Settings → Payments → WooPayments, enable multi-currency, then choose which currencies to activate. That’s genuinely most of it. For a straightforward store without complex pricing rules, this is usually all you need.

Option Two: A Dedicated Multi-Currency Plugin

WooPayments’ switcher has one real limitation — it works best when WooPayments is also your payment processor. If you’re using Stripe, PayPal, or a regional gateway instead, a standalone plugin often integrates more cleanly.

Plugins like Aelia Currency Switcher or FOX – Currency Switcher Professional add more granular control: per-product manual pricing overrides, multiple exchange rate sources, and geolocation-based currency switching that activates before a visitor even clicks anything. That extra control costs more setup time and, usually, a yearly license fee.

Choose this route if any of the following apply to your store:

  1. You use a payment gateway other than WooPayments
  2. You need to set exact manual prices per currency instead of pure conversion
  3. You sell high-value items where rounding errors on live rates actually matter
  4. You want automatic currency detection based on visitor location

The Setup Mistake That Costs Sales

Here’s something most guides skip. Adding currencies to the switcher isn’t the same as making sure your customer can actually pay in that currency. If your payment gateway only settles in USD, a customer who selects EUR still sees EUR prices, but their bank statement may show a converted USD charge with a foreign transaction fee attached. That mismatch generates support tickets and, sometimes, chargebacks.

Before you launch multi-currency, confirm your payment gateway processes native settlement in the currencies you’re offering, not just currency display. WooPayments and Stripe both support multi-currency settlement in many regions, but always check per-country before assuming.

If your store is already live and conversions still feel low after adding multi-currency, the currency switcher probably isn’t the actual problem. I’ve broken down the more common causes in why a WooCommerce store isn’t converting.

Does Multi-Currency Affect SEO or Page Speed?

Not meaningfully, if it’s set up correctly. Currency conversion happens client-side or via a lightweight geolocation check, so it shouldn’t slow down page load in any way a visitor notices. The bigger risk is duplicate content from currency-specific URLs, which some plugins generate. Stick to a single URL with a JavaScript-based switcher unless you specifically need separate country pages for other reasons.

How Exchange Rates Stay Accurate

Most multi-currency tools pull rates from a live API and refresh them on a schedule — commonly every twelve hours on free plans, faster on paid tiers. That’s frequent enough for nearly every small business, since exchange rates rarely swing enough in half a day to matter at typical order values. If you sell high-ticket items where a currency shift changes your margin meaningfully, look for a plugin with more frequent rate refreshes or manual override pricing.

Frequently Asked Questions

Is WooCommerce multi-currency free? Yes, if you use WooPayments as your gateway, the native currency switcher is included at no extra cost and supports 135 currencies.

Do I need a plugin if I already use WooPayments? Not necessarily. WooPayments includes its own currency switcher, so a separate plugin only makes sense if you need features it doesn’t offer, like manual per-currency pricing.

Will multi-currency slow down my WooCommerce store? No, in most setups conversion happens quickly through an API call or stored rate, and it shouldn’t add noticeable load time to your pages.

Can customers pay in a currency different from my store’s base currency? Yes, as long as your payment gateway supports settlement in that currency. Check your gateway’s supported currencies before enabling the option in WooCommerce.

How often do exchange rates update in WooCommerce multi-currency plugins? It depends on the plugin, but many refresh every 12 hours on free tiers and more frequently on paid plans.

Does adding multiple currencies hurt my store’s SEO? It can, only if the plugin generates separate URLs per currency without proper canonical tags. A JavaScript-based switcher on a single URL avoids that risk entirely.

Getting multi-currency working cleanly, without breaking your checkout or your SEO, usually takes an experienced hand the first time through. If you’d rather have someone set it up correctly than troubleshoot it later, reach out on WhatsApp and I’ll take a look at your store.

Small business owner and developer comparing payment gateways for small business checkout options on a laptop

Best Payment Gateways for Small Business in Europe

by with No Comment Client Resources

Quick answer: The best payment gateways for small business in Europe are Mollie, Stripe, and Adyen, each with no monthly fee and per-transaction pricing between roughly 1.1% and 1.9%. The real decision isn’t the processor’s brand name. It’s whether the gateway supports local methods like iDEAL, Bancontact, and SEPA Direct Debit, since those often convert better than cards alone.

I’ve built checkout flows for clients across Denmark, the Netherlands, and the wider EU, and the question I hear most is “just tell me which one to use.” Fair enough. But the honest answer depends on where your customers actually bank, not on which gateway has the flashiest homepage.

Why “Which Gateway Is Cheapest” Is the Wrong First Question

Every small business owner starts by comparing percentages. That instinct makes sense — nobody wants to lose margin on every sale. However, a 0.3% fee difference rarely moves the needle as much as a missing payment method does.

Here’s why. If a Dutch customer reaches your checkout and doesn’t see iDEAL, many will simply leave. Recent industry research from payments platform payabl. found that regional preference varies sharply: debit cards dominate in the UK, PayPal leads in Germany at 71%, and iDEAL takes the top spot in the Netherlands. A gateway that only processes cards well is quietly turning away buyers in exactly the markets you’re trying to reach.

That’s the real starting question: does this payment gateway support the methods your specific customers already trust?

The Three Gateways Worth Comparing in 2026

For most European small businesses, the shortlist comes down to Mollie, Stripe, and Adyen. All three plug into WordPress, WooCommerce, and custom-built sites without needing a merchant account elsewhere.

Mollie was built for European small businesses first. There’s no monthly fee and no contract — you pay per transaction, with rates like roughly €0.32 for iDEAL and €0.35 for SEPA payments. It’s simple to set up, and its dashboard is genuinely easy for a non-technical owner to read.

Stripe charges 1.5% + €0.25 for standard EU cards and 1.9% + €0.25 for premium EU cards, with international cards costing more. It has the deepest developer toolkit of the three, which matters if you eventually want custom checkout logic, subscriptions, or marketplace features.

Adyen charges a flat €0.11 processing fee per transaction plus a separate cost per payment method, with no setup or monthly fees. It’s popular with mid-sized and scaling businesses because pricing stays predictable as volume grows, though the interface leans more technical than Mollie’s.

None of these three is objectively “best.” A bakery in Rotterdam taking mostly iDEAL payments has different needs than a SaaS founder in Berlin billing subscriptions monthly.

What Local Payment Methods Actually Change

This is the part generic gateway comparisons skip. In the Netherlands, iDEAL still holds more than 60% of online payment share, according to Stripe’s own payment method data. In Belgium, over 80% of online businesses offer Bancontact because customers expect it by default.

If you’re building or rebuilding a WooCommerce store for a European audience, don’t just install the gateway with the lowest fee. Check which local rails it supports out of the box. I’ve seen stores lose meaningful checkout completion simply because the payment plugin only offered Visa and Mastercard to a Dutch audience that wanted their bank app instead.

If your store already gets decent traffic but conversions feel low, that’s often a checkout problem before it’s a traffic problem — I’ve written more about diagnosing that in why a WooCommerce store stops converting.

How the New Instant Payments Rules Affect You

Something changed in the background of European payments recently, and most small business owners haven’t noticed yet. Under EU Regulation 2024/886, banks and payment institutions across the Eurozone are now required to send and receive SEPA instant payments within ten seconds, at any hour, any day of the year. According to KPMG’s coverage of the regulation, receiving deadlines took effect in January 2025 and sending deadlines followed in October 2025.

For your business, this means bank transfer payments — long considered the slow option — are becoming nearly as fast as card payments in practice. That’s good news if you invoice clients or take SEPA Direct Debit payments, because cash reaches your account faster than it used to. Gateways like Mollie and Stripe are already routing eligible transfers through instant rails, so you may not need to do anything except make sure your provider supports it.

A Mistake I See Often

Business owners frequently pick a gateway based on what a competitor uses, without checking if their own audience matches. A UK-only service business copying a Dutch e-commerce store’s payment stack ends up offering iDEAL to customers who’ve never heard of it, while missing the debit card options their actual buyers expect. Match the gateway to your audience’s country, not to someone else’s setup.

Which Gateway Fits Which Business?

  • Selling mostly to Dutch or Belgian customers? Mollie’s local method coverage and simple per-transaction pricing usually win.
  • Running subscriptions, marketplaces, or need custom logic? Stripe’s developer tools make that far easier to build.
  • Scaling fast across multiple EU countries with growing volume? Adyen’s flat processing fee structure tends to stay predictable as you grow.
  • Not sure what your site even needs yet? Start with our website cost calculator to scope the build before locking in a payment stack.

Whichever gateway you choose, test the actual checkout flow yourself on a phone. A gateway that looks great in documentation can still feel clunky at the point where someone’s about to pay you.

Frequently Asked Questions

Which payment gateway is cheapest for a small business in Europe? Mollie and Adyen tend to have lower baseline transaction costs than Stripe for standard EU cards, though exact savings depend on your payment method mix and country.

Do I need to support iDEAL if I don’t sell in the Netherlands? No. Only add local methods relevant to where your actual customers are based — adding irrelevant options clutters checkout without adding sales.

Can I use more than one payment gateway on the same website? Yes, and some WooCommerce and Wix setups do run two gateways side by side, though it adds complexity to reconciliation and reporting.

Will the EU Instant Payments Regulation affect card payments too? No, it applies to SEPA credit transfers and bank-based payments, not card transactions, which already settle on their own network timelines.

Is PayPal worth adding alongside a main gateway? Often yes. Research shows PayPal remains the most recognized payment brand across much of Europe, and offering it as a secondary option can reduce cart abandonment.

How long does it take to switch payment gateways on an existing site? For a straightforward WooCommerce or Wix Velo setup, a gateway migration usually takes a few days, though anything with saved subscriptions needs more careful planning.

Picking the right payment gateway is a decision you’ll live with for years, and getting the checkout wrong quietly costs more than the fee percentage ever does. If you want a second opinion on which gateway fits your specific market and platform, message me on WhatsApp and I’ll walk through it with you.

Small business owner comparing WooCommerce vs Shopify UK pricing on a laptop screen

WooCommerce vs Shopify UK: 2026 Small Business Guide

by with No Comment Client Resources

Quick answer: For UK small businesses, WooCommerce vs Shopify usually comes down to time versus money. WooCommerce costs less over three years but needs someone to manage hosting and updates. Shopify costs more monthly but handles hosting, security, and support for you. Choose Shopify if you want speed; choose WooCommerce if you want control.

I get asked this question almost every week. A client walks in with a spreadsheet of Shopify app costs, or a WooCommerce site that broke after a plugin update, and wants to know which platform they should have picked. There’s no universal winner. But there is a right answer for your specific business, and I want to walk you through how to find it.

What’s the real difference between WooCommerce and Shopify?

WooCommerce is a free plugin that turns a WordPress site into an online shop. You own the hosting, you control the code, and you’re responsible for keeping everything updated. Shopify is a complete hosted service. You pay a monthly fee, and Shopify handles servers, security patches, and uptime.

Think of it like renting versus owning. Shopify is a serviced office — you pay more each month, but someone else fixes the plumbing. WooCommerce is owning the building — cheaper long-term, but you’re the one calling the electrician.

How much does each platform actually cost in 2026?

This is where most comparisons get vague. Let’s use real numbers.

Shopify’s Basic plan runs about £25 per month on annual billing, with online transaction fees around 2.9% plus 30p per sale unless you use Shopify Payments exclusively. Higher tiers reduce that percentage but raise the monthly fee.

WooCommerce itself is free. But you’ll pay for managed WordPress hosting, typically £10–£50 per month depending on traffic, plus occasional premium plugins for things like advanced shipping or subscriptions.

For a UK store doing roughly £60,000 a year in revenue, industry cost breakdowns commonly put WooCommerce’s all-in yearly cost between £150 and £400, against Shopify’s £900 to £1,800 once apps and transaction fees are included. That gap narrows fast, though, once your time is worth something. If maintaining WooCommerce eats ten hours a year and your time is worth £50 an hour, you’ve quietly spent £500 of the savings already.

There’s also a UK-specific wrinkle worth knowing. Shopify doesn’t add VAT to its payment processing fees for UK merchants, though Shopify Tax may apply once sales cross a threshold that’s usually £100,000 in the UK. That threshold matters if you’re scaling fast — it’s easy to miss until the invoice arrives.

Which platform is easier to manage day-to-day?

Shopify wins here, no contest. You log in, add a product, pick a theme, and you’re selling within an afternoon. There’s no server to configure and no plugin conflicts to debug at 11pm.

WooCommerce demands more from you. You’re choosing a host, installing SSL, picking a theme, and managing plugin updates that occasionally break each other. It’s not hard, exactly. It’s just ongoing. That’s the trade nobody mentions in the glossy comparison charts.

However, “easier” isn’t always “better.” If you already run a WordPress site with blog content driving traffic, bolting WooCommerce onto it keeps everything in one place. Splitting your blog and shop across two platforms creates its own headaches.

Does WooCommerce or Shopify rank better in Google?

WooCommerce generally has the edge for organic search, and here’s why. It inherits WordPress’s flexibility — you control URL structure, page speed optimisation, schema markup, and content architecture down to the smallest detail. That matters if blog content and SEO are part of your growth plan, which they should be for most UK small businesses without big ad budgets.

Shopify’s SEO has genuinely improved since its early years. Site speed is solid out of the box, and basic on-page SEO controls are built in. But you’re still working within Shopify’s structure. Some technical customisations that WooCommerce handles natively require a developer workaround or a paid app on Shopify.

If organic search is central to your customer acquisition strategy, that’s a real point in WooCommerce’s favour. If you’re driving traffic mainly through paid ads or social, the SEO gap matters far less.

Who actually wins for a UK small business?

Here’s my honest take, because I don’t think neutral-to-the-point-of-uselessness comparisons help anyone. If you’re a solo founder or small team selling under 100 products, don’t have technical staff, and want to launch fast, take Shopify. The monthly fee buys you peace of mind that’s worth more than the pounds saved on WooCommerce hosting.

If you already have a WordPress site, sell a growing catalogue, need custom checkout logic, or care deeply about organic traffic, WooCommerce earns its extra setup effort. It scales cheaper as revenue grows, and you’re never locked into a platform’s app marketplace for basic functionality.

One mistake I see constantly: businesses pick WooCommerce because it’s “free,” then discover six months later that nobody on their team can safely update a plugin without breaking the checkout. Free software isn’t free if it needs a developer on standby. Budget for that reality upfront, on either platform.

What about switching later?

Migrating between the two is possible in both directions, but it’s never as simple as an export-import wizard suggests. Product data, order history, SEO rankings, and customer accounts all need careful handling. If you’re unsure which platform fits, it’s worth getting the decision right the first time rather than paying twice for a migration. Our website cost breakdown guide covers what a proper WooCommerce or Shopify build actually costs once development, design, and setup are included.

FAQ

Is WooCommerce cheaper than Shopify for a UK small business?
Usually yes, over one to three years, once you account for hosting and plugins instead of Shopify’s monthly fee and transaction charges. The gap shrinks once you add the cost of your own time spent on maintenance.

Does Shopify charge VAT on transaction fees in the UK?
No. Shopify doesn’t add UK VAT on top of its payment processing fees, though Shopify Tax can apply once your sales pass roughly £100,000 in a calendar year.

Which platform is better for SEO, WooCommerce or Shopify?
WooCommerce generally offers more SEO flexibility because it’s built on WordPress, giving you deeper control over site structure and content. Shopify’s SEO has improved significantly but still works within a more fixed framework.

Can I switch from Shopify to WooCommerce later without losing data?
Yes, migration is possible, but product data, SEO rankings, and customer records all need careful handling by someone experienced with both platforms. A rushed migration risks lost rankings and broken order history.

WooCommerce vs Shopify UK isn’t a battle with one correct winner — it’s a match between your business model and each platform’s strengths. Shopify buys convenience. WooCommerce buys control and long-term savings, at the cost of your own time or a developer’s. Know which one you’re actually trading before you commit.

If you want a second opinion on which platform fits your specific business, or you need a developer to build and configure either one properly, message me on WhatsApp and I’ll give you a straight answer, not a sales pitch.

Do I need a developer to run a WooCommerce store?
Not strictly, but most small business owners benefit from at least an initial professional setup, since plugin conflicts and hosting configuration can get technical fast. Ongoing day-to-day management is manageable without one.

Is Shopify better for beginners with no technical background?
Yes. Shopify’s biggest advantage is that hosting, security, and updates are all handled for you, so you can launch and manage a store without touching code or server settings.

Small business owner selecting the best payment gateway option on a checkout tablet

Best Payment Gateway for Small Business (2026)

by with No Comment Client Resources

Quick answer: The best payment gateway for most small businesses in 2026 comes down to three realistic options: Stripe (2.9% + 30¢ online), Square (2.6% + 15¢ in-person, 3.3% + 30¢ online), and PayPal (3.49% + 49¢ standard). Stripe fits online-first businesses best, Square wins for in-person and hybrid models, and PayPal adds conversion trust at a higher cost.

I get asked this constantly during builds, usually right after a client has spent an hour comparing homepage marketing copy instead of actual numbers. Here’s the version with real math.

Stripe vs PayPal vs Square: The Actual 2026 Numbers

Let’s start with what each processor actually charges, because the headline percentage rarely tells the full story.

Stripe charges 2.9% plus 30 cents per successful online card charge in the US, according to Stripe’s own pricing page. There’s no setup fee and no monthly fee on the standard plan, which makes it easy to start with and predictable to scale.

Square charges 2.6% plus 15 cents for in-person transactions and 3.3% plus 30 cents for online payments. Square’s real strength is bundling — point-of-sale hardware, inventory, and booking tools all live under one account, which matters if you sell both in person and online.

PayPal charges 3.49% plus 49 cents on its standard plan, noticeably higher than Stripe or Square. PayPal’s Advanced and Pro plans drop closer to 2.59% plus 49 cents, but those require a monthly fee, so the savings only make sense once your volume justifies it.

Why the Headline Rate Isn’t the Real Cost

Here’s the part that trips people up: the fixed fee matters more than the percentage once your average sale gets small. A $15 sale through Stripe costs you 2.9% plus 30 cents, an effective rate closer to 4.9%, not 2.9%.

That’s why a coffee shop or a service business with lots of small transactions feels the fixed fee far more than a business selling $500 packages. If your average ticket is under $30, run the real math for each processor rather than trusting the advertised percentage alone.

International sales add another layer. Stripe adds 1.5% for international cards and 1% more for currency conversion, which can push a routine international sale’s fees close to 5.4% total. If you’re selling to customers outside the US regularly, that stacking cost deserves real attention before you commit to one processor.

Which Gateway Fits Which Business Model?

If your business is primarily online — services, digital products, e-commerce — Stripe usually wins. Its developer-friendly integration works cleanly with WordPress, Wix, and custom builds, and its checkout experience converts well without feeling generic.

If you’re mostly in-person, or hybrid with a physical location plus online orders, Square typically makes more sense. The bundled point-of-sale hardware and inventory tools save you from stitching together separate systems.

PayPal earns its higher cost through brand recognition. Some customers simply trust the PayPal button more, especially for higher-ticket or first-time purchases, and that trust can offset the extra fee through better conversion. It’s not the cheapest option, but it’s not irrational either — it depends on your audience.

Booking Deposits and Payment Gateways: A Different Problem

Booking-based businesses face a wrinkle none of the standard comparisons cover well: partial deposits and no-show fees. Not every gateway handles authorization holds, partial captures, or automatic cancellation charges equally well.

Stripe’s API generally offers the most flexibility here, letting a developer build custom deposit logic, automatic charge triggers on no-shows, and flexible refund rules. Square’s built-in booking tools handle this more simply out of the box, at the cost of some customization. If your business relies heavily on deposits or cancellation fees, that difference should weigh into your decision more than the base transaction rate.

The Mistake I See Most Often

Business owners frequently pick a gateway based on which one they’ve personally used as a customer, rather than which one fits their actual transaction pattern. That’s an understandable instinct, but it’s not the same evaluation.

A $40-average-ticket local service business and a $400-average-ticket consulting firm shouldn’t necessarily use the same processor, even if both owners personally prefer the same checkout button as shoppers. Run your actual numbers — average ticket size, transaction volume, and whether you sell internationally — before choosing.

What I Recommend for Most Small Business Sites

If I’m being direct: Stripe is my default recommendation for most online-first small business builds I work on, because the developer tooling is clean and the fees are predictable. That said, “default” doesn’t mean “always right” — a business with heavy in-person sales genuinely does better with Square’s bundled ecosystem.

The platform you’re building on matters too. If you’re weighing WordPress against Wix for your build, our WordPress vs Wix comparison covers how payment integration differs between the two, since that affects which gateways are easiest to implement cleanly.

Frequently Asked Questions

What’s the best payment gateway for a small online business?
Stripe is generally the best fit for online-first businesses due to its developer-friendly integration, predictable 2.9% + 30¢ pricing, and clean checkout experience.

Is PayPal more expensive than Stripe or Square?
Yes, on PayPal’s standard plan, which charges 3.49% + 49¢ compared to Stripe and Square’s roughly 2.9% + 30¢ rates. PayPal’s higher-tier plans reduce this but require monthly fees.

Which payment gateway is cheapest for small transactions?
Square tends to perform best for small in-person tickets due to its lower fixed fee (2.6% + 15¢), while Stripe’s fixed fee has a bigger relative impact on very small online sales.

Do payment gateways charge extra for international customers?
Yes. Most processors, including Stripe, add roughly 1.5% for international cards plus another 1% for currency conversion, which can meaningfully raise your effective rate.

Should a booking-based business choose a different gateway than a retail store?
Often, yes. Booking businesses benefit from gateways with strong deposit, authorization hold, and no-show fee handling, which varies significantly between Stripe, Square, and PayPal.

Can I use more than one payment gateway on my website?
Yes, and some businesses do, offering both Stripe and PayPal at checkout to capture customers who prefer one over the other. This adds development complexity but can improve conversion.

If you’re not sure which gateway fits your specific setup, that’s a quick conversation before you build anything. Message me on WhatsApp and I’ll help you figure out what actually makes sense for your business.

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 Resources

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 Resources

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 Resources

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 Resources

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 Resources

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.