Saudi WordPress hosting where the calendar is not Gregorian.
Business dates here are often Hijri, the weekend is Friday and Saturday, and one month of the year rearranges when people are awake.
A different year and a different week.
Date handling written for a Monday-to-Friday Gregorian world is wrong here in three separate ways.
Hijri dates alongside Gregorian
Official and business dates are frequently Hijri, which is a lunar calendar with different month lengths. Both are stored rather than one being derived on display.
A week that ends on Thursday
Reports, schedules and business-day calculations assume Monday to Friday by default. Here the working week runs Sunday to Thursday and every such calculation shifts.
Ramadan changes when traffic arrives
Activity moves to late evening and overnight for a month, so capacity planned on an annual average is planned for the wrong hours.
An origin in the region
Signed-in and checkout requests always reach the origin, and Gulf audiences are well served from within Asia.
Right-to-left as the default direction
Arabic content needs mirrored layout, not translated strings in a left-to-right frame.
Business days that are not business days.
A delivery estimate of three business days computed against a Monday-to-Friday week gives a Saudi customer a date that falls on their weekend.
- Hijri and Gregorian dates both stored
- Business-day logic using a Sunday-to-Thursday week
- Capacity planned for Ramadan hours
- Layout mirrored for Arabic
Dates a customer recognises.
The visible failure is not slowness. It is a promised delivery date that lands on the weekend, or an invoice dated in a calendar the recipient does not use.
What we change for Saudi sites
Three separate date assumptions have to change, and each of them is invisible until a customer points at a wrong date.
| Setting | What we do | Why |
|---|---|---|
| Calendar storage | Hijri and Gregorian both recorded rather than derived | Hijri months vary in length and official dates use them, so deriving one from the other at display time produces dates that disagree with the document they came from. |
| Business-day logic | Computed against a Sunday-to-Thursday week | Delivery estimates and service windows assume Monday to Friday by default, which places a promised date on the local weekend. |
| Seasonal capacity | Planned for Ramadan's shifted activity | Traffic moves to late evening and overnight for a month, so capacity sized on an annual average is sized for the wrong hours entirely. |
| Text direction | Right-to-left treated as the default for Arabic content | Arabic strings inside a left-to-right layout produce a page that reads inside out rather than one that is merely translated. |
| Origin region | Asia, close to Gulf audiences | Cached pages are local either way, but every signed-in and checkout request reaches the origin. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Do I need Hijri dates on my site?
Why do my delivery estimates land on the weekend?
Does Ramadan affect hosting?
Is right-to-left just a translation setting?
Use the calendar your customers use.
Move the site to an Asia origin - migration is free, date handling reviewed.