Website review, no card needed

episcopalhighschool.org logo

episcopalhighschool.org website review

Visit site (opens in a new tab)Reviewed 26 October 202646 issues · 89 checks

This review found 46 issues worth fixing on episcopalhighschool.org, 21 of them high impact, across 89 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.3 s1.9 sMay 9Oct 242.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.6 s
May 16, 20262.5 s
May 23, 20262.5 s
May 30, 20262.8 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.0 s
Jul 18, 20262.8 s
Jul 25, 20262.6 s
Aug 1, 20262.3 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
151 ms97 msMay 9Oct 24121 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026123 ms
May 16, 2026118 ms
May 23, 2026128 ms
May 30, 2026128 ms
Jun 6, 2026127 ms
Jun 13, 2026127 ms
Jun 20, 2026121 ms
Jun 27, 2026122 ms
Jul 4, 2026128 ms
Jul 11, 2026131 ms
Jul 18, 2026136 ms
Jul 25, 2026136 ms
Aug 1, 2026141 ms
Aug 8, 2026137 ms
Aug 15, 2026145 ms
Aug 22, 2026134 ms
Aug 29, 2026129 ms
Sep 5, 2026126 ms
Sep 12, 2026121 ms
Sep 19, 2026127 ms
Sep 26, 2026116 ms
Oct 3, 2026111 ms
Oct 10, 2026103 ms
Oct 17, 2026104 ms
Oct 24, 2026121 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of episcopalhighschool.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. episcopalhighschool.org at 0.8 s0.8 s
  2. episcopalhighschool.org at 1.5 s1.5 s
  3. episcopalhighschool.org at 2.3 s2.3 s
  4. episcopalhighschool.org at 3.0 s3.0 s
  5. episcopalhighschool.org at 3.8 s3.8 s
  6. episcopalhighschool.org at 4.5 s4.5 s
  7. episcopalhighschool.org at 5.3 s5.3 s
  8. episcopalhighschool.org at 6.1 s6.1 s

Speed

14 to fix16
  • Improve image delivery

    1.1 s · 9.5 MB

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

  • Render-blocking requests

    4.3 s

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

  • Use efficient cache lifetimes

    3.5 s · 668 KiB

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

  • Reduce unused CSS

    2.1 s · 459 KiB

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

  • Reduce unused JavaScript

    1.2 s · 181 KiB

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

  • Mobile performance score: 16

    16/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, amais.com and Facebook and others), adding 13.5 MB and 820 ms of main-thread time.

  • amais.com adds 307 ms

    307 ms

    amais.com costs a phone 307 ms of main-thread work and 12.7 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.

  • Font display

    850 ms

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

  • Google Tag Manager adds 332 ms

    332 ms

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

  • Minify CSS

    310 ms · 49 KiB

    49 KiB could be saved by minifying CSS.

  • 9 long tasks on the main thread

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

  • Main-thread work: 2.9 s

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

  • 2,467 HTML elements

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

  • Legacy JavaScript

    150 ms · 12 KiB

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

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 21 ms

    21 ms

    Your server sent the HTML in 21 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix33
  • Fails Core Web Vitals for real visitors

    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-user CLS: 1.00

    1.00

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

  • Largest Contentful Paint: 15.3 s

    15.3 s

    Your largest element takes 15.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WHAT SETS EPISCOPAL HIGH SCHOOL APART”.

  • First Contentful Paint: 7.4 s

    7.4 s

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

  • Cumulative Layout Shift: 1

    1

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

  • Time to Interactive: 15.3 s

    15.3 s

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

  • Speed Index: 9.5 s

    9.5 s

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

  • Total Blocking Time: 643 ms

    643 ms

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

  • Real-user LCP: 2.9 s

    2.9 s

    Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Tap response (INP) held steady for real visitors

    -7%

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

4 checks passed
  • Real-user INP: 146 ms

    146 ms

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 544 ms

    544 ms

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

Images and page weight

5 to fix18
  • Page weight: 14.0 MB in 128 requests

    14.0 MB

    Your homepage downloads 14.0 MB in 128 requests on a phone: images 12.6 MB (69), scripts 739 KiB (21) and stylesheets 479 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 38 images far larger than shown

    9.6 MB

    38 images are downloaded at several times the size a phone draws them, for example 20250415episcopalclassroomspring2025lisaboggs193-1034.jpg at 3,600 px wide, shown at 260 px. Resized copies would save about 9.6 MB.

  • 3 images over 500 KB

    3 images weigh 6.1 MB together. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (4.7 MB) is 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.

  • 20 images below the first screen load straight away

    20 images further down the page (3.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.0 g of CO₂ per visit

    3.97 g

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

Accessibility

6 to fixGoogle 8191
  • 1 button without a name

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

  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 10 images without alt text

    10 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9284
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “Episcopal High School: Best Boarding High School in Alexandria, VA”.

  • No structured data

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

  • Meta description is long (374 characters)

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 347 internal links, 18 external

    The homepage links to 347 pages on episcopalhighschool.org and 18 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Episcopal High School: Best Boarding High School in Alexandria, VA”.

  • Canonical URL set

    The canonical URL is https://www.episcopalhighschool.org/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.episcopalhighschool.org/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.episcopalhighschool.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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,104 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 2 pages share a title

    https://www.episcopalhighschool.org/admissions-and-aid and https://www.episcopalhighschool.org/welcome-to-ehs all use the title “Welcome to EHS | Admissions | Episcopal High School”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.episcopalhighschool.org/about-us has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.episcopalhighschool.org/since-1839-the-history-of-ehs and https://www.episcopalhighschool.org/heads-of-school use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.episcopalhighschool.org/admissions-and-aid, whose canonical is https://www.episcopalhighschool.org/welcome-to-ehs. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    8 of 9 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • Local business without LocalBusiness data

    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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,076 words of copy

    The homepage carries about 1,076 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Register here”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Inquire”, “The Roll Call” and “Register here”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 4 trackers load before any consent

    4

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

  • 3 cookies set on arrival

    3

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

  • 18 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at episcopalhighschool.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Azure

Company

Founded
1839

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on episcopalhighschool.org, including 23 speed issues, 3 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25