Website review, no card needed

earlham.edu logo

earlham.edu website review

Visit site (opens in a new tab)Reviewed 3 November 202648 issues · 99 checks

This review found 48 issues worth fixing on earlham.edu, 23 of them high impact, across 99 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.4 s1.5 sMay 16Oct 311.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.2 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.3 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.1 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.1 s
Aug 29, 20262.0 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20262.0 s
Oct 3, 20262.2 s
Oct 10, 20262.2 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Oct 31, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
220 ms140 msMay 16Oct 31188 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026179 ms
May 23, 2026194 ms
May 30, 2026211 ms
Jun 6, 2026210 ms
Jun 13, 2026183 ms
Jun 20, 2026160 ms
Jun 27, 2026150 ms
Jul 4, 2026152 ms
Jul 11, 2026149 ms
Jul 18, 2026153 ms
Jul 25, 2026158 ms
Aug 1, 2026166 ms
Aug 8, 2026181 ms
Aug 15, 2026185 ms
Aug 22, 2026188 ms
Aug 29, 2026190 ms
Sep 5, 2026179 ms
Sep 12, 2026187 ms
Sep 19, 2026186 ms
Sep 26, 2026171 ms
Oct 3, 2026178 ms
Oct 10, 2026170 ms
Oct 17, 2026177 ms
Oct 24, 2026184 ms
Oct 31, 2026188 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

Full-page screenshot of earlham.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. earlham.edu at 1.8 s1.8 s
  2. earlham.edu at 3.6 s3.6 s
  3. earlham.edu at 5.4 s5.4 s
  4. earlham.edu at 7.2 s7.2 s
  5. earlham.edu at 9.0 s9.0 s
  6. earlham.edu at 10.8 s10.8 s
  7. earlham.edu at 12.6 s12.6 s
  8. earlham.edu at 14.4 s14.4 s

Speed

15 to fix25
  • Reduce unused JavaScript

    8.4 s · 1.5 MB

    About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.4 s faster on a phone.

  • Use efficient cache lifetimes

    3.0 s · 858 KiB

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

  • Improve image delivery

    2.5 s · 991 KiB

    18 images could be 991 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

  • Render-blocking requests

    2.5 s

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

  • tiktokcdn-us.com adds 1.1 s

    1.1 s

    tiktokcdn-us.com costs a phone 1.1 s of main-thread work and 8.6 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Google Tag Manager adds 1.5 s

    1.5 s

    Google Tag Manager costs a phone 1.5 s of main-thread work and 1,016 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 13.1 s

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

  • Mobile performance score: 25

    25/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, tiktokcdn-us.com and Facebook and others), adding 10.4 MB and 4.2 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    750 ms · 164 KiB

    164 KiB could be saved by minifying JavaScript.

  • Facebook adds 802 ms

    802 ms

    Facebook costs a phone 802 ms of main-thread work and 342 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.

  • Reduce unused CSS

    300 ms · 86 KiB

    About 86 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.

  • FontAwesome CDN adds 295 ms

    295 ms

    FontAwesome CDN costs a phone 295 ms of main-thread work and 43 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.

  • 2,075 HTML elements

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

  • Font display

    200 ms

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

  • Legacy JavaScript

    150 ms · 24 KiB

    Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

  • 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: 10 ms

    10 ms

    Your server sent the HTML in 10 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix67
  • 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.

  • First Contentful Paint: 7.9 s

    7.9 s

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

  • Largest Contentful Paint: 49.7 s

    49.7 s

    Your largest element takes 49.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Slide 1”.

  • Speed Index: 23.2 s

    23.2 s

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

  • Time to Interactive: 50.0 s

    50.0 s

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

  • Total Blocking Time: 3.9 s

    3.9 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Tap response (INP) held steady for real visitors

    0%

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

6 checks passed
  • Real-user INP: 200 ms

    200 ms

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

  • Real-user CLS: 0.03

    0.03

    For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

    Real visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 769 ms

    769 ms

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

  • Largest content (LCP) got 22% faster for real visitors

    -22%

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

  • Cumulative Layout Shift: 0.024

    0.024

    The layout barely moves while loading (CLS 0.024, good is under 0.1).

Images and page weight

3 to fix53
  • Page weight: 30.1 MB in 384 requests

    30.1 MB

    Your homepage downloads 30.1 MB in 384 requests on a phone: media 21.1 MB (6), scripts 4.8 MB (136) and images 2.9 MB (73). Under 2 MB keeps phones on slow connections fast.

  • 10 images in older formats

    10 images (621 KiB) 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.

  • 10 images below the first screen load straight away

    10 images further down the page (570 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 8.5 g of CO₂ per visit

    8.54 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 8388
  • 4 text elements with low contrast

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

  • Frames without titles

    3 frames have no title, so screen-reader users cannot tell what they contain.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (36 elements)

    All page content should be contained by landmarks: 36 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 14 links without text

    14 visible links have no text or label, so screen readers cannot say where they go.

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 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).

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9282
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “ld+json block 2 is not valid JSON (Expected ',' or '}' after property value in JSON at position)”.

  • No XML sitemap

    No XML sitemap at https://earlham.edu/wp-sitemap.xml, so Google discovers your pages only by following links.

  • 137 internal links, 49 external

    The homepage links to 137 pages on earlham.edu and 49 external pages.

5 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “A world-class education for a rapidly changing world — Build a foundation for a good career PLUS skills to adapt to wha…”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “Earlham College — Excellence. For Good. For Life.”.

  • Canonical URL set

    The canonical URL is https://earlham.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.

AI search readiness

100
  • No llms.txt

    There is no https://earlham.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.

3 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,428 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix69
  • 7 linked pages are broken

    Your homepage links to https://earlham.edu/alumni, https://earlham.edu/earlhamday, https://earlham.edu/events/category/alumni, https://earlham.edu/alumni/alumni-events/homecoming-and-reunions, https://earlham.edu/alumni/alumni-awards and https://earlham.edu/faculty and 1 other, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 4 pages share a meta description

    https://earlham.edu/alumni/referral-scholarship and https://earlham.edu/host-event use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://earlham.edu/host-event 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 87 found) and read each the way a search engine does.

5 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 7 pages that loaded have a meta description.

  • 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 7 pages that loaded have a <title>.

Best practices

4 to fixGoogle 5474
  • 2 broken images

    2 images failed to load on a phone, for example https://fonts.gstatic.com/s/i/productlogos/translate/v14/24px.svg.

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “jQuery(...).chosen is not a function”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    9 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,492 words of copy

    The homepage carries about 1,492 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

6 checks passed
  • 12 calls to action

    The homepage has 12 calls to action, for example “Start a marketing project”, “Request Info” and “Apply”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Snap Pixel and 1 more (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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 cookies (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.

  • 62 other companies contacted

    Loading the homepage contacts 62 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 earlham.edu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

Company

Employees
298
Founded
1847
Headquarters
Richmond

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on earlham.edu, including 22 speed issues, 3 SEO issues and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25