parker.edu website review

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

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

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

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

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

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

8 third-party services load with your homepage (TikTok, Facebook and Google Tag Manager and others), adding 794 KiB and 1.0 s of main-thread time.

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

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

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

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

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

72 KiB could be saved by minifying JavaScript.

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

12 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 10.0 MB in 337 requests on a phone: images 6.6 MB (83), scripts 2.4 MB (107) and fonts 592 KiB (18). Under 2 MB keeps phones on slow connections fast.

40 images (4.9 MB) 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.

40 images further down the page (4.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images are downloaded at several times the size a phone draws them, for example 37022413 at 1,284 px wide, shown at 388 px. Resized copies would save about 79 KiB.

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

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

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

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

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

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

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

Your title is only 24 characters: “Home - Parker University”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 198 pages on parker.edu and 34 external pages.

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.

https://www.parker.edu/application, https://www.parker.edu/tour, https://www.parker.edu/give, https://www.parker.edu/contact, https://www.parker.edu/veteran-resources and https://www.parker.edu/campus-life and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.parker.edu/doctor-of-chiropractic-degree, whose canonical is https://www.parker.edu/academics/doctor-of-chiropractic-degree. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

We fetched 15 pages linked from your homepage (of 49 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=5140409&tm=gtm002&Ver=2&mid=bc6cc776-6184-418a-9441-326468817b25&bo=1&sid=eb2a2020d34511f1b687ab4e3dfd0371&vid=eb2a3bf0d34511f1bf3b65799194dd15&vids=1&msclkid=N&pi=918.

3 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Bootstrap's JavaScript requires jQuery version 1.9.1 or higher, but lower than version 3”.

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

There is no form on the homepage, so every lead has to click through to another page first.

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 1,030 words of visible text.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 4 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 22 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 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.