ssw.edu website review

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

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

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

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

Your mobile performance score is 55 (desktop: 49). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (YouTube, Google Tag Manager and Google Analytics and others), adding 1.4 MB and 537 ms of main-thread time.

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

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

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

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

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

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

Polyfills for old browsers add 14 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.

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 4.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your largest element takes 44.2 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 15.6 s (Speed Index). Good is under 3.4 s.

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

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

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

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

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

Your homepage downloads 8.7 MB in 237 requests on a phone: images 5.6 MB (15), scripts 2.2 MB (101) and stylesheets 518 KiB (96). Under 2 MB keeps phones on slow connections fast.

2 images (711 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 2.45 g of CO₂e: 294.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 link inside paragraphs relies on colour alone to stand out.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

5 visible links have no text or label, so screen readers cannot say where they go.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

There are 6 <h1> headlines (“Credential Your Lay Leaders”, “Transformation through Healing” and “A Season of Growth”). One clear main headline is easier for people and search engines.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 179 pages on ssw.edu and 21 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://ssw.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://ssw.edu/academics, https://ssw.edu/academics/degrees-and-diplomas, https://ssw.edu/academics/harrison-library, https://ssw.edu/academics/harrison-library/resources, https://ssw.edu/academics/harrison-library/catalog and https://ssw.edu/academics/harrison-library/contact and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://ssw.edu/academics/non-discrimination-policy-and-title-ix took over 3 s to send its HTML from our server.

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

7 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://imageserver.ebscohost.com/branding/tabbedsearch/css/simpletabs.css' from origin 'h…”.

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

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.

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

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