01 The Speed Rescue

We fix slow WordPress sites in one week.

$699 fixed. One WordPress site, one week, fixes implemented, not a PDF telling you to hire someone. If your mobile Core Web Vitals are not measurably better afterward, you pay nothing.

Your host is probably not the problem. We measured 83 slow WordPress sites: the median server answered in 85ms, and the median page still took 7.6 seconds to show anything. The weight is in the theme, the images and the scripts.

Not sure this is your problem? Send the URL anyway. The triage is free, takes you 30 seconds, and we answer plainly, including "your site is fine".

02 Free triage

Send your site URL and we reply within 24 hours.

The top 3 things slowing your site down

URL and email, nothing else. A human runs the first-pass diagnosis we use on paid rescues and writes you one useful email within 24 hours on working days.

Free · answered by a founder · no call, no drip campaign, no obligation

03 The usual diagnosis

Your server is fast. Your page is not.

We measured 83 WordPress sites that were genuinely slow on mobile, taken from our own research pool of local businesses. The pattern was the same almost every time.

85ms

Median TTFB

How long the server took to answer. That is a healthy number. Hosting was almost never the bottleneck.

7.6s

Median LCP

How long until the main content actually appeared on a phone. Google calls anything over 2.5s poor.

21.7s

p90 LCP

The worst tenth of the group. Nobody waits 21 seconds. They hit back and call the next business on the list.

The gap between 85ms and 7.6s is everything that happens after the server replies: a theme shipping CSS and JavaScript for components your pages never use, full-size images resized in the browser instead of on the server, and a stack of plugins each loading its own scripts in the head. That is the work, and that is why "move to faster hosting" would have been the wrong advice for nearly all of them.

04 What the $699 buys

What you get.

  1. 01

    Real mobile numbers first

    LCP, INP, CLS and TTFB measured on a phone profile, on the pages that matter: home, your main service or content template, and whatever page your ads or search traffic actually land on. Written down before we touch anything.

  2. 02

    Theme weight cut at the source

    Page builders ship CSS and JavaScript for components your pages never use. We find what is loading, cut what is dead, and stop the rest from blocking the first paint.

  3. 03

    Images fixed properly

    The single most common cause we find: a 4000px hero served to a 390px phone. Correct sizes, modern formats, real lazy-loading below the fold, and the one image above the fold left eager so the LCP element does not wait.

  4. 04

    Plugin JavaScript put in its place

    Sliders, chat widgets, popups, analytics, fonts and tracking pixels loading in the head and blocking the page. We defer, scope or remove them, and document what went and why.

  5. 05

    Fixes implemented

    This is the difference. Most speed audits end with a PDF telling you what someone should do. Ours ends with the work done and the numbers to prove it.

Want to see the shape of the deliverable before you pay? Here is a sample Speed Rescue report, findings and numbers included.

05 How it works

How it works.

1

Send your site URL

The free triage. We run your site through the same first-pass diagnosis we use on paid work and reply within 24 hours with the top 3 things slowing it down. No call, no follow-up sequence.

free · 24h
2

Book the rescue: $699 fixed

One WordPress site, one week. We need wp-admin access and (ideally) hosting or SFTP access; we work on staging where your host provides it and tell you before anything touches production.

$699
3

Fixes implemented, not described

Mobile Core Web Vitals measured on your real templates, then the theme weight, the images and the scripts fixed in your site. You get before/after numbers from PageSpeed Insights and a short write-up of every change we made.

1 week

06 Who you're paying

Who does the work.

Etherlabz builds and maintains WordPress plugins in the open: Headless Bridge (WordPress as a headless CMS) and Simple Post Types. Read the code before you hand us wp-admin. The founders do the work themselves: no ticket queue, no offshore relay.

One site at a time, one week each. That is why the price can be fixed.

“Communication was clear, consistent, and highly responsive, making collaboration smooth and efficient.”

Kristjan Idrizi · Founder & CEO · ★ Verified 5.0 review on Clutch

07 FAQ

Fine print.

What does "measurably faster or free" mean exactly?

We benchmark your site before we start (PageSpeed Insights, mobile, your key templates) and again after. If the Core Web Vitals numbers have not measurably improved, you pay nothing. We put the before/after numbers in the handover, so neither side has to argue about it.

Is this not just "buy better hosting"?

Almost never, and we can show our work. Across 83 genuinely slow WordPress sites we measured, the median time to first byte was 85ms while the median LCP was 7.6 seconds. The server answered fast and the page still took seconds to appear. That gap is the theme, the images and the plugin JavaScript, which is what we fix. When hosting genuinely is the bottleneck, the free triage says so before you pay us anything.

What access do you need?

A wp-admin account (administrator) and hosting access where possible: SFTP or your host panel. We work on staging when your host offers it. Every change is listed in the handover, and we never touch content or user data beyond what testing requires.

Will my site look different afterward?

No. Speed work that changes your design is a redesign wearing a disguise. We agree in advance on anything visible (a slider that has to go, a font that has to be swapped for a system stack) and you can say no to any of it. If you do want the design changed, that is the €490 UI/UX audit and a separate conversation.

Can my live site break while you work on it?

We take a full backup (files and database) before any change. Work happens on staging where your host provides it; otherwise changes go in one at a time in an agreed window, each one reversible, with the backup as the floor. If anything misbehaves we restore and tell you what happened.

What counts as one site?

One WordPress installation on one domain. Custom themes and page builders are fine (that is most sites we see). A multisite network, a second language site on its own install, or a headless frontend on top counts as more and needs a quote first. Write to us before paying and we quote it properly.

I have a WooCommerce store. Is this the right one?

No. A store has a cart and a checkout that need their own treatment, and plugin conflicts that speed work alone will not solve. That is the $699 Store Rescue, same price, same week, with the checkout and conflict work included.

When do I pay, and how does the refund work?

You pay the $699 to book the week; the benchmark numbers are taken before we touch anything and again at handover, both from PageSpeed Insights on the same templates. If the after numbers are not better than the before numbers, you say so at handover and the fee comes back in full. No claim forms, no argument: the numbers are in the report we both look at.

What happens after the week?

You get the change log, the before/after numbers, and a short list of what to watch. Sites get slow again when plugins pile back up, so if you want us to keep it fast, that is what the Care Plans are for, from $99/mo. No pressure; the rescue stands on its own.

Running a shop? That is the $699 Store Rescue, which adds the checkout and plugin-conflict work. Site hacked instead of slow? That is the security page. Design rather than speed? The €490 UI/UX audit.

Start with the free triage.

30 seconds of your time, 24 hours of ours. The top 3 things slowing your site down, in writing, then you decide about the $699.