Website review, no card needed

godstowe.org logo

godstowe.org website review

Visit site (opens in a new tab)Reviewed 21 October 202626 issues · 83 checks

This review found 26 issues worth fixing on godstowe.org, 5 of them high impact, across 83 checks. The most urgent: 7 buttons without a name. 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.9 s717 msMay 2Oct 171.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.2 s
May 9, 20263.2 s
May 16, 20263.6 s
May 23, 20263.5 s
May 30, 20263.6 s
Jun 6, 20263.0 s
Jun 13, 20261.4 s
Jun 20, 20261.5 s
Jun 27, 20261.4 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 15, 20261.5 s
Aug 22, 20261.3 s
Aug 29, 20261.4 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.2 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
216 ms95 msMay 2Oct 17112 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026109 ms
May 9, 2026135 ms
May 16, 2026177 ms
May 23, 2026191 ms
May 30, 2026202 ms
Jun 6, 2026176 ms
Jun 13, 2026121 ms
Jun 20, 2026121 ms
Jun 27, 2026111 ms
Jul 4, 2026115 ms
Jul 11, 2026113 ms
Jul 18, 2026117 ms
Jul 25, 2026119 ms
Aug 1, 2026128 ms
Aug 22, 2026137 ms
Aug 29, 2026137 ms
Sep 5, 2026129 ms
Sep 12, 2026137 ms
Sep 19, 2026135 ms
Sep 26, 2026120 ms
Oct 3, 2026122 ms
Oct 10, 2026120 ms
Oct 17, 2026112 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 godstowe.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix78
  • Reduce unused JavaScript

    600 ms · 489 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 1.0 MB and 899 ms of main-thread time.

  • Mobile performance score: 78

    78/100

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

  • Google Tag Manager adds 538 ms

    538 ms

    Google Tag Manager costs a phone 538 ms of main-thread work and 699 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 224 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    210 KiB

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

  • Legacy JavaScript

    150 ms · 23 KiB

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

  • Font display

    150 ms

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

  • Render-blocking requests

    150 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

  • Improve image delivery

    75 KiB

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

  • Reduce unused CSS

    30 KiB

    About 30 KiB of CSS is downloaded but never applied on this page.

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

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 1.2 s of it running JavaScript. That is comfortably low.

  • Server response: 31 ms

    31 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 15.2 s

    15.2 s

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

  • Largest Contentful Paint: 3.5 s

    3.5 s

    Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A leading independent day and boarding school, welcoming bo…”.

  • Total Blocking Time: 427 ms

    427 ms

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

  • 24 images without width and height

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

  • Speed Index: 3.9 s

    3.9 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Tap response (INP) held steady for real visitors

    -5%

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

8 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.1 s

    1.1 s

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

  • Real-user INP: 135 ms

    135 ms

    Real visitors wait 135 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.

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 755 ms

    755 ms

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

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

    -59%

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

  • Cumulative Layout Shift: 0.015

    0.015

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.53 g

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

4 checks passed
  • Page weight: 1.9 MB in 65 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 65 requests on a phone: scripts 1.2 MB (15), fonts 328 KiB (6) and images 313 KiB (18). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 8091
  • 7 buttons without a name

    7 buttons have no accessible name, so screen readers announce just “button”.

  • 16 images without alt text

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

  • All page content should be contained by landmarks (36 elements)

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

  • Zoom is disabled

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

  • 3 links without text

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

  • 1 form field without a label

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

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

4 to fixGoogle 8577
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (26 characters)

    Your title is only 26 characters: “Welcome to Godstowe School”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: sameAs is an empty list”.

  • 5 links crawlers can't follow

    5 links have no real href, so search engines can't follow them.

  • 129 internal links, 35 external

    The homepage links to 129 pages on godstowe.org and 35 external pages.

5 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “Welcome to Godstowe School, a co-educational day and boarding school for girls aged 9 months to 13 years, and boys aged…”.

  • Canonical URL set

    The canonical URL is https://www.godstowe.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.godstowe.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.godstowe.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 (479 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix93
  • 1 linked page hidden from search

    https://www.godstowe.org/admissions/welcome-to-admissions is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

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

    The homepage carries about 282 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: “CONTACT”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “contact”, “Start Your Journey” and “enquire now”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 3 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
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (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.

  • 13 cookies set on arrival

    13

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

  • 21 other companies contacted

    Loading the homepage contacts 21 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 godstowe.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on godstowe.org, including 10 speed issues, 4 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