Most of your audience arrives on a mid-range Android over mobile data. That single fact decides more about whether the site works than anything in the theme settings.
Two constraints run through everything: pages are read on phones over cellular, and half the content may be right-to-left.
A page that loads instantly on office fibre can take fifteen seconds on 3G. What matters is total transferred bytes, which is a number a lab test flatters and a real phone does not.
Urdu flips the entire layout, not just the text. Padding, icons, tables and carets all have a direction, and a theme that only translates strings looks broken.
Urdu display faces are large, and Nastaliq shaping is heavier than Latin rendering. Unsubsetted they delay first paint on exactly the devices least able to afford it.
International capacity out of Pakistan is finite and shared. Serving cached pages from a nearby edge removes the leg of the journey your server cannot influence.
The same brand is written in Urdu and in Latin transliteration, and visitors type either. Matching only one halves your site search silently.
A site signed off on a laptop over broadband tells you almost nothing about the experience the majority of your visitors are having.
On a slow connection the cost of a page is the bytes it asks for. Everything else is a rounding error next to that.
These differ from a standard WordPress site on the same plan, and each follows from a mobile-first audience and a bidirectional language.
| Setting | What we do | Why |
|---|---|---|
| Page weight target | Treated as a hard budget in kilobytes rather than a lab score | A synthetic score is measured on a fast connection, while the audience is on cellular where transferred bytes are the whole cost of the page. |
| Layout direction | Built on logical properties so the interface mirrors, not only the text | Urdu reverses the entire layout, and a theme that swaps strings without mirroring padding, icons and controls produces a page that reads as broken rather than as translated. |
| Urdu webfonts | Subset to the glyphs in use and served from the edge | Nastaliq faces are large and shape more expensively than Latin, so an unsubsetted file delays first paint most on the low-powered devices that dominate the audience. |
| Image delivery | Device-appropriate sizes enforced rather than relying on the browser | A desktop-sized image sent to a phone spends the visitor's data allowance to render something smaller than the file it downloaded. |
| Search indexing | Urdu and Latin transliterations matched against the same entry | Brands and place names are written in both scripts and visitors type whichever their keyboard offers, so indexing one form makes the other return nothing. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Free migration, a real weight budget, and Urdu that mirrors instead of merely translating.