A speed audit already pointed at caching
PageSpeed, GTmetrix or a developer already told you "set up caching and a CDN" — this is that, done properly.
Caching and a CDN, configured for your host — not a plugin left on default.
Page and object caching, plus CDN configuration matched to your specific stack and visitors' geography. Cart, checkout and logged-in pages excluded correctly, with a before-and-after TTFB and Core Web Vitals report.
THE PROBLEM
What a generic caching plugin install usually gets wrong
Installing a caching plugin and leaving it on default settings is not the same as having caching configured. Most of the problems it causes trace back to the same handful of gaps.
WHAT USUALLY GETS SKIPPED
- Checkout, cart or account pages cached by accident, serving one visitor's session or pricing to another
- A CDN pointed at the wrong origin or geography, adding latency instead of removing it
- The plugin's caching layer fighting the host's own built-in caching, producing stale pages that need a hard refresh
- Cache headers left unset, so the browser and CDN re-fetch assets that should have been served instantly
- No purge rule tied to actual content changes, so edits don't show up until someone remembers to clear the cache manually
- Server response time (TTFB) never actually measured, so nobody knows if the setup even helped
WHO THIS IS FOR
When this is the right booking
This is the caching-and-CDN implementation specifically — not a full diagnosis. If you're not sure caching is actually the problem, WordPress Speed Optimization or Core Web Vitals Fix will find the real cause first.
Visitors are spread across regions
Traffic coming from outside your server's own region, adding latency a CDN is built to remove.
Running WooCommerce and worried about caching it wrong
Cart, checkout and account pages need explicit exclusion rules — getting this wrong breaks orders, not just speed.
A caching plugin is already installed but misbehaving
Stale content, broken checkout, or conflicts with the host's own caching — reconfigured rather than replaced where possible.
SCOPE
What I deliver
- Page and object caching configured for your specific host, not a one-size plugin default
- A CDN set up and configured for your visitors' actual geography, with correct cache headers and purge rules
- Cache-exclusion rules set correctly for cart, checkout, account pages and any logged-in views
- Conflicts checked and resolved between the caching layer and your host's own built-in caching
- A before-and-after TTFB and Core Web Vitals report, so the improvement is measured, not assumed
TECHNOLOGY I USE
- WordPress
- WP Rocket
- W3 Total Cache
- Cloudflare
- Redis / Object Cache
- .htaccess
- Nginx
- PageSpeed Insights
PROCESS
How a caching & CDN setup runs
-
Baseline the current state
TTFB, cache headers and any existing caching layer measured and recorded first, so the before-and-after report is real.
-
Check host-level caching
Confirm what your host already does at server level, so the plugin and CDN layers are configured to work with it, not against it.
-
Configure page and object caching
Set up and tuned for your specific stack, with exclusion rules for cart, checkout, account pages and any logged-in views.
-
Set up the CDN
Pointed at the right origin, with correct cache headers and a purge rule tied to actual content changes.
-
Test the exclusions
Cart and checkout tested directly to confirm nothing gets served stale to the wrong visitor.
-
Deliver the report
A before-and-after TTFB and Core Web Vitals comparison, so the improvement is measured, not assumed.
BENEFITS
What you get out of it
Caching and a CDN done right is one of the highest-impact, lowest-risk performance changes a WordPress site can make — done wrong, it's also one of the most common causes of a broken checkout.
Faster TTFB, measured
A concrete before-and-after comparison, not a plugin dashboard that just says "optimized."
Nothing cached that shouldn't be
Cart, checkout and account pages explicitly excluded and tested, so speed doesn't come at the cost of broken orders.
Matched to your host, not generic
Configured against what your specific host and stack actually do, so the caching layer and CDN work together instead of colliding.
RELEVANT WORK
Projects built with performance as a requirement
Each of these is written up as a full case study — the problem, the approach, the stack and the outcome.
Formatry
A SaaS marketing site where TTFB and caching were tied directly to trial sign-up conversion, not just a scoring exercise.
- Webflow
- CMS
- Performance
Canvascroft
An image-heavy WooCommerce site where caching and CDN delivery needed to hold up without breaking checkout.
- WordPress
- Elementor
- WooCommerce
TESTIMONIALS
What clients say
Every completed Upwork contract to date, each rated 5.0 — quoted as written.
“He is very punctual on timelines and has a complete inside out knowledge of WordPress theme development.”
“He completed the customer theme development work before time. The work delivered is awesome and he delivered more than expected. Really a good and honest freelancer to work with.”
“Ashekur Rahman delivers the work timely and perfectly. His knowledge in wordpress is very vast and he can do anything in wordpress and web developement.”
FAQ
Questions I get asked
What people ask before booking, mostly about how this differs from the other performance services and whether it's safe for a store.
How is this different from WordPress Speed Optimization?
WordPress Speed Optimization looks at everything that could be slowing the site down — images, plugin bloat, code path, hosting and caching together. This service is the caching and CDN piece specifically: if that's already been diagnosed as the cause, or you just want the caching layer done properly, this is the narrower, faster booking.
How is this different from Core Web Vitals Fix?
Core Web Vitals Fix diagnoses and fixes whichever metric Search Console actually flagged — that could be LCP, INP or CLS, and the cause might have nothing to do with caching at all. This service is one specific implementation: server-side/page caching plus CDN configuration. If you already know caching is the gap, book this directly.
Will this conflict with my host's built-in caching?
That's checked as part of the setup. Some hosts already run their own server-level caching, and stacking a plugin's caching on top without coordinating the two is a common cause of stale pages or broken checkouts. The configuration is matched to what your host already does, not layered on blindly.
Do I need a paid CDN?
No — a free-tier CDN is enough for most WordPress sites, and that's the default unless your traffic or geography genuinely needs a paid tier. You get a straight recommendation either way, not an upsell to the more expensive option.
Will this break my cart or checkout pages?
Not if it's configured correctly, which is the point of doing it as a dedicated setup rather than a quick plugin install. Cart, checkout, account and any logged-in views are explicitly excluded from page caching so pricing, stock and session data stay accurate.
Do you work with clients outside Bangladesh?
Most of my clients are outside Bangladesh — the UK, Germany and the US primarily. I am based in Bangladesh and work across European and North American time zones without difficulty, with a same-day reply to anything urgent.
Available for new projects
NEXT STEP
Tell me about the host and stack, and I’ll scope the setup.
Based in Bangladesh, working with clients worldwide. Whether caching's never been configured or something's already conflicting — every serious enquiry gets a reply within one working day.
- Reply within one working day
- Fixed quote before work starts
- UK, EU and US hours covered
ALSO WORTH READING