What a speed fix costs and what it actually buys you
A speed audit for a UAE business site is AED 1,400 (about USD 380) and takes three working days. The fix work that follows is normally AED 2,600 to AED 5,900 (about USD 700 to USD 1,600). On a typical WordPress or page builder site that moves mobile Largest Contentful Paint from six or seven seconds to under two and a half seconds, which is the threshold Google calls good and the point where a visitor in Dubai, Doha or Riyadh stops feeling the wait.
What follows is the order we actually work in. If you read one section, read the one on measuring, because most speed budget here is spent on a problem nobody confirmed was real.
Measure properly before you touch anything
Nearly every slow site conversation opens with a screenshot of a score out of 100. That score is not the problem, and chasing it is how agencies bill for work no customer can feel. Two distinctions decide whether your numbers are worth acting on.
Lab data versus field data
Lab data is one simulated test on a throttled connection, which is what Lighthouse, PageSpeed Insights and WebPageTest give you. Field data is what real visitors experienced over a rolling 28 day window, collected by Chrome, and it is the only data Google uses for ranking. A site can score 92 in the lab and still fail Core Web Vitals in the field, because real people arrive on three year old Android phones on mobile data, not on a clean laptop with fibre. Pull the field numbers from Search Console first, then use lab tests to hunt the cause.
Test from a Gulf location, not a US server
Most free tools default to a test node in the United States or northern Europe. If your server sits in Frankfurt and the tester sits in Virginia, you are measuring a route none of your customers take. Run WebPageTest from Dubai, and read Time to First Byte separately, because distance shows up there first. A site hosted in the United States answers a UAE visitor roughly 180 to 300 milliseconds slower on the first byte alone, before a single image loads. That is not fatal by itself, but it sits underneath every other number and inflates all of them.
The real culprits, in the order they usually show up
Across the audits we run for Gulf clients, a short list explains most of the damage, and we check in roughly this order of how often each turns out to be the main offender.
Images straight off a camera or a phone
The most common cause and the cheapest to fix. A photographer sends 4,000 pixel wide JPEGs at four megabytes each, someone uploads them untouched, and the homepage ships 12 MB of images to a phone that displays them 380 pixels wide. Convert to WebP or AVIF, resize to the largest size actually rendered, add width and height attributes so nothing jumps while loading, and lazy load everything below the fold. That usually removes 60 to 80 percent of page weight. One warning: the hero image must stay eager and preloaded, because lazy loading the image that defines Largest Contentful Paint makes the score worse.
Plugin sprawl and heavy page builders
A five year old WordPress site with 38 plugins is carrying code left behind by three previous agencies. Page builders compound it: Elementor, WPBakery and Divi load their own libraries whether a page needs them or not. Deactivating what is unused, replacing single purpose plugins with a few lines of code, and dequeueing builder assets on pages built without the builder typically strips 400 to 900 KB per page. Audit for abandoned plugins while you are in there, because unmaintained plugins are the most common way these sites get hacked.
Render blocking scripts, chat widgets and tracking tags
Open the network tab and count third party domains. A normal Gulf SME site loads Google Analytics, Tag Manager, the Meta Pixel, a Snapchat or TikTok pixel, a WhatsApp button, a live chat tool, a review widget and a font provider, eight external connections competing with your own content. Chat widgets are the worst value on the page: 200 to 400 KB of JavaScript to render a floating button, so load it on first interaction. Payment scripts from PayTabs, Telr, Network International or Stripe belong on the checkout page only, never in the global header, and the same goes for booking widgets.
What each fix typically gains
Typical ranges from real audits on business sites in the region, not best cases. Measure before you buy.
| Fix | Typical gain | Effort |
|---|---|---|
| Compress, resize and convert images | 1.0 to 3.0 seconds off LCP | Low |
| Server, object and browser caching | 0.3 to 1.2 seconds off TTFB | Low |
| Defer chat, pixels and analytics tags | 0.5 to 2.0 seconds off interaction delay | Low |
| Remove unused plugins and builder assets | 0.4 to 1.5 seconds | Medium |
| Move hosting into the region, add a CDN | 0.15 to 0.4 seconds off TTFB | Medium |
| Self host and subset fonts, Arabic and Latin | 0.2 to 0.8 seconds, no text flash | Medium |
| Critical CSS, deferred stylesheets | 0.3 to 0.9 seconds off first paint | Medium |
| Rebuild the front end on a clean stack | 3 to 6 seconds, but it is a rebuild | High |
Notice that the cheapest work sits at the top. A proposal that opens with a rebuild, before anyone has compressed an image, is selling you the expensive thing first.
Hosting and CDN choices that matter for Gulf visitors
Hosting is where Gulf sites differ most from the generic advice online, and it is the one variable an owner can change in an afternoon.
Where your server actually sits
An AED 30 per month shared plan puts your site on a machine with several hundred others, usually in the United States,. Move to a region close to your visitors: AWS in Bahrain or the UAE, Azure UAE North, or a serious Dubai based host. If you serve government, healthcare or financial clients, or handle personal data under the UAE data protection law, hosting inside the country may be a contract requirement rather than a performance choice, so settle that before picking a plan. Keep the .ae domain at a registrar you control, use a fast DNS provider, and put a CDN in front. One caveat vendors skip: a CDN accelerates cached assets, not a slow origin, so a logged in dashboard stays slow until you fix the server behind it.
Arabic font loading, the cost nobody audits
On bilingual sites this is routinely the second heaviest thing on the page. An Arabic typeface covers a large glyph set, so one weight of Cairo, Tajawal, Almarai or IBM Plex Sans Arabic is several times the size of a Latin equivalent. Load four weights of an Arabic family plus a Latin family from a font provider and you have added 600 KB to 1.2 MB and two extra connections before your text renders. The other half of the problem is CSS: many themes ship both the left to right and the right to left stylesheet on every page, so Arabic visitors download the English layout rules too.
A font setup that actually works
Two weights maximum, regular and bold. WOFF2 only. Self host the files on your own domain so there is no third party lookup. Use unicode range so the browser fetches the Arabic file only when Arabic characters appear, preload the file used by the headline, and set font display to swap so text is readable while the font arrives. On the bilingual sites we have rebuilt that takes a typical font payload from around 900 KB to under 200 KB, and removes the flicker where Arabic headings reflow after the page appears.
What an audit and a fix engagement cost
Our published pricing on the Codelith Lab global page is fixed and quoted in AED with the USD equivalent, so you can approve it without a discovery call. Speed work sits inside that same ladder.
| Engagement | AED | USD | Timeline |
|---|---|---|---|
| Speed audit with a prioritised fix list | 1,400 | 380 | 3 working days |
| Standard fix, brochure site up to 15 pages | 2,600 | 700 | 5 to 7 working days |
| Deep fix, large or ecommerce site | 5,900 | 1,600 | 2 to 3 weeks |
| Rebuild as a fast business website | 5,900 | 1,600 | 3 to 4 weeks |
| Rebuild ecommerce with a clean checkout | 11,800 | 3,200 | 5 to 7 weeks |
| Care plan, monitoring and monthly checks | 440 per month | 120 per month | Ongoing |
On VAT, be precise with your accountant. We invoice from India, so our invoice does not carry UAE VAT the way a Dubai agency invoice would. A UAE registered business normally accounts for imported services under the reverse charge mechanism, declaring the 5 percent and recovering it in the same return when it is fully taxable, which usually nets to zero. Compare totals, not headline numbers.
How long results take in the real world
Lab numbers move the same day. Run WebPageTest an hour after the work ships and the improvement is already visible, which is why agencies love before and after screenshots. Field data is slower by design: the Chrome User Experience Report uses a rolling 28 day window, so Search Console will not show a clean pass until roughly four weeks after the fix, and six to eight weeks before the change is fully reflected across all URL groups. Plan your reporting around that, and do not panic in week two.
Ranking movement is the least predictable part, and any vendor promising positions is guessing. Page experience is a tiebreaker between comparable results, not a substitute for content and links. The commercial gain arrives earlier and is easier to prove: on Gulf ecommerce sites where we took mobile LCP from six seconds to under two and a half, the reliable movement was in bounce rate and completed checkouts, typically a 10 to 20 percent lift on mobile conversion, largest on paid traffic.
Find out what is actually slowing your site
Send us the URL. In three working days you get a measured audit from a Gulf test location, a prioritised fix list with expected seconds saved, and a fixed price to do it. No retainer, no lock in.
How to verify the improvement instead of trusting a report
A PDF full of green circles proves that someone ran a tool, not that your site got faster for customers. Verify it yourself, and insist the numbers below are part of the handover.
Five checks you can run without a developer
First, run WebPageTest from Dubai before and after, three runs, and compare the median rather than the best. Second, open Search Console four weeks later and confirm the mobile URL group has moved out of Poor. Third, hard refresh with the network tab open and compare the transferred size. Fourth, check field data in your analytics, so you are looking at real visitors. Fifth, watch a business number: bounce rate, add to cart, form submissions, WhatsApp clicks. If page weight fell and business numbers did not move in a month, speed was not your bottleneck, and an honest partner will say so.
When you should not buy a speed optimisation
Four situations where this is the wrong purchase. If your site gets a few hundred visits a month, speed is not your constraint, demand is, and the money belongs in search and paid acquisition. If visitors arrive and do not enquire, look at your offer and your call to action before your image sizes. If you are on a closed platform where you cannot control the asset pipeline, the ceiling is low and a migration beats more patches. And if your theme is a multipurpose marketplace theme with 30 plugin dependencies, we can shave 40 percent off the weight, but the floor underneath stays high.
The honest rule we apply: when the fix quote crosses about 60 percent of the rebuild price, rebuild instead. A clean, fast business website build is AED 5,900 (about USD 1,600) and arrives without the technical debt, so paying AED 4,000 to patch a site you already dislike is bad money. The same logic runs upward: if the slowness is a bloated booking system bolted onto a marketing site, the answer is a proper application, from AED 27,500 (about USD 7,500) for a web app or SaaS MVP, not another caching plugin.
How we work, and where we are based
Our team is in India. We are not going to dress that up, because you will find out and it will cost us the relationship. What it means for you is senior engineers at a lower cost base than a Dubai agency, and a working day that starts at 08:00 in the UAE and runs past 17:30 Gulf time, so you get answers inside your own business hours rather than the following morning. Calls happen on WhatsApp and Google Meet, and you deal with the engineer doing the work, not an account manager relaying messages.
The commercial safeguards matter more than any sales pitch. Every engagement has a written scope listing the exact fixes, a fixed price, and milestones you sign off. The code and repository are yours from day one, in your own GitHub or Bitbucket account, and hosting stays in your name with your billing, so if we vanished tomorrow another developer picks it up with no negotiation. We take a full backup and work on staging before touching production, so rollback takes minutes. Change requests are quoted per item and approved in writing before we start. Support is one business day for a response, same day for a down site on the care plan, and handover includes a recorded walkthrough and written notes.
Also read: Our full Gulf price list, including landing pages at AED 2,600, business websites at AED 5,900 and white label work for agencies from USD 2,400 per month, is published openly on the Codelith Lab global pricing page.
