radcliffe.in website review

20 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 8.3 s faster on a phone.

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

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

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

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

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

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

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

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

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

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

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

Polyfills for old browsers add 13 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 see the first content after 3.2 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 37.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Radcliffe School Admission Open AY 2027-28”.

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

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

The layout shifts by 0.416 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 206 ms to 237 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.4 MB in 254 requests on a phone: images 6.0 MB (48), scripts 1.3 MB (74) and fonts 794 KiB (9). Under 2 MB keeps phones on slow connections fast.

4 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.

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

1 image is downloaded at several times the size a phone draws it, for example Radcliffe-School-Admission-Open-AY-2027-28-Mobile.jpeg at 1,380 px wide, shown at 390 px. Resized copies would save about 270 KiB.

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

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (4 elements).

1 visible link has no text or label, so screen readers cannot say where it goes.

Elements with role="none" or role="presentation" have conflicts (26 elements).

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

There are 2 <h1> headlines (“radcliffe-school” and “Best CBSE School in India - Radcliffe School”). One clear main headline is easier for people and search engines.

Structured data found (Article, EducationalOrganization, ImageObject and LocalBusiness) but with 1 problem, for example “Article: missing datePublished”.

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

The homepage links to 111 pages on radcliffe.in and 5 external pages.

Your homepage links to https://www.radcliffe.in/radcliffe-school-kharghar-grade-10-toppers-cbse-2025, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.radcliffe.in/careers, https://www.radcliffe.in/contact-us, https://www.radcliffe.in/admission-process, https://www.radcliffe.in/inspiring-academic-excellence, https://www.radcliffe.in/learn-from-finest-teachers and https://www.radcliffe.in/enrichment-through-extracurricular and 3 others took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97214899&Ver=2&mid=4dda3ee0-1ea7-430a-9158-2b0089d84aa5&bo=1&sid=12300d90d6e011f1b42edd59f58ef6eb&vid=123017e0d6e011f19defc11c8e4b073f&vids=1&msclkid=N&pi=918639831&lg.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: “20,000+ students”. 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.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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