Website speed optimization, measured before and after.
A slow website loses the customer before the page loads. I find what is actually slowing your site, fix it at the server, the cache and the page, then measure again so you can see the difference for yourself.
Or call or text (502) 387-1142
Websites I have built for Kentucky businesses
Most slow sites are slow for two or three reasons, not twenty.
Speed tools hand you a long list of warnings, and most of them barely matter. On the WordPress sites I see, the time usually goes to a few places: a server that takes too long to answer, pages rebuilt from scratch on every visit instead of cached, images far larger than the screen, and scripts loaded on every page whether they are needed or not.
Fix those and much of the list stops mattering. That is how I approach website speed optimization: measure, find the few things that cost the most time, fix them properly, and measure again.
The work that actually moves the numbers.
Faster server response
Current PHP, a server that is not crowded, and a database cleared of years of leftovers. Server response is the floor every other improvement stands on.
Full-page caching, two layers
Pages cached on the server and at Cloudflare’s edge, close to your visitors. Cloudflare does not cache HTML by default, so the rules are written for your site.
Caching that respects carts
On WooCommerce, the cart, checkout and account pages stay out of the cache, so no shopper ever sees someone else’s basket or a stale price at checkout.
Images that weigh what they should
Photos resized to the size they are shown, converted to modern formats and loaded only as visitors scroll to them, with the originals kept safe.
Less code on every page
Plugins, fonts, sliders and tracking tags audited. Anything a page does not need is removed or loaded only where it is used.
Layouts that hold still
Images and embeds are given their space up front, so text does not jump around as the page loads. That is exactly what the layout-shift score measures.
Same sites, same content, a fraction of the wait.
Todd Lewis Law: homepage response down from as much as 1.95 seconds to 0.16, and homepage weight cut from 4.7 MB to 1.3 MB, with nothing removed from the page. The site moved to my server, gained two layers of caching and lost its oversized images.
Vendome Copper & Brass Works: homepage response from roughly one second to between 0.12 and 0.19 seconds for visitors, after a move to current PHP, server-side caching and the removal of a third-party image proxy. The database shrank from 448 MB to 314 MB along the way.
The Island Earth, my own 3,800-product store: origin response roughly halved on every page, and cached pages reach visitors in about 0.2Â seconds.
Core Web Vitals in plain English
Google measures how real visitors experience a page with three Core Web Vitals, set out in its Web Vitals guide:
- Largest Contentful Paint (LCP): how long the main content takes to appear. Good is 2.5 seconds or less.
- Interaction to Next Paint (INP): how quickly the page responds when someone taps or clicks. Good is 200 milliseconds or less. INP replaced First Input Delay as a Core Web Vital in 2024.
- Cumulative Layout Shift (CLS): how much the layout jumps while it loads. Good is 0.1 or less.
Google judges each one at the 75th percentile of real page loads, on phones and desktops separately. A fast test on your office computer does not mean your customers on a phone see a fast site.
PageSpeed Insights shows two kinds of numbers. Field data comes from real Chrome users over the previous 28 days. Lab data comes from a single simulated load on one device and one network. They often disagree, and the field data is what your visitors actually lived through. A lab score of 100 is nice to have; it is not the goal.
Google says good Core Web Vitals line up with what its ranking systems reward, but speed does not replace useful content. A faster site earns its keep with people first: less waiting between a visitor and your phone number. If you want a quick outside look at your own site, try the WordPress health check.
Measure, fix the big things, measure again.
Measure
Server response, page weight and Core Web Vitals recorded for your key pages, using real-visitor data wherever Google has it.
Find the cost
Each delay traced to its cause: the server, the cache, an image, a plugin or a script.
Fix in order
The biggest wins first, tested on a copy, so nothing breaks on the live site while it gets faster.
Prove it
The same measurements again, side by side with the first ones, in a short plain report.
What speed work can and cannot promise.
No score or ranking promises
I will not promise a 100 or a ranking. Lab scores swing from run to run, and a busy store will never test like a one-page brochure site.
Sometimes it is the host
If the server is the bottleneck, no plugin will fix it. I will say so, and moving hosts may be the real fix.
Sometimes it is the build
A site built on a heavy page builder can only go so far. If a redesign is the honest answer, you will hear it before you spend money on tuning.
Website speed optimization, answered.
What is website speed optimization?
Finding what makes your pages slow for real visitors and fixing it: server response, caching, image sizes, scripts and layout stability. Done properly, it is measured before and after, so you can see what changed.
Will a caching plugin make my site fast?
It helps, often a lot, but on its own it cannot fix a slow server, huge images or heavy scripts. On a store it also has to be set up so carts and checkouts are never cached.
Why is my PageSpeed score different every time?
The score comes from a single simulated load, and small differences in network and server timing change it. The field data in the same report, from real visitors over the previous 28 days, is steadier and matters more.
Does site speed affect Google rankings?
Google says good Core Web Vitals align with what its ranking systems reward, and recommends achieving them. Speed will not outrank better content, but a slow site makes good content harder to use.
Can you speed up a WooCommerce store?
Yes. Stores need extra care because cart, checkout and account pages must never be cached. I keep those pages dynamic and cache everything else, then test a real order to be sure.
How much does website speed optimization cost?
It depends on what is slowing the site. Some fixes are server and cache settings; others mean reworking images or templates. I measure first and quote from a short written scope, so the number matches the work.
Send me your slowest page.
Tell me which page feels slow and where your site is hosted. I work from Louisville, Kentucky, on sites anywhere in the United States, and I will tell you what is costing the most time, whether or not you hire me.
Connect with me
Tell me which page is slow.
What happens next
- 01I reply, usually the same day. Every message comes straight to me, not a ticket queue.
- 02A short call. What the site needs to do, who it is for, and what has not worked before.
- 03A written scope and flat quote. Before any work starts, with hosting and ongoing care listed separately.
5.0 on Google · 23 reviews · I usually reply the same day