squ.edu.om website review

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

About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.1 s faster on a phone.

Esri ArcGIS costs a phone 3.0 s of main-thread work and 3.0 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.

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

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

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

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

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

19 images could be 6.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

8 third-party services load with your homepage (Esri ArcGIS, Google CDN and Google Tag Manager and others), adding 4.7 MB and 4.4 s of main-thread time.

The HTML itself could arrive about 950 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 931 ms on a phone.

Google CDN costs a phone 560 ms of main-thread work and 801 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.

Google Tag Manager costs a phone 351 ms of main-thread work and 365 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.

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

Your server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

8 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.

3 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Your largest element takes 20.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SQU Web Site”.

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

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

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

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

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

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

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

Your homepage downloads 27.1 MB in 285 requests on a phone: images 21.2 MB (80), scripts 3.3 MB (69) and other files 1.4 MB (106). Under 2 MB keeps phones on slow connections fast.

7 images weigh 7.6 MB together. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example meet7262.jpg at 1,180 px wide, shown at 170 px. Resized copies would save about 929 KiB.

18 images (9.4 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.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

All page content should be contained by landmarks: 14 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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

4 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.

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

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

Your title is only 24 characters: “Sultan Qaboos University”. 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 24 characters: “Sultan Qaboos University”. 70 to 160 characters is enough to sell the click.

There are 4 <h1> headlines (““ We are proud of this university; and more than …”, ““ We want this to be a world-class university ”” and “"Education the Power of Excellence"”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 175 pages on squ.edu.om and 14 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 /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.

/About/Facts-and-Figures/Philosophy-of-Education, /About/Facts-and-Figures/Institutional-Accreditation, /About/Facts-and-Figures/Annual-Report, /About/University-Administration/Councils-and-Committees, /About/University-Administration/Vice-Chancellor/Advisors and /About/University-Administration/Vice-Chancellor/Former-Vice-Chancellors have no meta description, so Google writes the search snippet from whatever text it finds.

/About/Facts-and-Figures/Statistical-Overview, /About/Facts-and-Figures/Philosophy-of-Education, /About/Facts-and-Figures/Institutional-Accreditation, /About/Facts-and-Figures/Annual-Report, /About/University-Administration/Vice-Chancellor and /About/University-Administration/Vice-Chancellor/Advisors and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

/About, /About/Facts-and-Figures/Statistical-Overview, /About/Facts-and-Figures/Philosophy-of-Education, /About/Facts-and-Figures/Institutional-Accreditation, /About/Facts-and-Figures/Annual-Report and /About/University-Administration/Councils-and-Committees took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 92 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.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

The homepage carries about 718 words of visible text.

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 7 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 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.