Website review, no card needed
uoh.edu.sa website review
Visit site (opens in a new tab)Reviewed 20 November 202635 issues · 81 checks
This review found 35 issues worth fixing on uoh.edu.sa, 10 of them high impact, across 81 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 5.9 s |
| Jun 6, 2026 | 6.1 s |
| Jun 13, 2026 | 6.1 s |
| Jun 20, 2026 | 5.9 s |
| Jun 27, 2026 | 5.8 s |
| Jul 4, 2026 | 5.9 s |
| Jul 11, 2026 | 6.1 s |
| Jul 18, 2026 | 6.5 s |
| Jul 25, 2026 | 7.1 s |
| Aug 1, 2026 | 7.0 s |
| Aug 8, 2026 | 6.8 s |
| Aug 15, 2026 | 6.3 s |
| Aug 22, 2026 | 5.9 s |
| Aug 29, 2026 | 5.7 s |
| Sep 5, 2026 | 5.5 s |
| Sep 12, 2026 | 5.5 s |
| Sep 19, 2026 | 5.5 s |
| Sep 26, 2026 | 5.6 s |
| Oct 3, 2026 | 5.8 s |
| Oct 10, 2026 | 5.5 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 4.1 s |
| Oct 31, 2026 | 2.8 s |
| Nov 7, 2026 | 2.4 s |
| Nov 14, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 122 ms |
| Jun 6, 2026 | 122 ms |
| Jun 13, 2026 | 115 ms |
| Jun 20, 2026 | 118 ms |
| Jun 27, 2026 | 119 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 115 ms |
| Jul 25, 2026 | 117 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 114 ms |
| Aug 15, 2026 | 112 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 116 ms |
| Sep 5, 2026 | 116 ms |
| Sep 12, 2026 | 115 ms |
| Sep 19, 2026 | 115 ms |
| Sep 26, 2026 | 115 ms |
| Oct 3, 2026 | 115 ms |
| Oct 10, 2026 | 118 ms |
| Oct 17, 2026 | 116 ms |
| Oct 24, 2026 | 112 ms |
| Oct 31, 2026 | 110 ms |
| Nov 7, 2026 | 105 ms |
| Nov 14, 2026 | 105 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
2.0 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
Reduce unused CSS
900 ms · 148 KiBAbout 148 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
258 KiB16 images could be 258 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2,259 HTML elements
The page has 2,259 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
150 ms · 3 KiB3 KiB could be saved by minifying CSS.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 113 ms. During a long task the page ignores taps.
Reduce unused JavaScript
112 KiBAbout 112 KiB of JavaScript is downloaded but never used on this page.
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.
1 third-party service on the page
1 third-party service load with your homepage (userway.org), adding 3 KiB and 0 ms of main-thread time.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 231 ms of it running JavaScript. That is comfortably low.
Server response: 544 ms
544 msYour server sent the HTML in 544 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 4.9 s
4.9 sYour largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “بانر”.
Time to Interactive: 7.3 s
7.3 sThe page becomes fully interactive after 7.3 s. Good is under 3.8 s.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Real-user TTFB: 916 ms
916 msReal visitors wait 916 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.22
0.22The layout shifts by 0.22 while loading, so content jumps under the reader's thumb. Good is under 0.1.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 88 ms
88 msReal visitors wait 88 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 122 ms to 105 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-11-14, real Chrome visitors' largest content (lcp) went from 5.9 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 32 ms
32 msScripts block the page for only 32 ms while loading. Good is under 200 ms.
Images and page weight
An image on the first screen is lazy-loaded
STD03.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
3 images far larger than shown
215 KiB3 images are downloaded at several times the size a phone draws them, for example STD03.webp at 2,172 px wide, shown at 390 px. Resized copies would save about 215 KiB.
About 0.4 g of CO₂ per visit
0.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.42 g of CO₂e: 50.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.5 MB in 77 requests
1.5 MBYour homepage downloads 1.5 MB in 77 requests on a phone: images 758 KiB (65), fonts 303 KiB (4) and stylesheets 187 KiB (5). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 131 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (19 characters)
Your title is only 19 characters: “الرئيسية جامعة حائل”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (61 characters)
Your meta description is only 61 characters: “جامعة حائل هي مؤسسة تعليمية رائدة في المملكة العربية السعودية”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
140 internal links, 31 external
The homepage links to 140 pages on uoh.edu.sa and 31 external pages.
5 checks passed
One H1 headline
Your main headline reads: “جامعة حائل”.
Canonical URL set
The canonical URL is https://www.uoh.edu.sa/.
Structured data in place
Structured data found: EducationalOrganization.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.uoh.edu.sa/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.uoh.edu.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
1 linked page is broken
Your homepage links to https://www.uoh.edu.sa/_trust, which answers with an error. Visitors hit a dead end and search engines drop it.
2 pages point its canonical at the homepage
https://www.uoh.edu.sa/ar/Pages/ServicesList.aspx and https://www.uoh.edu.sa/Ar declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.uoh.edu.sa/Ar all use the title “الرئيسية جامعة حائل”. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages share a meta description
https://www.uoh.edu.sa/ar/Pages/ServicesList.aspx and https://www.uoh.edu.sa/Ar use the same meta description. A description written for each page earns more clicks.
10 pages with very little text
https://www.uoh.edu.sa/ar/Pages/ServicesList.aspx, https://www.uoh.edu.sa/Ar, https://www.uoh.edu.sa/Ar/About/Pages/default.aspx, https://www.uoh.edu.sa/Ar/About/Pages/President.aspx, https://www.uoh.edu.sa/Ar/About/Pages/StrategicPlan.aspx and https://www.uoh.edu.sa/Ar/Agencies/Pages/default.aspx and 4 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.
3 pages slow to respond
https://www.uoh.edu.sa/Ar/Agencies/University-Agency-P-S-S-R/Pages/default.aspx, https://www.uoh.edu.sa/Ar/Agencies/University-Agency-A-A/Pages/default.aspx and https://www.uoh.edu.sa/Ar/Colleges/Pages/default.aspx took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 90 found) and read each the way a search engine does.
4 checks passed
Every page has a meta description
All 10 pages that loaded have a meta description.
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 10 pages that loaded have a <title>.
Best practices
21 small tap targets
21 of 67 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “RegisterSod is not defined”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
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.
Only about 68 words
The homepage has only about 68 words of visible text; thin pages give Google and first-time buyers little to go on.
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
1 short form
A short form (6 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 18 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
2 other companies contacted
Loading the homepage contacts 2 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 uoh.edu.sa, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Azure
Company
- Founded
- 2005
- Headquarters
- Ha'il
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on uoh.edu.sa, including 14 speed issues, 3 SEO issues and 3 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.