When a university site fails Core Web Vitals, the cause is almost never mysterious. Across the .edu audits we have run, the same seven issues account for the overwhelming majority of the damage. Here they are, ranked by how much time each one typically costs on a program page loaded on a mid-range Android phone.
1. Autoplay hero video
A looping homepage video ships 6 to 22MB before the visitor sees anything meaningful. It is the single largest LCP offender on .edu homepages. Replace it with a compressed poster image and a "watch our story" button that loads the video on click. Typical saving: 1.5 to 2.5 seconds.
2. Uncompressed hero and faculty images
Original-resolution JPEG and PNG uploads at 3 to 8MB, served at 1200px display width. Convert to WebP or AVIF, resize to actual display dimensions, and serve responsive srcsets. A 2.8MB PNG becomes a 140KB WebP with no visible difference. Typical saving: 0.8 to 2 seconds.
3. Tag manager sprawl
Google Analytics, Google Ads, Meta, LinkedIn Insight, Hotjar, a chat widget, a virtual tour embed, and two vendors nobody remembers. Audit the container, remove anything not tied to a dashboard someone reads, and load the survivors on interaction. Typical saving: 0.5 to 1.5 seconds of blocking time.
4. Multiple YouTube iframes per program page
Five to nine embedded players each pull hundreds of kilobytes before the visitor scrolls. Use a lightweight facade that loads the real player on click. Typical saving: 0.4 to 1.2 seconds.
5. Twelve theme bundles for twelve colleges
Every college with its own slightly forked stylesheet and script bundle means shared visitors download the same framework repeatedly across sub-sites. Consolidate to one design system with per-college theming variables. This is a quarter-long program, not a sprint, and it is the fix that lasts.
6. Legacy jQuery carousels and accordions below the fold
Old UI plugins that still parse and execute on load even though nobody scrolls to them. Remove the plugin, rebuild the two components you still use in native CSS and a few lines of JavaScript.
7. Under-rightsized hosting during admissions peaks
Shared or fixed-capacity hosting that groans in September when traffic runs 5 to 15 times baseline. Move to Acquia, Pantheon, or WP Engine with a CDN in front. We deploy on all three and hold Drupal certified partner and WP Engine Advanced Agency Partner status.
Which of these should we fix first?
Issues 1 through 4 are a two-week sprint that a single developer can complete, and they typically move a failing program page to passing Core Web Vitals on their own. Issues 5 through 7 are a one-quarter program that keeps it there.
How do we stop the site from slowing down again?
Set a page-weight budget per template, for example 1.2MB total and 200KB of CSS plus JavaScript for a program page, and enforce it in CI so a bad deploy fails the build. Give one named person monthly ownership of the number. Sites where performance is "everyone's job" degrade again inside a year.
Does any of this actually affect enrollment?
Yes. Google field data shows roughly a 1 percent conversion drop per 100ms above 2.5s LCP. On a program page taking 800 RFI submissions a month, moving from 2.5s to 4.5s costs about 160 inquiries monthly. Slow pages are also cited less often by AI assistants, which increasingly mediate the college search.
Where to go next
Read how to fix slow university websites in 2026, why university websites get slow and hard to manage, and 9 must-have elements of university website development. See our higher-ed work with the University of Toronto and Berklee, or book a performance audit.
Seattle, WA
A full-service digital agency working in WordPress, Drupal, Shopify, Webflow, React, and React Native. We partner with universities, governments, and growing brands to ship sites and products that hold up after launch.
