Website review, no card needed

woodward.edu logo

woodward.edu website review

Visit site (opens in a new tab)Reviewed 1 November 202637 issues · 88 checks

This review found 37 issues worth fixing on woodward.edu, 12 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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
2.8 s2.2 sMay 9Oct 242.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.5 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.6 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.6 s
Sep 19, 20262.7 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.8 s
Oct 24, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
116 ms103 msMay 9Oct 24104 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026105 ms
May 16, 2026104 ms
May 23, 2026105 ms
May 30, 2026106 ms
Jun 6, 2026109 ms
Jun 13, 2026110 ms
Jun 20, 2026110 ms
Jun 27, 2026106 ms
Jul 4, 2026105 ms
Jul 11, 2026110 ms
Jul 18, 2026112 ms
Jul 25, 2026114 ms
Aug 1, 2026112 ms
Aug 8, 2026112 ms
Aug 15, 2026106 ms
Aug 22, 2026105 ms
Aug 29, 2026106 ms
Sep 5, 2026105 ms
Sep 12, 2026106 ms
Sep 19, 2026109 ms
Sep 26, 2026111 ms
Oct 3, 2026110 ms
Oct 10, 2026109 ms
Oct 17, 2026105 ms
Oct 24, 2026104 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 woodward.edu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. woodward.edu at 0.4 s0.4 s
  2. woodward.edu at 0.8 s0.8 s
  3. woodward.edu at 1.1 s1.1 s
  4. woodward.edu at 1.5 s1.5 s
  5. woodward.edu at 1.9 s1.9 s
  6. woodward.edu at 2.3 s2.3 s
  7. woodward.edu at 2.6 s2.6 s
  8. woodward.edu at 3.0 s3.0 s

Speed

9 to fix29
  • Use efficient cache lifetimes

    8.8 s · 1.5 MB

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

  • Reduce unused JavaScript

    7.2 s · 1.3 MB

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

  • Render-blocking requests

    5.8 s

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

  • Mobile performance score: 29

    29/100

    Your mobile performance score is 29. 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, weglot.com and juicer.io and others), adding 1.6 MB and 811 ms of main-thread time.

  • Reduce unused CSS

    750 ms · 119 KiB

    About 119 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Google Tag Manager adds 659 ms

    659 ms

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

  • 2,493 HTML elements

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

  • Main-thread work: 2.4 s

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

  • Legacy JavaScript

    150 ms · 46 KiB

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

  • 10 long tasks on the main thread

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

  • Improve image delivery

    182 KiB

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

  • Font display

    50 ms

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

  • 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: 10 ms

    10 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 20.9 s

    20.9 s

    Your largest element takes 20.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Pause Pause Pause Pause Pause”.

  • Time to Interactive: 21.1 s

    21.1 s

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

  • First Contentful Paint: 5.9 s

    5.9 s

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

  • Speed Index: 9.6 s

    9.6 s

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

  • Cumulative Layout Shift: 0.284

    0.284

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

  • Total Blocking Time: 498 ms

    498 ms

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

  • Tap response (INP) held steady for real visitors

    0%

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

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

    +15%

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

6 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 96 ms

    96 ms

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

  • Real-user CLS: 0.06

    0.06

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 616 ms

    616 ms

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

Images and page weight

3 to fix74
  • Page weight: 3.5 MB in 102 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 102 requests on a phone: scripts 2.3 MB (21), images 959 KiB (53) and stylesheets 141 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Reese.jpg 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 far larger than shown

    78 KiB

    1 image is downloaded at several times the size a phone draws it, for example unnamed1.jpg at 460 px wide, shown at 1 px. Resized copies would save about 78 KiB.

  • 2 images in older formats

    2 images (235 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.

  • 1 image below the first screen load straight away

    1 image further down the page (156 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.99 g

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

Accessibility

5 to fixGoogle 9393
  • Links must have discernible text (5 elements)

    Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

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

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 37 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

5 to fixGoogle 8585
  • No structured data

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

  • No social preview image

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

  • No XML sitemap

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

  • 6 links with vague text

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

  • 1 link crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 118 internal links, 23 external

    The homepage links to 118 pages on woodward.edu and 23 external pages.

5 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Woodward Academy is a private school in Atlanta, Georgia, offering Pre-K to 12 college-preparatory education with diver…”.

  • One H1 headline

    Your main headline reads: “Welcome to Woodward”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Pre-K-Grade 12 Private School in Atlanta | Woodward Academy”.

  • Canonical URL set

    The canonical URL is https://www.woodward.edu/.

  • robots.txt in place

    robots.txt is in place.

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

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 (4,340 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    https://www.woodward.edu/parentportal and https://www.woodward.edu/employees all use the title “Veracross”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.woodward.edu/parentportal and https://www.woodward.edu/employees have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.woodward.edu/who-we-are/strategic-plan, https://www.woodward.edu/who-we-are/our-stories, https://www.woodward.edu/who-we-are/community and https://www.woodward.edu/who-we-are/our-history have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.woodward.edu/parentportal and https://www.woodward.edu/employees have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 2 pages slow to respond

    https://www.woodward.edu/who-we-are/our-stories and https://www.woodward.edu/who-we-are/careers took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 52 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.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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

2 to fixGoogle 9687
  • 5 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://sites-management-api.451.io/site?domain=woodward.shell.451.io&type=shell451' from origin 'h…”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • No opening hours

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

  • 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 951 words of copy

    The homepage carries about 951 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “INQUIRE (OPENS IN NEW WINDOW/TAB)” and “APPLY (OPENS IN NEW WINDOW/TAB)”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Inquire(opens in new window/tab)”, “Apply(opens in new window/tab)” and “Academy-wide Late Start Day”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 11 cookies set on arrival

    11

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

  • No consent tool detected

    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.

  • 24 other companies contacted

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

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 woodward.edu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

Company

Founded
1900

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on woodward.edu, including 15 speed issues, 5 SEO issues and 2 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