We fix slow WordPress, Elementor and WooCommerce sites at the source. Core Web Vitals tuned on real devices, asset pipelines rebuilt, queries profiled, third-party scripts controlled and caches layered correctly.
Most speed plugins chase synthetic Lighthouse scores while the real users on cellular phones still wait four seconds for a hero image. We measure with field data from CrUX, real device throttling and Server-Timing so the wins show up where people actually browse.
Every engagement ships a before and after report with LCP, INP, CLS and TTFB numbers, the fixes that moved each metric and the code, config or infra change behind it. Nothing gets marked done on vibes.
A structured, measurable process. You see the baseline, the hypotheses, the fixes and the lift. No black box, no guesswork.
We capture CrUX field data, run Lighthouse and WebPageTest on representative URLs, profile the backend with Query Monitor and Server-Timing and write a ranked list of hypotheses by expected impact on LCP, INP and CLS.
Images converted to AVIF or WebP with correct sizes, fonts subset and preloaded, render-blocking CSS and JS resolved, third-party scripts deferred or proxied, hero resources preloaded and layout shift removed at the source.
Slow queries rewritten or cached, autoloaded options pruned, object cache wired to Redis, page cache layered with stale-while-revalidate and an edge CDN configured with correct cache keys and bypass rules.
We re-run field and lab measurements, deliver a before and after report, wire a performance budget to CI and show your team how to keep scores green when new plugins or content land.
A caching plugin is not a strategy. A generalist freelancer will not profile your database. Here is how we stack up on work that actually moves Core Web Vitals.
Pricing reflects scope and site complexity, not hours burnt. Pick a tier close to your needs or ask for a custom estimate after the audit.
Focused audit and quick wins on a standard marketing site. Core Web Vitals lift with frontend and cache fixes.
Full remediation across frontend, backend and CDN. Report, performance budget and handover session included.
Complex WooCommerce, membership or multisite work. Backend profiling, cart and search caching done right.
Ongoing performance retainer with field-data monitoring, CI budgets and quarterly regression sweeps.
We do not close a performance ticket on a lab score alone. Wins have to show up for real users on real devices over real networks.
Hero resource preloaded, image served in modern format at correct size, render path unblocked on mobile.
Long tasks broken up, third-party scripts deferred, main thread kept responsive under real interaction.
Explicit dimensions on media, font swap strategy set and reserved space for late-loading widgets.
PHP profiled, slow queries rewritten, autoloaded options pruned and page cache serving the bulk of traffic.
Performance, accessibility, SEO and best practices all measured and documented before we close the job.
Improvement verified on 28 day field data, not just a single lab run you can cherry-pick.
Cache keys, bypass cookies and purge rules set so logged-in and cart traffic never serves stale content.
Pull requests fail if LCP, bundle size or long tasks regress beyond the threshold agreed with you.
Your team gets a runbook covering budgets, monitoring dashboards and how to diagnose the next regression.
We are the silent performance team behind design and marketing agencies. Your client sees your audit, your report and your brand on every artefact. Our name never appears in the plugin header, the Slack channel or the handover docs.
Audit reports, dashboards and runbooks carry your brand, not ours.
One point of contact for every engagement. Shared Slack, weekly syncs, fast replies.
Retainer rates, bulk discounts and priority scheduling for agency partners.
We plug into your ClickUp, Linear, Jira or Notion. No tool switching, no friction for your team.
You send the staging access, current Lighthouse and any pain points the client has raised.
We run the baseline, write the ranked hypotheses and send you a partner rate quote. Never shown to your client.
You mark up, brand the proposal and present it on your letterhead at your price.
Your client signs off on your terms, with your brand, and pays you directly.
Silent work on branded staging. No vendor credits, no email signatures, no footer links from us.
You review the before and after, accept handover and ship the report to your client under your agency name.
Yes. We audit page-builder assets, unused widgets, oversized DOM output, responsive images, fonts, animations and third-party scripts. If the builder is the bottleneck, we clean what can be cleaned and recommend a rebuild only when it is the better long-term option.
Real work. A caching plugin is five minutes of the job. The rest is image pipeline, font strategy, render-blocking scripts, slow queries, autoloaded options, object cache on Redis and an edge CDN configured with correct cache keys. We hand you a report showing which change moved which metric.
Core Web Vitals first. LCP under 2.5s, INP under 200ms, CLS under 0.1 on mobile CrUX field data. We also track TTFB, total blocking time, bytes shipped and the full Lighthouse score. Lab runs confirm the theory, field data confirms the win for real users.
No. Work happens on a staging clone with a snapshot of production. We document every change, test cross-browser and gate the release on the performance budget we agreed with you. If something regresses, we roll back and investigate before shipping again.
Yes. Commerce is where most of the interesting perf work lives. Cart fragments, dynamic product pages, search filters, admin-ajax and payment redirects all need the right cache bypass rules, not a flat page cache. We handle that without breaking checkout.
A focused audit and quick wins takes 1 to 2 weeks. A full remediation with backend, cache and edge work on a WooCommerce or large site takes 2 to 4 weeks. You get a firm timeline in the written scope before work begins.
Yes. We wire a performance budget to CI so a pull request that regresses LCP or bundle size fails the build. Monthly retainers include field-data monitoring, budget reviews and quarterly regression sweeps so new plugins and content never quietly tank scores.
Share the URL, current pain points and any target metrics. A performance engineer will respond with a baseline snapshot and a written scope within one business day.