هذا المقال متوفر باللغة العربية — اقرأ بالعربية
A slow website costs you visitors before they read a single word. For Arabic websites there are a few extra challenges: heavier Arabic fonts, right-to-left layouts that sometimes load extra stylesheets, and audiences spread across Egypt, the Gulf and beyond, often browsing on mobile data. In this guide we’ll show you how to speed up WordPress for Arabic sites, starting with how speed is measured and ending with a practical checklist.
How Google measures speed: Core Web Vitals
Google measures real user experience with three metrics called Core Web Vitals. According to web.dev, these are the thresholds for a “good” experience:
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How fast the main content appears | 2.5 seconds or less | More than 4 seconds |
| INP (Interaction to Next Paint) | How quickly the page responds to taps and clicks | 200 milliseconds or less | More than 500 milliseconds |
| CLS (Cumulative Layout Shift) | How much the layout jumps while loading | 0.1 or less | More than 0.25 |
Google recommends measuring these at the 75th percentile of real page visits, separately for mobile and desktop. INP replaced the older FID metric as a Core Web Vital in March 2024, and it’s often the hardest one for sites loaded with scripts.
To see your numbers, use PageSpeed Insights for a single page, and the Core Web Vitals report in Google Search Console for the whole site. Lab tests are useful for debugging, but the real user data is what tells you how your visitors actually experience the site.
How to read a PageSpeed Insights report
When you enter a page’s URL, you’ll see two different sections, and many people mix them up:
- Real user experience. This appears if your page or site has enough traffic, and shows LCP, INP and CLS from actual visits over a recent period. This is the part that matters most.
- Lab diagnostics. A simulated test on a virtual device and network, with a score out of 100 and a list of suggestions. It’s very useful for finding causes, but the score itself isn’t the goal.
Always start with the mobile results, and focus on suggestions about the hero image, fonts and scripts, since those usually make the biggest difference on Arabic sites. After every change, test the same page again to confirm it actually helped.
Why Arabic sites face extra speed challenges
- Arabic fonts are larger. An Arabic font file has to cover many letter shapes, and many sites also load a separate Latin font plus several weights of each. That adds up quickly.
- Fonts can shift the layout. If the fallback font and the final Arabic font have very different sizes, text jumps when the web font arrives, which hurts CLS.
- RTL stylesheets. Some themes and plugins load a separate RTL stylesheet on top of the main one instead of a single combined file.
- Distance to the server. A site hosted far from its audience adds delay to every request, which shows up in LCP.
- Mobile-first audiences. Many visitors in the region browse on phones over mobile data, so heavy pages hurt more.
How to speed up WordPress for Arabic sites, step by step
1. Start with good hosting close to your audience
No plugin can fully make up for a slow server. Choose hosting with a modern PHP version, enough resources for your traffic, and servers reasonably close to where your visitors are. Then put a CDN in front of the site so static files like images, CSS and fonts are served from locations near your visitors.
2. Turn on page caching
Without caching, WordPress builds every page from scratch with PHP and database queries on every visit. Page caching saves a ready HTML copy and serves it instantly. Many hosts provide server-level caching, and if yours doesn’t, a reputable caching plugin does the job. For dynamic sites like WooCommerce stores, add a persistent object cache such as Redis if your host supports it, and make sure the cart, checkout and account pages are excluded from page cache.
3. Handle Arabic fonts carefully
Fonts are where Arabic sites can win the most, quickly:
- Use fewer fonts and weights. One Arabic family in two weights, regular and bold, is enough for most sites.
- Use the WOFF2 format, which is compressed and supported by modern browsers.
- Host fonts on your own domain when you can, so the browser doesn’t need extra connections to a third-party server.
- Subset the font to the characters you actually need, and use
unicode-rangeso the Latin font only downloads for Latin text. - Use
font-display: swapso text shows immediately with a fallback font, then pick a fallback with similar proportions to reduce the jump. - Preload only the one font used in the main heading or body above the fold. Preloading everything slows things down instead.
4. Optimize images, especially the LCP image
- Serve modern formats such as WebP or AVIF, which WordPress supports in the media library.
- Upload images at the size they’re actually displayed, not straight from the camera.
- WordPress lazy-loads images by default, which is good for images further down the page. Make sure your main hero image, which is usually the LCP element, is not lazy-loaded.
- Give every image width and height attributes so the browser reserves space and the layout doesn’t shift.
5. Cut down on JavaScript
Heavy scripts are the main enemy of INP. Review what loads on each page:
- Remove plugins you don’t need, and check which ones load scripts on every page even when only one page uses them.
- Delay non-critical scripts such as chat widgets, heatmaps and some tracking tags until after the page becomes interactive.
- Be careful with sliders, animations and large page builder add-on packs. Each one adds code that the browser has to run.
6. Use the speed features already in WordPress
WordPress 6.8 added speculative loading using the browser’s Speculation Rules API. By default it prefetches same-site links conservatively, when a visitor starts clicking a link, so the next page opens faster. It doesn’t run for logged-in users or on sites without pretty permalinks. Developers can adjust it with the wp_speculation_rules_configuration filter and exclude paths such as cart or checkout URLs.
7. Keep the database light
Over time, the database collects post revisions, expired transients, spam comments and leftover tables from deleted plugins. Clean these up carefully, after a backup, and limit how many revisions WordPress keeps. On WooCommerce stores, also check that old sessions and logs aren’t piling up. Database cleanup is easier to keep up with when it’s part of a regular schedule, and our list of routine WordPress maintenance tasks shows where it fits.
8. Check how your theme handles right-to-left
WordPress loads a theme’s rtl.css file automatically when the site language is right-to-left. That’s normal, but check what actually loads on your Arabic pages. Some setups load the full left-to-right stylesheet and then a second large file that overrides most of it, and some plugins add their own RTL files too. Open your browser’s developer tools, look at the CSS files on an Arabic page, and remove anything that loads twice or isn’t used. Themes built with modern CSS logical properties, which describe “start” and “end” instead of “left” and “right”, usually need far less extra RTL code. If the problem goes beyond speed and the layout itself breaks in Arabic, our guide to fixing RTL layout issues in WordPress walks through the common causes and fixes.
Common mistakes we see on Arabic sites
- Loading the same Arabic font from two sources, for example from the theme and again from a page builder.
- Loading every font weight from thin to black when the design uses two.
- Installing three speed plugins at once, which then conflict and sometimes make the site slower or break the layout.
- Testing only on desktop on a fast office connection, while most visitors use phones.
- Chasing a perfect lab score instead of improving the real user numbers in Search Console.
A speed checklist for Arabic WordPress sites
- Measure the current state with PageSpeed Insights and Search Console, and note the numbers.
- Confirm hosting quality and add a CDN.
- Turn on page caching, with the right exclusions for stores.
- Reduce fonts to one Arabic family and two weights, in WOFF2, with swap.
- Compress images, use modern formats, and don’t lazy-load the hero image.
- Remove or delay unnecessary scripts.
- Clean the database after taking a backup.
- Measure again, and compare mobile numbers in particular.
Speed and search
Page experience is one of the fundamentals Google lists for Search, including for its AI features. A fast site won’t rank on speed alone if the content isn’t helpful, but a slow one makes it harder for good content to get the attention it deserves. Speed also matters for conversions: visitors who wait too long for a checkout page often don’t come back.
If you’re adding new capabilities to your site, keep speed in mind from the start. Our guide to AI in WordPress 7.0 covers the new features arriving in WordPress, and every new plugin or integration is worth measuring before and after.
Frequently asked questions
Which caching plugin is the best?
The best one is the one that suits your host. If your host already provides server caching, adding another caching plugin can cause conflicts. Start by asking your host what they offer.
Do I need to replace my theme to get a fast site?
Not always. Many sites get much faster from fonts, images, caching and fewer scripts alone. If the theme itself loads a lot of unused code on every page, though, rebuilding with a lighter theme can be worth it.
How long until Search Console shows improvement?
The Core Web Vitals report is based on real user data collected over a period of time, so improvements show up gradually, not the same day.
Do I need a CDN if all my visitors are in one country?
It still helps, because it takes load off your server and serves static files from the nearest available location. Just make sure its settings don’t conflict with your site’s caching or with dynamic store pages.
Will installing more than one speed plugin make my site faster?
Usually the opposite. Two caching or file optimization plugins can clash and leave you with broken or slower pages. You’re better off with one well configured caching plugin, testing the site after each change and checking the result in PageSpeed Insights before adding any new tool.
A final word
Speeding up an Arabic WordPress site isn’t about one magic plugin. It’s a series of sensible decisions: good hosting, caching, careful fonts, light images and fewer scripts. Take them one at a time and measure after each step. If you’d like a site built for speed from day one, or a professional review of an existing one, take a look at our WordPress Development service or book a free consultation.
