Website review, no card needed
saia.gov.sa website review
Visit site (opens in a new tab)Reviewed 18 October 202639 issues · 87 checks
This review found 39 issues worth fixing on saia.gov.sa, 15 of them high impact, across 87 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 5.0 s |
| May 2, 2026 | 5.3 s |
| May 9, 2026 | 5.2 s |
| May 16, 2026 | 5.2 s |
| May 23, 2026 | 4.9 s |
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.7 s |
| Jun 13, 2026 | 4.7 s |
| Jun 20, 2026 | 4.7 s |
| Jun 27, 2026 | 4.5 s |
| Jul 4, 2026 | 4.5 s |
| Jul 11, 2026 | 4.5 s |
| Jul 18, 2026 | 4.5 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.5 s |
| Aug 8, 2026 | 4.3 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 4.4 s |
| Sep 5, 2026 | 4.6 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 130 ms |
| May 2, 2026 | 136 ms |
| May 9, 2026 | 129 ms |
| May 16, 2026 | 122 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 111 ms |
| Jun 13, 2026 | 109 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 120 ms |
| Jul 4, 2026 | 122 ms |
| Jul 11, 2026 | 118 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 126 ms |
| Aug 1, 2026 | 124 ms |
| Aug 8, 2026 | 115 ms |
| Aug 15, 2026 | 105 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 98 ms |
| Sep 5, 2026 | 98 ms |
| Sep 12, 2026 | 97 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 94 ms |
| Oct 3, 2026 | 94 ms |
| Oct 10, 2026 | 92 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Render-blocking requests
6.1 s41 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.1 s.
Reduce unused JavaScript
1.4 s · 387 KiBAbout 387 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42 (desktop: 65). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
2.8 MB39 files are served with short cache lifetimes, so returning visitors download them again (2.8 MB).
Improve image delivery
1.8 MB23 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Twitter Online Conversion Tracking and others), adding 4.1 MB and 223 ms of main-thread time.
Reduce unused CSS
300 ms · 66 KiBAbout 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
customer-oci.com adds 0 ms
0 mscustomer-oci.com costs a phone 0 ms of main-thread work and 2.7 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Google Tag Manager adds 166 ms
166 msGoogle Tag Manager costs a phone 166 ms of main-thread work and 497 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
b-cdn.net adds 0 ms
0 msb-cdn.net costs a phone 0 ms of main-thread work and 511 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Minify CSS
150 ms · 13 KiB13 KiB could be saved by minifying CSS.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 61 ms. During a long task the page ignores taps.
Minify JavaScript
51 KiB51 KiB could be saved by minifying JavaScript.
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 270 ms of it running JavaScript. That is comfortably low.
Server response: 112 ms
112 msYour server sent the HTML in 112 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.8 s
11.8 sYour largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “التخطيط الاستراتيجي”.
Time to Interactive: 19.8 s
19.8 sThe page becomes fully interactive after 19.8 s. Good is under 3.8 s.
First Contentful Paint: 5.6 s
5.6 sThe first text or image appears after 5.6 s on a phone. Good is under 1.8 s.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.292
0.292The layout shifts by 0.292 while loading, so content jumps under the reader's thumb. Good is under 0.1.
25 images without width and height
25 images have no width and height attributes, so the layout jumps as each one loads.
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 71 ms
71 msReal visitors wait 71 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 553 ms
553 msReal visitors wait 553 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 30% faster for real visitors
-30%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 130 ms to 92 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 60% faster for real visitors
-60%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 5.0 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 7 ms
7 msScripts block the page for only 7 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.1 MB in 219 requests
4.1 MBYour homepage downloads 4.1 MB in 219 requests on a phone: images 2.8 MB (44), scripts 885 KiB (35) and fonts 331 KiB (9). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.17 g of CO₂e: 140.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 37 images in the HTML carry an alt attribute.
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (20 characters)
Your title is only 20 characters: “أهلاً وسهلاً! | SAIA”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://saia.gov.sa/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
92 internal links, 7 external
The homepage links to 92 pages on saia.gov.sa and 7 external pages.
1 checks passed
robots.txt in place
robots.txt is in place.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://saia.gov.sa/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
15 pages without a meta description
https://saia.gov.sa/ar/node/9, https://saia.gov.sa/ar/pages/board-directors, https://saia.gov.sa/ar/pages/courses-and-training, https://saia.gov.sa/ar/node/42, https://saia.gov.sa/ar/node/83 and https://saia.gov.sa/ar/pages/strategic-planning and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages with very little text
https://saia.gov.sa/ar/node/9, https://saia.gov.sa/ar/pages/board-directors, https://saia.gov.sa/ar/pages/courses-and-training, https://saia.gov.sa/ar/node/42, https://saia.gov.sa/ar/node/83 and https://saia.gov.sa/ar/pages/strategic-planning and 9 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
2 checks passed
Tap targets are thumb-sized
15 of 18 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Only about 26 words
The homepage has only about 26 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
4 checks passed
Social proof on the page
Social proof on the homepage: 16 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and X (Twitter) Ads (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at saia.gov.sa, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Drupal
- Framework
- jQuery
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on saia.gov.sa, including 16 speed issues, 7 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.