uop.edu.jo website review

22 images could be 5.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.4 s faster on a phone.

Google CDN costs a phone 10.5 s of main-thread work and 31 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

83 files are served with short cache lifetimes, so returning visitors download them again (3.7 MB).

YouTube costs a phone 3.1 s of main-thread work and 4.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

13 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.

A phone's processor spends 22.6 s on main-thread work while loading, 18.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).

Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google CDN, YouTube and Google Tag Manager and others), adding 5.3 MB and 13.9 s of main-thread time.

About 2.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

20 long tasks block the main thread while loading, the longest for 2.0 s. During a long task the page ignores taps.

About 258 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

20 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 38 KiB JavaScript that modern phones do not need.

10 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Real visitors see the first content after 4.7 s (75th percentile). Good is under 1.8 s.

Your largest element takes 23.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Petra University”.

Visually, the page fills in at 24.1 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 10.0 s in total while the page loads. Good is under 200 ms.

The page becomes fully interactive after 65.8 s. Good is under 3.8 s.

The first text or image appears after 4.1 s on a phone. Good is under 1.8 s.

Real visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 146 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 15.7 MB in 262 requests on a phone: images 9.0 MB (98), scripts 5.2 MB (47) and stylesheets 444 KiB (16). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 4.46 g of CO₂e: 535.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

30 images have no alt text, which hurts accessibility and image search.

18 links have no text or label, so screen readers cannot say where they go.

13 tap targets are too small or too close together to hit reliably with a finger.

6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

3 elements hidden from screen readers can still receive keyboard focus.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Headings skip levels (h1 → h5 and h1 → h6), which makes the page harder to scan with a screen reader.

Your title is only 12 characters: “جامعة البترا”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 6 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

There is no robots.txt at uop.edu.jo/robots.txt, the first file search crawlers ask for.

9 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 22 pages on uop.edu.jo and 18 external pages.

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.

There is no https://www.uop.edu.jo/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.

Your homepage links to https://www.uop.edu.jo/_catalogs/masterpage/indexAr.html, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.uop.edu.jo/ar/pages/default.aspx and https://www.uop.edu.jo/ar/Pages/default.aspx all use the title “جامعة البترا”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.uop.edu.jo/Ar/prospectivestudents/pages/default.aspx and https://www.uop.edu.jo/Ar/hrd/pages/default.aspx have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.uop.edu.jo/ar/Pages/default.aspx, https://www.uop.edu.jo/Ar/Pages/ContactUs.aspx and https://www.uop.edu.jo/ar/Pages/Useful-links.aspx use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://www.uop.edu.jo/ar/Pages/default.aspx, whose canonical is https://www.uop.edu.jo/Ar/Pages/default.aspx. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.uop.edu.jo/Ar/prospectivestudents/pages/default.aspx and https://www.uop.edu.jo/Ar/hrd/pages/default.aspx have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.uop.edu.jo/ar/Pages/default.aspx, https://www.uop.edu.jo/Ar/Pages/ContactUs.aspx, https://www.uop.edu.jo/Ar/prospectivestudents/pages/default.aspx, https://www.uop.edu.jo/Ar/hrd/pages/default.aspx and https://www.uop.edu.jo/ar/Pages/Useful-links.aspx 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.

https://www.uop.edu.jo/ar/Pages/default.aspx, https://www.uop.edu.jo/Ar/Pages/ContactUs.aspx, https://www.uop.edu.jo/Ar/prospectivestudents/pages/default.aspx, https://www.uop.edu.jo/Ar/hrd/pages/default.aspx and https://www.uop.edu.jo/ar/Pages/Useful-links.aspx took over 3 s to send their HTML from our server.

We fetched 8 pages linked from your homepage and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 17 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.