mcpherson.edu website review

About 1,008 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.4 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Bing Ads and others), adding 892 KiB and 734 ms of main-thread time.

About 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

Google Tag Manager costs a phone 479 ms of main-thread work and 523 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.

10 long tasks block the main thread while loading, the longest for 358 ms. During a long task the page ignores taps.

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

6 images could be 227 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

13 KiB could be saved by minifying CSS.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 18.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “students outside the Commons”.

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

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

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

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

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

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

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

Your homepage downloads 4.7 MB in 121 requests on a phone: images 2.2 MB (16), scripts 2.1 MB (82) and fonts 189 KiB (9). Under 2 MB keeps phones on slow connections fast.

6 images (407 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.

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

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

4 tap targets are too small or too close together to hit reliably with a finger.

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

Your meta description is 190 characters; Google truncates after about 160, so the end of your pitch is cut.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 68 pages on mcpherson.edu and 15 external pages.

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

https://www.mcpherson.edu/apply, https://www.mcpherson.edu/visit, https://www.mcpherson.edu/giving/make-a-gift, https://www.mcpherson.edu/incoming, https://www.mcpherson.edu/family and https://www.mcpherson.edu/alumni and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187273463&tm=gtm002&Ver=2&mid=48d7eb36-7fe1-4af4-a8e1-6dcb96b0020b&bo=1&sid=f616b4d0d56e11f1bf8117f1154d3dca&vid=f616c620d56e11f1b0ea0d41709cb53e&vids=1&msclkid=N&pi=9.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

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

The homepage carries about 530 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 2 mores (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.

Opening the homepage sets 12 cookies (measured from a US location before any click).

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.

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