kaplan.com.sg website review

About 621 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

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

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

Google Tag Manager costs a phone 1.0 s of main-thread work and 758 KiB 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.

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.3 MB and 1.7 s of main-thread time.

1 image could be 564 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

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

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

Your largest element takes 16.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Odeon 333 Homepage Banner v1”.

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

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

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

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

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

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

The first text or image appears after 1.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-24, real Chrome visitors' tap response (inp) went from 179 ms to 212 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Odeon 333 Homepage Banner v1.png weighs 598 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.1 MB in 195 requests on a phone: scripts 1.6 MB (84), images 1.3 MB (30) and stylesheets 81 KiB (51). Under 2 MB keeps phones on slow connections fast.

2 images (61 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.

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

There are 3 <h1> headlines (“”, “Where do you see yourself in the future?” and “STUDY WITH KAPLAN AND OUR RENOWNED PARTNERS”). One clear main headline is easier for people and search engines.

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

Structured data found ((untyped) and EducationalOrganization) but with 2 problems, for example “block has no @type”.

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

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

The homepage links to 192 pages on kaplan.com.sg and 8 external pages.

There is no https://www.kaplan.com.sg/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.kaplan.com.sg/academic-levels/diplomas-courses/part-time has no meta description, so Google writes the search snippet from whatever text it finds.

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

4 of 13 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 “Failed to load resource: the server responded with a status of 404 ()”.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 1,145 words of visible text.

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