Website review, no card needed

houghton.edu logo

houghton.edu website review

Visit site (opens in a new tab)Reviewed 28 October 202626 issues · 81 checks

This review found 26 issues worth fixing on houghton.edu, 8 of them high impact, across 81 checks. The most urgent: fails Core Web Vitals for real visitors. 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.2 s1.7 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.0 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.8 s
Jul 4, 20261.9 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.1 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
130 ms102 msMay 9Oct 24123 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026127 ms
May 16, 2026122 ms
May 23, 2026117 ms
May 30, 2026113 ms
Jun 6, 2026110 ms
Jun 13, 2026112 ms
Jun 20, 2026113 ms
Jun 27, 2026111 ms
Jul 4, 2026109 ms
Jul 11, 2026105 ms
Jul 18, 2026108 ms
Jul 25, 2026111 ms
Aug 1, 2026113 ms
Aug 8, 2026114 ms
Aug 15, 2026114 ms
Aug 22, 2026117 ms
Aug 29, 2026117 ms
Sep 5, 2026120 ms
Sep 12, 2026119 ms
Sep 19, 2026119 ms
Sep 26, 2026118 ms
Oct 3, 2026115 ms
Oct 10, 2026118 ms
Oct 17, 2026117 ms
Oct 24, 2026123 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 houghton.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. houghton.edu at 0.4 s0.4 s
  2. houghton.edu at 0.8 s0.8 s
  3. houghton.edu at 1.1 s1.1 s
  4. houghton.edu at 1.5 s1.5 s
  5. houghton.edu at 1.9 s1.9 s
  6. houghton.edu at 2.3 s2.3 s
  7. houghton.edu at 2.6 s2.6 s
  8. houghton.edu at 3.0 s3.0 s

Speed

4 to fix75
  • Mobile performance score: 75

    75/100

    Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    600 ms · 102 KiB

    1 image could be 102 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Fonts, Adobe TypeKit and assetcdn.net), adding 1.7 MB and 0 ms of main-thread time.

  • assetcdn.net adds 0 ms

    0 ms

    assetcdn.net costs a phone 0 ms of main-thread work and 1.6 MB 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

    25 KiB

    About 25 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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.

2 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 138 ms of it running JavaScript. That is comfortably low.

  • Server response: 21 ms

    21 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 4.7 s

    4.7 s

    Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is element render delay (2.4 s).

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user CLS: 0.20

    0.20

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

  • Speed Index: 4.7 s

    4.7 s

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

  • Time to Interactive: 4.7 s

    4.7 s

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

  • Tap response (INP) held steady for real visitors

    -4%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

6 checks passed
  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 107 ms

    107 ms

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 527 ms

    527 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix65
  • 1 image over 500 KB

    220824-Move-In-chapel.jpg weighs 509 KiB. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    925 KiB

    6 images are downloaded at several times the size a phone draws them, for example 220824-Move-In-chapel.jpg at 1,920 px wide, shown at 334 px. Resized copies would save about 925 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (112 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.5 g of CO₂ per visit

    0.55 g

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

2 checks passed
  • Page weight: 1.9 MB in 21 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 21 requests on a phone: images 1.6 MB (8), fonts 241 KiB (5) and HTML 71 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

9 to fixGoogle 8790
  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

    10 elements hidden from screen readers can still receive keyboard focus.

  • Elements must only use permitted ARIA attributes (2 elements)

    Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • 7 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

Google 100100
  • 110 internal links, 9 external

    The homepage links to 110 pages on houghton.edu and 9 external pages.

8 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Houghton University is a liberal arts and sciences Christian university; nationally ranked with customizable programs o…”.

  • One H1 headline

    Your main headline reads: “Be Strong, Be Courageous, Be Fearless”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Houghton University | Nationally Ranked Christian University”.

  • Canonical URL set

    The canonical URL is https://www.houghton.edu/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.

  • 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://www.houghton.edu/sitemap_index.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://www.houghton.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 (6,907 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.houghton.edu/events has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    42 of 51 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix89
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 527 words of copy

    The homepage carries about 527 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “APPLY”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Apply”, “Apply by Dec 1 for a chance to win” and “Schedule a Visit”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Phone number on the homepage

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

  • 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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 3 other companies contacted

    Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 houghton.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
Hosting
Cloudflare

Company

Employees
249
Founded
1883

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on houghton.edu, including 10 speed 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