scrantonprep.org website review

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Usersnap and termly.io and others), adding 17.1 MB and 474 ms of main-thread time.

finalsite.net costs a phone 0 ms of main-thread work and 16.3 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.

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

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

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

6 images could be 153 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

For real visitors the layout shifts by 0.41 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 99 ms to 95 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 3.3 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 22.2 MB in 74 requests on a phone: media 18.8 MB (2), scripts 1.4 MB (15) and images 1.4 MB (26). Under 2 MB keeps phones on slow connections fast.

Scranton_logo_purple.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example footer-logo.svg at 143 px wide, shown at 44 px. Resized copies would save about 8 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate 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.

Elements with visible text labels do not have matching accessible names. (3 elements).

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

Your meta description is only 34 characters: “Home - Scranton Preparatory School”. 70 to 160 characters is enough to sell the click.

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

No XML sitemap at https://www.scrantonprep.org/sitemap.xml, so Google discovers your pages only by following links.

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

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

The homepage links to 138 pages on scrantonprep.org and 18 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.scrantonprep.org/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.scrantonprep.org/parents, https://www.scrantonprep.org/giving and https://www.scrantonprep.org/about/directory took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://www.scrantonprep.org/.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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.

Social proof on the homepage: 7 testimonial or review blocks. 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.

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

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

Opening the homepage sets 2 cookies (measured from a US location before any click).

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