utica.edu website review

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

27 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.8 s faster on a phone.

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

About 684 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.4 s faster on a phone.

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

Your mobile performance score is 26. 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 hideousplay.com and others), adding 1.3 MB and 990 ms of main-thread time.

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

25 KiB could be saved by minifying JavaScript.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need.

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

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 27.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Commencement 2024”.

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

The layout shifts by 1.089 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Real visitors wait 228 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 145 ms to 188 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

1 image have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 4.8 MB in 119 requests on a phone: images 2.3 MB (42), scripts 1.7 MB (29) and stylesheets 721 KiB (5). Under 2 MB keeps phones on slow connections fast.

2024-Commencement-DSC_5410-2520x1120-crop.jpg weighs 577 KiB. On a phone connection a single image that size takes seconds.

18 images (1.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.

8 images further down the page (642 KiB) 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 cyber_range_ribbon_cutting_2026.jpg at 960 px wide, shown at 270 px. Resized copies would save about 96 KiB.

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

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

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

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

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

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

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

No Open Graph image (also missing: og:title, og:description), 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 126 pages on utica.edu and 10 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.

There is no https://www.utica.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.utica.edu/academics/programs and https://www.utica.edu/honors 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.utica.edu/academics/student-support-and-success, whose canonical is https://www.utica.edu/directory/student-success. 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 92 found) and read each the way a search engine does.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

The homepage carries about 602 words of visible text.

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