Website review, no card needed
som.yale.edu website review
Visit site (opens in a new tab)Reviewed 20 November 202630 issues · 79 checks
This review found 30 issues worth fixing on som.yale.edu, 5 of them high impact, across 79 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
77CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
| Nov 7, 2026 | 2.2 s |
| Nov 14, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 282 ms |
| Jun 6, 2026 | 269 ms |
| Jun 13, 2026 | 240 ms |
| Jun 20, 2026 | 228 ms |
| Jun 27, 2026 | 231 ms |
| Jul 4, 2026 | 226 ms |
| Jul 11, 2026 | 219 ms |
| Jul 18, 2026 | 233 ms |
| Jul 25, 2026 | 248 ms |
| Aug 1, 2026 | 260 ms |
| Aug 8, 2026 | 282 ms |
| Aug 15, 2026 | 289 ms |
| Aug 22, 2026 | 292 ms |
| Aug 29, 2026 | 299 ms |
| Sep 5, 2026 | 301 ms |
| Sep 12, 2026 | 301 ms |
| Sep 19, 2026 | 288 ms |
| Sep 26, 2026 | 264 ms |
| Oct 3, 2026 | 225 ms |
| Oct 10, 2026 | 199 ms |
| Oct 17, 2026 | 205 ms |
| Oct 24, 2026 | 205 ms |
| Oct 31, 2026 | 210 ms |
| Nov 7, 2026 | 213 ms |
| Nov 14, 2026 | 209 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Improve image delivery
2.1 s · 435 KiB7 images could be 435 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 164 KiBAbout 164 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, enzuzo.com and Adobe TypeKit and others), adding 755 KiB and 731 ms of main-thread time.
Google Tag Manager adds 642 ms
642 msGoogle Tag Manager costs a phone 642 ms of main-thread work and 542 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 296 ms. During a long task the page ignores taps.
Reduce unused JavaScript
293 KiBAbout 293 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 946 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,557 HTML elements
The page has 1,557 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
108 KiB2 files are served with short cache lifetimes, so returning visitors download them again (108 KiB).
Render-blocking requests
100 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 7.7 s
7.7 sYour largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Philippine Airlines staff during the COVID pandemic”.
Time to Interactive: 11.6 s
11.6 sThe page becomes fully interactive after 11.6 s. Good is under 3.8 s.
Real-user INP: 275 ms
275 msReal visitors wait 275 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 568 ms
568 msScripts block taps and scrolling for 568 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 282 ms to 209 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.07
0.07The layout barely moves while loading (CLS 0.07, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Speed Index: 2.3 s
2.3 sVisually, the page fills in at 2.3 s (Speed Index), inside the 3.4 s “good” threshold.
Images and page weight
Page weight: 2.2 MB in 51 requests
2.2 MBYour homepage downloads 2.2 MB in 51 requests on a phone: images 1.1 MB (15), scripts 840 KiB (21) and stylesheets 164 KiB (5). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (87 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.6 g of CO₂ per visit
0.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.63 g of CO₂e: 76.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Yale School of Management | Educating Leaders for Business and Society”.
Structured data has 2 problems
Structured data found (Organization, VideoObject, WebPage and WebSite) but with 2 problems, for example “Organization: missing name”.
88 internal links, 42 external
The homepage links to 88 pages on som.yale.edu and 42 external pages.
6 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “The Yale School of Management, also known as Yale SOM, is a world-renowned business school that offers MBA, EMBA, MAM, …”.
One H1 headline
Your main headline reads: “Mission Matters”.
Canonical URL set
The canonical URL is https://som.yale.edu/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://som.yale.edu/sitemap.xml.
AI search readiness
Organization data is thin (0 of 6 facts)
Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://som.yale.edu/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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,633 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
https://som.yale.edu/50th-anniversary, https://som.yale.edu/centers/the-broad-center/masters-degree-in-public-education-management and https://som.yale.edu/the-som-experience have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://som.yale.edu/programs/silver-scholars, whose canonical is https://som.yale.edu/programs/mba/admissions/silver-scholars. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://som.yale.edu/50th-anniversary has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 63 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
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 ()”.
2 checks passed
Tap targets are thumb-sized
13 of 16 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Local business without LocalBusiness data
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 971 words of copy
The homepage carries about 971 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact”, “Apply” and “Apply Now”.
Social proof on the page
Social proof on the homepage: 11 testimonial or review blocks and 2 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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.
6 cookies set on arrival
6Opening the homepage sets 6 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
19 other companies contacted
Loading the homepage contacts 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at som.yale.edu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on som.yale.edu, including 15 speed issues, 2 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.