Performance Fixes
Your Core Web Vitals report told you what's broken. I'll fix it.
Code-level fixes for LCP, CLS, and INP failures on WordPress, Shopify, WooCommerce, or a custom stack. No developer handoff, no plugin papering over the symptom: the root cause gets fixed in your code, then verified against real field data.
What gets fixed
Not a plugin. The actual root cause.
LCP (Largest Contentful Paint)
Render-blocking CSS and JS, unoptimised hero images, slow server response, and a font-loading strategy that delays the first meaningful paint.
CLS (Cumulative Layout Shift)
Unsized images and embeds, late-injected banners and ads, and web font swaps that shift content after the page looks done.
INP (Interaction to Next Paint)
Long main-thread tasks, oversized JS bundles, and third-party script bloat that makes clicks and taps feel laggy.
Platform-specific issues
Shopify Liquid theme scripts, WooCommerce plugin conflicts, and WordPress plugin bloat that a generic speed test can't diagnose.
Crawl and indexing
Broken redirect chains, orphaned pages, and resources blocked from Googlebot that keep pages from being properly indexed.
Structured data
Missing or broken schema markup for products, articles, local business, and FAQs, corrected and validated.
How it works
Send what you've got. I fix it. You get proof it worked.
Send me what you've got
An existing audit, a Lighthouse or PageSpeed report, or just your URL if you haven't had one yet. Either way, tell me what's bothering you about the site.
I fix it at the code level
In your theme, your components, your build: not a plugin that hides the symptom. You get a progress update as I work through it.
I verify the gain
Lighthouse re-run on the spot, and an optional re-check against real field data 60 days later to confirm the fix held under actual traffic.
Rate
One rate, billed only for the hours worked.
Performance fix implementation
Most single-issue fixes (one blocking script, one CLS culprit) take 1 to 3 hours. A full remediation across a whole site typically runs 8 to 20 hours depending on scope. Same rate whether it's standalone or a follow-up to an audit.
Already had a Full Site Audit or Quick Wins Audit? Fixes are billed at the same hourly rate.
Prices in ZAR (South African Rand).
FAQ
Common questions
Do you only do audits, or can you fix the issues too?
Both. Every audit includes a prioritised fix list, and I can implement the fixes directly at R980 an hour, the same rate whether it's a standalone job or a follow-up to an audit.
I already have an audit or PageSpeed report from someone else. Can you just fix it?
Yes. Send me the report or the URL and I'll scope the fix work directly. No need to redo the audit first.
How is this different from a caching plugin or an automated speed service?
Plugins and automated services typically defer, minify, or cache around a problem. I trace each Core Web Vitals failure to its root cause in the code and fix that, so it holds up under real traffic and doesn't break the next time a plugin updates.
How long does a performance fix take?
Most single-issue fixes, like one render-blocking script or one CLS culprit, take 1 to 3 hours. A full remediation across LCP, CLS, and INP typically runs 8 to 20 hours depending on how much technical debt is in the codebase.