A prospective student is comparing universities on her phone. She taps your link and waits. If your homepage is typical, she waits 19.6 seconds for the main content to appear.
Long before that, she has gone back to the search results and opened the next name on her list.
That is what we found when we measured 194 Indian universities again in September 2026, 90 private and 104 deemed. We ran Google’s Lighthouse audit on each homepage as a phone loads it. Google’s target for main content is 2.5 seconds, and only 1 of the 189 homepages we could measure met it.
Students do not see a score. They see a blank screen, then a page that jumps as it loads, then the back button.
Lighthouse checks four things. The first chart puts the median of each on one scale. The second counts how many homepages fall in each performance band.
The speed crisis hiding behind good scores
How far behind is speed? Lighthouse medians, 0 to 100
How many homepages are slow? Performance score bands
Three of four Lighthouse scores check how a site is built. Performance measures what a student feels on a phone.
The Number That Should Worry You
Lighthouse gives four scores. Three check whether a site is built correctly: whether search engines can read it, whether it meets accessibility standards, and whether it follows current web practice. The fourth, performance, measures what a student feels when she taps your link on a 4G connection between classes.
University homepages do well on the first three. The median scores are 85 for SEO, 81 for accessibility and 75 for best practices. The median performance score is 51.
88 of 189 homepages (46.6%) score under 50, which Lighthouse calls poor. Universities have invested in being found. They have not invested in what happens after a student arrives.
Moving from 45 to 75 on performance removes a real barrier between a student’s interest and her application.
Why University Websites Are Slow
Our study did not measure causes. It did record what each of the 194 homepages is built on, and three patterns stand out.
Three patterns in what 194 university homepages are built on
If we found no CDN on your homepage and it scores under 50 on a phone, start with the CDN.
No Content Delivery Network (CDN)
We detected a content delivery network (CDN) on 102 of 194 homepages. A CDN keeps copies of your site on servers in many cities, so each student loads it from one nearby. On the other 92, our detector found none.
Universities draw students from across India, from Tamil Nadu to Punjab and from Rajasthan to the Northeast. Without a CDN, a student in Chennai and a student in Chandigarh load the same page at different speeds.
A CDN is the cheapest infrastructure fix available. Free tiers cover most university traffic, and setup takes days, not months.
Your Platform Decides How Fast You Can Fix It
WordPress runs 69 of the 194 homepages. For those universities, caching, image compression and a CDN are plugin settings, work measured in days.
On 117 homepages our detector could not name a content management system. That does not mean the site is custom-built. But changes on those sites usually need a developer.
Heavy Images and Unoptimised Pages
We detected a modern JavaScript framework, such as React, Vue.js or Angular, on 15 of 194 homepages. A framework is not a speed fix on its own, and a rebuild is rarely the right first step. For most universities, the gains will come from images, caching and hosting.
University websites are image-heavy by nature: campus panoramas, event banners, faculty photos, virtual tours. Without compression and lazy loading, which fetches each image only as a student scrolls to it, these files hold the whole page back.
What Slow Actually Costs
When a student leaves a slow page, she does not stop looking. She opens the next university on her list, or an aggregator page that loads faster and already carries your fees on its own terms.
The cost is hard to see. Higher education has no cart-abandonment metric. The drop-off is silent: a student who never scrolled past the loading screen, never found the fee page, never started the application. Marketing teams read it as low interest, not slow infrastructure.
The loss compounds. Google uses Core Web Vitals, including how fast the main content appears, as a ranking signal. A slow page loses the student today and some of its search position over time.
The invisible cost of a slow website
How page speed compounds into lost applications you’ll never see
Step 1
Slow page load
Main content arrives long after Google’s 2.5-second target.
Step 2
Student leaves
No scroll, no fee check, no application.
Step 3
Lower rankings
Google uses Core Web Vitals as a ranking signal.
Step 4
Aggregators win
Their pages load fast and tell your story on their terms.
Step 5
Lost applications
No cart abandonment metric in higher ed. The drop-off is silent and permanent.
Speed improvements are deprioritised because they need technical investment with no visible marketing outcome. But speed compounds across conversions, rankings and student experience, and it is a fix most universities have not made yet.
This Is a Sector-Wide Problem
Slow homepages are not confined to one type of university. Deemed homepages have a median mobile performance score of 53.5, and private homepages 48.
Both sit near Lighthouse’s poor band, and neither is close to Google’s 2.5-second target for main content. Speed is a gap across the whole sector, and every university in it can close its own share.
The 5-Point Speed Audit Framework
Before committing to a redesign, ask your team to run this audit. It takes an hour and tells you exactly where performance is weakest.
Step 1: Test your key pages separately. Ask your team to run a performance test (using Google’s free Lighthouse tool) on your homepage AND your admissions page. They often have very different scores. The admissions page is typically heavier due to images, forms, and third-party tools embedded on it. Look at the performance score specifically, not the overall website health score.
Step 2: Check whether you have a CDN. Is your site distributed through a content delivery network? If not, this is the single highest-impact fix. Implementation can be completed in days, not months.
Step 3: Measure image weight. University websites are image-heavy. Are campus photos, banners and event images compressed and served in modern formats such as WebP? A single uncompressed campus panorama can add several megabytes to a page.
Step 4: Count the third-party tools on each page. Chat widgets, analytics tags, social embeds and marketing pixels each add to load time. Individually they seem small. Collectively, they can add seconds before a student can interact with your page.
Step 5: Benchmark against peers. Compare your score with the cohort median in our Technical Report and with your three closest competitors. A 55 means something different if they score 70 than if they score 45.
The 5-Point Speed Audit
A prioritised checklist for university marketing and IT teams: it takes about an hour
Step 1 · Start here
Run Lighthouse Performance Separately
Not the overall score. Run Performance only on your homepage AND admissions page. They often have very different scores.
Step 2 · Quick win
Check CDN Status
Is your site served through Cloudflare, AWS CloudFront, or another CDN? If not, this is the single highest-impact fix.
Step 3 · High impact
Measure Image Payload
Are images compressed and in modern formats (WebP, AVIF)? A single uncompressed campus panorama adds several megabytes to a page.
Step 4 · Technical
Audit Render-Blocking Resources
Count CSS and JS files that load before interactivity. Chat widgets, analytics and social embeds each add milliseconds. Collectively, seconds.
Step 5 · Context
Benchmark Against Peers
A score of 55 means something different if competitors score 70 or 45. Compare against the cohort median in our Technical Report.
A prioritised fix list ranked by impact and implementation difficulty. In the order to do them.
Takes about an hour. Tells you where your performance score is bleeding and what to fix first.
What It Takes to Reach the Top Band
Only one of the 189 homepages we measured scored 90 or above. The tenth fastest scored 74. A fast homepage needs four things, and none of them is rare:
- They serve every page through a CDN, as foundation, not afterthought.
- They compress images, use modern formats and load each image only when a student scrolls to it.
- They keep third-party scripts to a minimum: fewer chat widgets, analytics tags and social embeds.
- They measure. You cannot show that a speed fix worked without analytics on the page.
None of this needs a redesign. These are decisions about how a site is built and maintained, and every university in the study can make them.
What University Leaders Should Do Next
Slow homepages are common across the sector, they have causes you can name, and they cost enquiries you never see. The fix does not need a redesign. A CDN, compressed images and fewer third-party scripts on key pages are infrastructure work, not a change of strategy.
That work needs marketing and IT to agree on one point. Website speed is a marketing metric. It decides whether a student reaches your fee page, your programmes and your application form.
The universities that fix this first gain a quiet advantage in admissions. Their sites will not be flashier. Their pages will load before a student’s patience runs out.
This is Part 2 of a 12-part series based on Thrivemattic’s 194-university study (September 2026 snapshot, v2). For the full findings, see the research overview. For detailed speed and stack data, see the Technical Report.
For your own university’s view, see Find Your University’s Digital Ranking. It gives each university a four-part grade: Google search, AI visibility, technical health and admission pages.
How fast is your university’s homepage on a phone?
Speed, Google search, AI answers, admission pages and Reddit across the 194 universities in our study.
Read the full studyLook up your university and compare it with its peers in the study.
Find your university’s ranking See how we work with universities
