qu.edu.qa website review

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

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

About 967 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.5 s faster on a phone.

About 196 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

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

6 third-party services load with your homepage (ContentSquare, Google Tag Manager and ally.ac and others), adding 610 KiB and 699 ms of main-thread time.

Polyfills for old browsers add 121 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.

ContentSquare costs a phone 576 ms of main-thread work and 168 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.

88 KiB could be saved by minifying JavaScript.

45 KiB could be saved by minifying CSS.

The page has 2,316 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

14 long tasks block the main thread while loading, the longest for 122 ms. During a long task the page ignores taps.

4 files are served with short cache lifetimes, so returning visitors download them again (45 KiB).

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 wait 7.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.40 (75th percentile). Good is under 0.1.

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

Real visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

The layout shifts by 0.378 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 295 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

30 images have no width and height attributes, so the layout jumps as each one loads.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 137 ms to 141 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 4.3 s to 4.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 27.9 MB in 177 requests on a phone: images 24.1 MB (47), scripts 2.2 MB (49) and other files 665 KiB (25). Under 2 MB keeps phones on slow connections fast.

10 images weigh 20.5 MB together. On a phone connection a single image that size takes seconds.

15 images are downloaded at several times the size a phone draws them, for example 3265_0_cam_research.jpg at 4,592 px wide, shown at 310 px. Resized copies would save about 15.5 MB.

30 images (23.8 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

24 images further down the page (15.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

22 buttons have no accessible name, so screen readers announce just “button”.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.

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 on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 8 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.

Your meta description is only 13 characters: “جامعة قطر: QU”. 70 to 160 characters is enough to sell the click.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.qu.edu.qa/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 208 pages on qu.edu.qa and 1 external page.

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.qu.edu.qa/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.

https://www.qu.edu.qa/ar/about/Pages/default.aspx, https://www.qu.edu.qa/ar/about/Pages/President-Message.aspx, https://www.qu.edu.qa/ar/about/Pages/mission-and-vision.aspx, https://www.qu.edu.qa/ar/about/Pages/Organization-Structure.aspx, https://www.qu.edu.qa/ar/about/leadership/Pages/default.aspx and https://www.qu.edu.qa/ar/about/Pages/qu-timeline.aspx and 8 others use the same meta description. A description written for each page earns more clicks.

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

https://www.qu.edu.qa/ar/about/Pages/Events.aspx and https://www.qu.edu.qa/ar/about/Pages/newsroom.aspx have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.qu.edu.qa/ar/about/Pages/default.aspx, https://www.qu.edu.qa/ar/about/Pages/President-Message.aspx, https://www.qu.edu.qa/ar/about/Pages/mission-and-vision.aspx, https://www.qu.edu.qa/ar/about/Pages/Organization-Structure.aspx, https://www.qu.edu.qa/ar/about/leadership/Pages/default.aspx and https://www.qu.edu.qa/ar/about/Pages/qu-timeline.aspx and 8 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.

https://www.qu.edu.qa/ar/about/Pages/default.aspx, https://www.qu.edu.qa/ar/about/Pages/President-Message.aspx, https://www.qu.edu.qa/ar/about/Pages/mission-and-vision.aspx, https://www.qu.edu.qa/ar/about/Pages/Organization-Structure.aspx, https://www.qu.edu.qa/ar/about/leadership/Pages/default.aspx and https://www.qu.edu.qa/ar/about/Pages/qu-timeline.aspx and 4 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 176 found) and read each the way a search engine does.

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'toLowerCase')”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 102 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and 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.

Opening the homepage sets 8 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.