Server level
GZIP compression, browser caching and the server settings that quietly throttle a busy site. If the hosting really is the bottleneck we say so, and recommend what to move to.
Website speed optimization
We take WordPress and custom sites to a target we put in writing: 90 or more on desktop and 75 or more on mobile PageSpeed, with before-and-after reports you can read. The price is fixed by the size of your site, not by the hour.
Free, instant, and straight from Google. No email, no sign-up.
Try it now
Type your address and we send it straight to Google PageSpeed Insights, the test Google itself ranks on. The full report opens in a new tab, and the mobile and desktop scores appear here too. Nothing is stored and nothing is sent to us.
Scores come straight from Google PageSpeed Insights and can move a few points between runs. We work to the same test, on the same settings, before and after.
What we measure, not what we assume
Egyptian and Gulf WordPress sites we maintain, all measured with the same tool on the same simulated phone. The full method and findings are published.
Sound familiar?
If two of these are true for your site, there is almost certainly a double-digit score sitting on the table.
It usually is. The same sites we measured score 85 on desktop and 67 on a phone, and the phone is the number Google ranks on.
Every second of wait is budget spent on a visitor who leaves before the page appears.
In our measurement the median server answered in 131 ms. The server was rarely the problem.
Caching helps what your own site sends. Most of the weight we find comes from somewhere else.
You get a list of red items from a tool, not a diagnosis of your site.
The real cause
These are the six worst offenders from the September measurement. Not one of them is the website's own code, and not one is fixed by changing host.
| Three Google Tag Manager containers on one site | 1,116 ms blocking · 502 KB |
| A single embedded YouTube video | 1,041,445 bytes |
| One third-party chat and reviews widget | 975 ms render-blocking, on every run |
| Google Fonts loaded from Google's servers | 763 ms render-blocking |
| A hosting provider's own injected script | 933 ms render-blocking |
| A Facebook pixel plus a session recorder | 495 KB combined |
First, the audit
Google PageSpeed Insights, GTmetrix and Pingdom on your real pages, not a guess from the outside.
The work
Biggest win first. We measure after each area, so you can see which change bought which second.
GZIP compression, browser caching and the server settings that quietly throttle a busy site. If the hosting really is the bottleneck we say so, and recommend what to move to.
Every plugin audited for what it costs in milliseconds. Unused ones removed, heavy ones replaced with lighter alternatives, with your sign-off on each.
Spam comments, post revisions and expired transients cleaned out, then an automatic clean-up scheduled so it stays that way.
Compressed and resized without visible loss, converted to modern formats such as WebP, and lazy-loaded so nothing below the screen downloads before it is needed.
A caching plugin configured properly rather than installed and left on defaults, and a CDN so visitors are served from close to where they are.
CSS, JavaScript and HTML minified, and scripts combined and deferred so the render-blocking queue in front of your content disappears.
The phone view treated on its own terms, because that is where the damage is and the number Google ranks on.
The same test before and after, a written before-and-after report, and the list of what to watch so the score holds.
What we commit to
Measured with Google PageSpeed Insights, the same thing Google ranks on: load time, interactivity and visual stability.
A website does not stand still. New content, a plugin update, an embedded video, a tracking script added next month: each one takes something off the score. On the one-time plan the guarantee runs for 7 days after delivery and maintenance is yours from there. On the annual plan we re-optimise every quarter and watch it every month, and the guarantee runs for the whole term.
Pricing
Priced by the size of the site, counted from your sitemap. All rates are in US dollars and exclude 14% VAT. Each rate covers one WordPress site.
The full optimization above, delivered once. Scores guaranteed for 7 days after delivery; maintenance is yours after that.
The same optimization, then a full review and re-optimization every quarter, and monitoring every month. Scores guaranteed for the whole term.
| Two ways to buy it | Quarterly optimization | Monthly maintenance |
|---|---|---|
| Small siteUp to 50 pages | $500 | $100 |
| Medium site50 to 200 pages | $800 | $200 |
| Large siteMore than 200 pages | $1,500 | $300 |
How it goes
We measure your pages with PageSpeed Insights, GTmetrix and Pingdom, and send a written report with what is realistically achievable. If there is not enough to gain, we say so.
A fixed price from the page count and the plan you pick, with the score target written into it.
Backup, then one pass at a time, measuring as we go. Your site stays live.
Before and after, same test, same phone profile. In plain language.
Speed decays as content and plugins are added. The annual plan re-optimises quarterly and watches it monthly.
Proof
EGIC's site has held a PageSpeed score between 95 and 98 on mobile and desktop since we built it, checked every month rather than once at launch. Speed that is maintained is worth more than speed that is achieved.
Before you ask
Every change is made after a full backup, one at a time, and on a staging copy when the site takes orders. If something misbehaves we roll that single change back, not the whole job.
WordPress is most of what we see, and most of this page is written with it in mind. The same method works on custom sites, Shopify themes and anything else that loads in a browser; what changes is which levers exist.
Sometimes, and we will tell you when it is. But in our own measurement the median server answered in 131 milliseconds, so hosting was rarely the thing that made those sites slow. Ask anyone selling you an upgrade to show you the time-to-first-byte number first.
Until someone adds a heavy plugin, a video embed or a tracking script. That is the normal life of a website, which is why we re-measure monthly on a support plan instead of treating speed as a one-off.
Yes, and it often costs less that way. We hand over the list of changes with the measurement behind each one, and your developer applies what they want to own.
You hear that during the audit, before you pay for the optimization. We do not take a site on and discover afterwards that the target was never reachable.
Because after that, what happens to the site is out of our hands: new content, plugin updates, a video embed, a tracking script. The annual plan exists for companies that would rather we held the target all year than re-buy an optimization in eight months.
Where to go next
A website, a mobile app, a CRM or an ERP: tell us what you have in mind and we'll come back with a plan, a timeline and a price. Thirty minutes is enough to tell whether we're the right team.