manhattan.edu website review

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

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

29 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

Google Tag Manager costs a phone 1.1 s of main-thread work and 1,004 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.

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

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

8 third-party services load with your homepage (Google Tag Manager, Vimeo and cloudfront.net and others), adding 9.0 MB and 2.5 s of main-thread time.

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

Vimeo costs a phone 493 ms of main-thread work and 6.5 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.

cloudfront.net costs a phone 366 ms of main-thread work and 1.0 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.

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

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

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

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

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

2 KiB could be saved by minifying JavaScript.

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 15.1 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 27.4 s. Good is under 3.8 s.

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

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

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

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

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

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

Your homepage downloads 10.3 MB in 163 requests on a phone: other files 5.8 MB (58), scripts 2.8 MB (61) and images 1.0 MB (27). Under 2 MB keeps phones on slow connections fast.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 174 pages on manhattan.edu and 22 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.

Your homepage links to https://manhattan.edu/admissions/financial-aid, which answers with an error. Visitors hit a dead end and search engines drop it.

https://manhattan.edu/admissions, https://manhattan.edu/admissions/undergraduate, https://manhattan.edu/graduate, https://manhattan.edu/admissions/transfer, https://manhattan.edu/admissions/veterans and https://manhattan.edu/admissions/financial-aid/loans-grants/scholarships-and-grants and 2 others use the same meta description. A description written for each page earns more clicks.

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

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

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

4 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://qvdt3feo.com/events.js' violates the following Content Security Policy directive: "script-s…”.

1 image is served at too low a resolution for sharp phone screens.

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

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.

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

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

Before a visitor clicks anything, the page loads Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and HubSpot and 3 mores (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 13 cookies, 3 of them by other companies (measured from a US location before any click).

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