su.edu website review

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

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

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 1.3 MB 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 34 (desktop: 43). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

8 third-party services load with your homepage (Google Tag Manager, YouTube and Facebook and others), adding 3.8 MB and 2.1 s of main-thread time.

24 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

YouTube costs a phone 412 ms of main-thread work and 994 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.

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

Facebook costs a phone 271 ms of main-thread work and 295 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.

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

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

Accessibe Accessibility Overlay costs a phone 154 ms of main-thread work and 436 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.

geckoengage.com costs a phone 62 ms of main-thread work and 722 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.

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

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

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

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

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

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

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

Scripts block taps and scrolling for 961 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 187 ms to 366 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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.2 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 59.4 MB in 201 requests on a phone: media 51.0 MB (19), scripts 3.4 MB (69) and images 2.5 MB (28). Under 2 MB keeps phones on slow connections fast.

buzzy_icon-circle_big.png weighs 558 KiB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example buzzy_icon-circle_big.png at 740 px wide, shown at 74 px. Resized copies would save about 508 KiB.

11 images (2.2 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.

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

<svg> elements with an img or image role must have alternative text: 18 elements on the page fail this check, rated serious by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

The homepage links to 327 pages on su.edu and 51 external pages.

There is no /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.

/campus-maps and /bookstore have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example /jobs, whose canonical is /human-resources. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/su-giving and /bookstore have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 third-party cookies are 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 “Unexpected token ';'”.

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.

Social proof on the homepage: “1,400+ Students”. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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