Each country's lens: Chrome data by Arab country
How do visitors in nine Arab countries experience your site's speed? Real Chrome data.
- Checks your page
- Reads:Other services
- 1 rule
- Last updated
What we keep
The result appears here
Enter your page’s address and press “Check the page”. This is what the tool runs on it:
- Visitors' experience in some countries is below the marknot started
What it checks
- LCP, INP and CLS for your visitors' phones in Saudi Arabia, the UAE, Egypt, Kuwait, Qatar, Bahrain, Oman, Jordan and Morocco.
- The share of good visits (LCP up to 2.5 s, INP up to 200 ms, CLS up to 0.1) for the latest month whose tables are published.
- The origin's popularity rank in each country.
- From the Chrome UX Report tables in BigQuery, because the usual CrUX API has no country dimension.
- It runs when the server's operator has put in a service account and a project to pay for the query; without them it says it is off.
Example
<p>يبطؤ موقعنا عند الزوار في بعض الدول.</p>
<p>يسرع موقعنا عند الزوار في كل الدول.</p>
How to fix
- Start with the worst country and test the page on a network and phone like theirs.
- Bring your server closer to your visitors with a CDN that has points of presence in the region.
- Cut the size of images, fonts and scripts, and fix the dimensions of images and ads.
- See the «Core Web Vitals» check for the detail of each metric.
<img src="hero.jpg" width="800" height="450" alt="منتجاتنا" fetchpriority="high" />FAQ
Because it gives the page's or the origin's figures for the whole world and does not separate countries. Your site may be fast for most visitors and slow in one country, and the difference is lost in the average.
The server's operator pays Google Cloud, not you. The query reads nine countries' tables for one month, and before it we run a free dry run that tells us how much it would read, and we do not run it if that is over the cap (20 GB by default); BigQuery itself refuses to bill more than the cap. The bytes BigQuery really billed show on the result; and the result is kept for a day so the query is not repeated.
Because a country's CrUX table includes the origins that have enough visits from Chrome users there. An origin with few visitors in a country does not appear.
What this tool runs
- Visitors' experience in some countries is below the markminor
crux-country-gaps
How we measure
We query by origin (the domain with its protocol) for the phone histograms of LCP, INP and CLS in chrome-ux-report.country_<cc>.<yyyymm> for the nine countries, for the latest month whose tables exist, compute the share of density in the bins that end at or under the good threshold, and ask the popularity rank in a second query. The queries use named parameters and a maximumBytesBilled limit, and are preceded by a dry run.