geniebook.com website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Other Google APIs/SDKs and others), adding 1.4 MB and 1.2 s of main-thread time.

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

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

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

Google CDN costs a phone 285 ms of main-thread work and 734 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 50 ms).

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 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Ask an expert on WhatsApp”.

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

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

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

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

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

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

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

Your homepage downloads 2.3 MB in 90 requests on a phone: scripts 1.2 MB (17), other files 598 KiB (35) and fonts 302 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.

Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is 73 characters, so Google will cut it off around 60: “Personalised Learning for Primary, Secondary and JC Students | Geniebook.”.

Structured data found (EducationalOrganization, FAQPage, Service and SoftwareApplication) but with 4 problems, for example “SoftwareApplication: no offers (price) block”.

The homepage links to 509 pages on geniebook.com and 23 external pages.

https://geniebook.com/programmes/psle-preparation-programme and https://geniebook.com/geniebook-personalised-learning are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://geniebook.com/programmes/geniebook-campus, https://geniebook.com/programmes/psle-preparation-programme and https://geniebook.com/geniebook-personalised-learning use the same meta description. A description written for each page earns more clicks.

https://geniebook.com/programmes/jc-online-programme and https://geniebook.com/blog have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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 6,077 words of visible text.

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