unisel.edu.my website review

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

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

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

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

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

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

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

About 291 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.

Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

4 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google Fonts and others), adding 1.1 MB and 487 ms of main-thread time.

YouTube costs a phone 477 ms of main-thread work and 991 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.

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

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

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

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

15 KiB could be saved by minifying CSS.

15 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Advance Your Academic Journey with Our Undergraduate and Po…”. Most of its time is element render delay (5.6 s).

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

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

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

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

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

Your homepage downloads 6.8 MB in 126 requests on a phone: images 4.3 MB (34), scripts 1.6 MB (37) and fonts 453 KiB (9). Under 2 MB keeps phones on slow connections fast.

10 images (1.2 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.

5 images further down the page (447 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example 128-BADGE-QS-WORLD-UNIVERSITT-RANKING-ASIA-2026-1.png at 400 px wide, shown at 57 px. Resized copies would save about 45 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 1.92 g of CO₂e: 231.0 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.

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

Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.

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

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

Some list items are not inside a list.

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.

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.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

1 element hidden from screen readers can still receive keyboard focus.

Headings skip levels (h2 → h6, h2 → h6 and h2 → h6), 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 28 characters: “UNISEL | Universiti Selangor”. 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 33 characters: “UNISEL | LEADER OF TRANSFORMATION”. 70 to 160 characters is enough to sell the click.

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

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

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

The homepage links to 233 pages on unisel.edu.my and 75 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://unisel.edu.my/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://unisel.edu.my/about-universiti-selangor, https://unisel.edu.my/about-universiti-selangor/https://unisel.edu.my/vision-mission, https://unisel.edu.my/about-universiti-selangor/https://unisel.edu.my/word_from_president, https://unisel.edu.my/our-management, https://unisel.edu.my/open-policies and https://unisel.edu.my/admission and 8 others 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://unisel.edu.my/about-universiti-selangor/https://unisel.edu.my/vision-mission, whose canonical is https://unisel.edu.my/vision-mission. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://unisel.edu.my/about-universiti-selangor/https://unisel.edu.my/vision-mission and https://unisel.edu.my/about-universiti-selangor/https://unisel.edu.my/word_from_president took over 3 s to send their HTML from our server.

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

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

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

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

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

There is no form on the homepage, so every lead has to click through to another page first.

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 684 words of visible text.

Before a visitor clicks anything, the page loads Google Ads (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, 1 of them by other companies (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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.