Website review, no card needed

thewalkerschool.org logo

thewalkerschool.org website review

Visit site (opens in a new tab)Reviewed 30 October 202646 issues · 90 checks

This review found 46 issues worth fixing on thewalkerschool.org, 15 of them high impact, across 90 checks. The most urgent: page weight: 35.8 MB in 78 requests. 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 s2.1 sMay 9Oct 243.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.3 s
May 16, 20262.3 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.4 s
Jun 13, 20262.3 s
Jun 20, 20262.4 s
Jun 27, 20262.8 s
Jul 4, 20262.9 s
Jul 11, 20263.1 s
Jul 18, 20263.2 s
Jul 25, 20263.1 s
Aug 1, 20263.2 s
Aug 8, 20263.0 s
Aug 15, 20262.9 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.5 s
Sep 19, 20262.7 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
122 ms94 msMay 9Oct 24119 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026101 ms
May 16, 2026103 ms
May 23, 2026101 ms
May 30, 2026101 ms
Jun 6, 2026100 ms
Jun 13, 202697 ms
Jun 20, 2026101 ms
Jun 27, 2026103 ms
Jul 4, 2026103 ms
Jul 11, 2026110 ms
Jul 18, 2026113 ms
Jul 25, 2026118 ms
Aug 1, 2026119 ms
Aug 8, 2026114 ms
Aug 15, 2026108 ms
Aug 22, 2026104 ms
Aug 29, 2026107 ms
Sep 5, 2026104 ms
Sep 12, 2026106 ms
Sep 19, 2026113 ms
Sep 26, 2026108 ms
Oct 3, 2026108 ms
Oct 10, 2026113 ms
Oct 17, 2026111 ms
Oct 24, 2026119 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 thewalkerschool.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thewalkerschool.org at 0.4 s0.4 s
  2. thewalkerschool.org at 0.9 s0.9 s
  3. thewalkerschool.org at 1.3 s1.3 s
  4. thewalkerschool.org at 1.7 s1.7 s
  5. thewalkerschool.org at 2.2 s2.2 s
  6. thewalkerschool.org at 2.6 s2.6 s
  7. thewalkerschool.org at 3.0 s3.0 s
  8. thewalkerschool.org at 3.5 s3.5 s

Speed

12 to fix50
  • Render-blocking requests

    3.0 s

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

  • Reduce unused CSS

    1.0 s · 190 KiB

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

  • Improve image delivery

    28.9 MB

    20 images could be 28.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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 35.6 MB and 1.3 s of main-thread time.

  • amais.com adds 301 ms

    301 ms

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

  • Mobile performance score: 50

    50/100

    Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    450 ms · 415 KiB

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

  • Google Tag Manager adds 691 ms

    691 ms

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

  • Reduce unused JavaScript

    450 ms · 286 KiB

    About 286 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Facebook adds 290 ms

    290 ms

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

  • 10 long tasks on the main thread

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

  • Main-thread work: 3.1 s

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

  • Font display

    250 ms

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

  • Minify CSS

    150 ms · 13 KiB

    13 KiB could be saved by minifying CSS.

  • Minify JavaScript

    17 KiB

    17 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    13 KiB

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

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

    20 ms

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

Core Web Vitals

11 to fix67
  • 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 LCP: 5.6 s

    5.6 s

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Time to Interactive: 11.9 s

    11.9 s

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

  • Largest Contentful Paint: 4.7 s

    4.7 s

    Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “How did we get here? Our standards are high for how we lear…”. Most of its time is element render delay (2.4 s).

  • Total Blocking Time: 816 ms

    816 ms

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

  • Speed Index: 6.1 s

    6.1 s

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

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

    +30%

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • 3 images without width and height

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

  • Tap response (INP) got 13% slower for real visitors

    +13%

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

3 checks passed
  • Real-user INP: 145 ms

    145 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 35.8 MB in 78 requests

    35.8 MB

    Your homepage downloads 35.8 MB in 78 requests on a phone: images 29.9 MB (28), media 4.5 MB (2) and scripts 940 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 13 images over 500 KB

    13 images weigh 29.5 MB together. On a phone connection a single image that size takes seconds.

  • 14 images far larger than shown

    21.2 MB

    14 images are downloaded at several times the size a phone draws them, for example 8_4-1307.png at 2,560 px wide, shown at 340 px. Resized copies would save about 21.2 MB.

  • 14 images in older formats

    14 images (29.5 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.

  • 9 images below the first screen load straight away

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

  • About 10.1 g of CO₂ per visit

    10.14 g

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

Accessibility

4 to fixGoogle 8594
  • 23 images without alt text

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

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

  • Headings skip levels

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

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

4 to fixGoogle 7785
  • Title is short (4 characters)

    Your title is only 4 characters: “Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 12 links with vague text

    12 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 set, so this is minor.

  • 277 internal links, 9 external

    The homepage links to 277 pages on thewalkerschool.org and 9 external pages.

6 checks passed
  • Meta description: 110 characters

    Your meta description is 110 characters: “Explore a top-rated PK3-12 college preparatory school in Marietta, GA, with a diverse and inclusive community.”.

  • One H1 headline

    Your main headline reads: “Home”.

  • Canonical URL set

    The canonical URL is https://www.thewalkerschool.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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.thewalkerschool.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.thewalkerschool.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 (1,759 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 2 pages share a title

    https://www.thewalkerschool.org/about-us and https://www.thewalkerschool.org/we-value all use the title “We Value”. 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.thewalkerschool.org/admission has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.thewalkerschool.org/about-us, https://www.thewalkerschool.org/we-value and https://www.thewalkerschool.org/history 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.thewalkerschool.org/about-us, whose canonical is https://www.thewalkerschool.org/we-value. 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 90 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: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • 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: “more than 50 teams”. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 704 words of visible text.

3 checks passed
  • 16 calls to action

    The homepage has 16 calls to action, for example “Inquire”, “Visit and Apply” and “Learn more”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 17 other companies contacted

    Loading the homepage contacts 17 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 thewalkerschool.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

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 thewalkerschool.org, including 23 speed issues, 4 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