pnu.edu.sa website review

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

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

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

Your mobile performance score is 63 (desktop: 84). Pages that score under 90 lose visitors before the first paint.

About 125 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 610 ms faster on a phone.

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

2 images could be 323 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

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

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

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

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

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

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

3 third-party services load with your homepage (Clarity, muneer.cx and Google Fonts), adding 51 KiB and 103 ms of main-thread time.

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 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your largest element takes 5.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “الخدمات الرقمية في جامعة الأميرة نورة”. Most of its time is resource load delay (4.8 s).

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

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

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

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

2 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-17, real Chrome visitors' tap response (inp) went from 108 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

1 image further down the page (357 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

1 image (357 KiB) is 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 0.56 g of CO₂e: 67.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

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

The homepage links to 152 pages on pnu.edu.sa and 43 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://pnu.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.

https://pnu.edu.sa/ar/Pages/Home.aspx and https://pnu.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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://pnu.edu.sa/ar, whose canonical is https://pnu.edu.sa/ar/Pages/Home.aspx. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://pnu.edu.sa/ar, https://pnu.edu.sa/ar/AboutUniversity/Pages/AboutLinks.aspx, https://pnu.edu.sa/ar/AboutUniversity/Pages/UniversityCouncil1.aspx, https://pnu.edu.sa/ar/AboutUniversity/Pages/OrganizationStructure1.aspx, https://pnu.edu.sa/ar/AboutUniversity/Pages/PNUinNumbers.aspx and https://pnu.edu.sa/ar/AboutUniversity/Pages/PresidentMessage.aspx and 6 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://pnu.edu.sa/ar/Centers/Pages/AllCenters.aspx, https://pnu.edu.sa/ar/MediaCenter/Pages/About.aspx and https://pnu.edu.sa/ar/MediaCenter/Pages/Mediafiles.aspx took over 3 s to send their HTML from our server.

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

26 of 67 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Muneer: not loading because the subscription for this widget is not active. Contact Muneer support to resolve it.”.

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.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 39 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 Microsoft Clarity (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 3 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.