What actually makes a Dubai website slow
Almost never the design. It's usually four things at once:
- A heavy page-builder stack.
- A hero image nobody resized.
- A dozen plugins each loading their own scripts.
- An origin server a long way from the person waiting.
On a phone on mobile data that adds up to seconds before a photograph appears, and seconds is where people leave. Project One Motors was exactly that: a WordPress build that took four seconds to load a photo of a car, and needed touching in three places to add one.
What I build instead
- Next.js, generated ahead of time wherever a page can be static - so the visitor gets HTML, not a database round trip.
- Cloudflare's edge, so the page is served near the person asking for it rather than from one server somewhere else entirely.
- Images resized and served as WebP at the size the layout actually uses, which is usually the single biggest win available on a media-heavy site.
- An admin built around the client's real workflow, because a site nobody can update goes out of date, and an out-of-date site costs more than a slow one.
0.4 seconds, on a real client site
The Project One Motors rebuild is proof rather than a promise. A supercar dealership whose website took four seconds to show a photo of a car worth more than an apartment. I rebuilt it as a custom Next.js platform on Cloudflare's edge and it loads in four tenths of a second.
The risky part was never the build, it was the migration - a dealership's organic search traffic is its foot traffic - so the redirects were mapped, the URL structure kept where it had earned its rankings, and the schema markup rebuilt properly.
This site is the same argument
mayantha.net runs on the stack it's describing: Next.js, statically generated, on Cloudflare. Nothing here is hosted somewhere I wouldn't put a client. Eating your own cooking is the cheapest credibility available.
Speed is one input, not the whole game
Being fast helps you rank, and it stops helping the moment there's nothing on the page worth ranking. A Dubai dealership genuinely lost a page-one spot to a homepage that was too slow on a phone, and I've written up how speed moves a ranking and where it stops mattering.
But a fast page with thin content is just a fast page. In my experience speed shows up in conversion before it shows up in position.