lbs.edu.ng website review

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

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

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

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

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

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

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

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

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

8 third-party services load with your homepage (Google CDN, Facebook and Google Tag Manager and others), adding 1.4 MB and 707 ms of main-thread time.

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

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

Facebook costs a phone 212 ms of main-thread work and 315 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.

33 KiB could be saved by minifying JavaScript.

15 KiB could be saved by minifying CSS.

Polyfills for old browsers add 54 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.

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

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

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

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

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

Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text ““Dear Alumni, Partners and Stakeholders, As we step into 20…”.

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

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

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

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

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

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

Your homepage downloads 6.3 MB in 200 requests on a phone: images 2.5 MB (41), scripts 1.9 MB (71) and stylesheets 791 KiB (63). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example MINDS-Scholarship-At-Lagos-Business-School.jpg at 1,080 px wide, shown at 326 px. Resized copies would save about 116 KiB.

5 images (423 KiB) 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.

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

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

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

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

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

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

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.

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

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

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

539 links have no real href, so search engines can't follow them.

Your title is only 28 characters: “Home - Lagos Business School”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“About LBS” and “Faculty and Research”). One clear main headline is easier for people and search engines.

Your meta description is 272 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 1,283 pages on lbs.edu.ng and 46 external pages.

There is no https://www.lbs.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://www.lbs.edu.ng/partnership-membership, https://www.lbs.edu.ng/faqs-2, https://www.lbs.edu.ng/contact, https://www.lbs.edu.ng/who-we-are, https://www.lbs.edu.ng/the-school and https://www.lbs.edu.ng/our-people and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lbs.edu.ng/mba-document-request has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.lbs.edu.ng/faqs-2, https://www.lbs.edu.ng/contact, https://www.lbs.edu.ng/about-lbs, https://www.lbs.edu.ng/our-people, https://www.lbs.edu.ng/careers-at-lbs and https://www.lbs.edu.ng/executive-education/executive-programmes and 2 others took over 3 s to send their HTML from our server.

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

5 errors were logged to the browser console while the page loaded, for example “Creating a worker from 'blob:https://www.lbs.edu.ng/6255ae7b-5f3f-432a-a7a1-8ec03aa32df4' violates the following Conten…”.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Content security policy”).

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 10,157 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.