sun.edu.ng website review

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

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

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

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

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

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

About 267 KiB of JavaScript is downloaded but never used on this page.

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

4 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google/Doubleclick Ads and others), adding 324 KiB and 268 ms of main-thread time.

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

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

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.

1 file is served with short cache lifetimes, so returning visitors download them again (4 KiB).

3 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 33.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Skyline University Nigeria is the first private tertiary in…”.

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

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

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

6 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 178 ms to 172 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.5 MB in 144 requests on a phone: images 12.0 MB (22), scripts 740 KiB (49) and fonts 524 KiB (8). Under 2 MB keeps phones on slow connections fast.

3 images weigh 5.1 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 IMG_0118.jpg at 2,048 px wide, shown at 330 px. Resized copies would save about 3.5 MB.

11 images (6.1 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.

7 images further down the page (5.8 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 3.83 g of CO₂e: 459.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

[role="img"] and [role="image"] elements must have alternative text: 27 elements on the page fail this check, rated serious by axe-core.

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.

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

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

No Open Graph image, 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.

The homepage links to 101 pages on sun.edu.ng and 16 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://sun.edu.ng/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://sun.edu.ng/tuition, https://sun.edu.ng/librarians-message and https://sun.edu.ng/news-knowledgebase have no <h1> headline, so visitors and search engines get no clear main topic.

https://sun.edu.ng/tuition, https://sun.edu.ng/sun-newsline, https://sun.edu.ng/library, https://sun.edu.ng/librarians-message, https://sun.edu.ng/circulation-terms and https://sun.edu.ng/general-rules-of-the-library and 4 others took over 3 s to send their HTML from our server.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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