Website review, no card needed
thebrooke.org website review
Visit site (opens in a new tab)Reviewed 3 November 202634 issues · 86 checks
This review found 34 issues worth fixing on thebrooke.org, 9 of them high impact, across 86 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.5 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 176 ms |
| May 23, 2026 | 186 ms |
| May 30, 2026 | 190 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 182 ms |
| Jun 20, 2026 | 177 ms |
| Jun 27, 2026 | 176 ms |
| Jul 4, 2026 | 181 ms |
| Jul 11, 2026 | 199 ms |
| Jul 18, 2026 | 192 ms |
| Jul 25, 2026 | 194 ms |
| Aug 1, 2026 | 192 ms |
| Aug 8, 2026 | 188 ms |
| Aug 15, 2026 | 192 ms |
| Aug 22, 2026 | 193 ms |
| Aug 29, 2026 | 210 ms |
| Sep 5, 2026 | 211 ms |
| Sep 12, 2026 | 210 ms |
| Sep 19, 2026 | 210 ms |
| Sep 26, 2026 | 199 ms |
| Oct 3, 2026 | 198 ms |
| Oct 10, 2026 | 196 ms |
| Oct 17, 2026 | 194 ms |
| Oct 24, 2026 | 189 ms |
| Oct 31, 2026 | 179 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
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.5 s
3.2 s
3.8 s
4.4 s
5.0 s
Speed
Render-blocking requests
1.5 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google CDN and fundraiseup.com and others), adding 2.5 MB and 1.1 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
300 ms · 467 KiB27 files are served with short cache lifetimes, so returning visitors download them again (467 KiB).
YouTube adds 361 ms
361 msYouTube costs a phone 361 ms of main-thread work and 978 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.
Google CDN adds 308 ms
308 msGoogle CDN costs a phone 308 ms of main-thread work and 742 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.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
Optanon adds 70 ms
70 msOptanon costs a phone 70 ms of main-thread work and 310 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 CSS
178 KiBAbout 178 KiB of CSS is downloaded but never applied on this page.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 127 ms. During a long task the page ignores taps.
Improve image delivery
73 KiB2 images could be 73 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 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: 383 ms
383 msYour server sent the HTML in 383 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 21.6 s
21.6 sThe page becomes fully interactive after 21.6 s. Good is under 3.8 s.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 5.7 s
5.7 sYour largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A row of soldiers sit in front of their horses in the trenc…”.
Largest content (LCP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 971 ms
971 msReal visitors wait 971 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 297 ms
297 msScripts block taps and scrolling for 297 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 176 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 179 ms
179 msReal visitors wait 179 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.078
0.078The layout barely moves while loading (CLS 0.078, good is under 0.1).
Images and page weight
Page weight: 4.0 MB in 90 requests
4.0 MBYour homepage downloads 4.0 MB in 90 requests on a phone: scripts 2.2 MB (39), HTML 560 KiB (4) and other files 414 KiB (19). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (130 KiB) 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.
About 1.1 g of CO₂ per visit
1.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.12 g of CO₂e: 134.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 13 images in the HTML carry an alt attribute.
56 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 56 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
45 internal links, 15 external
The homepage links to 45 pages on thebrooke.org and 15 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Every horse remembered”.
Title: 31 characters
Your title is a healthy 31 characters: “Every horse remembered | Brooke”.
Canonical URL set
The canonical URL is https://www.thebrooke.org/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.thebrooke.org/sitemap.xml.
AI search readiness
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.thebrooke.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 (902 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://www.thebrooke.org/about-us/contact-us, https://www.thebrooke.org/what-we-do, https://www.thebrooke.org/what-we-do/our-strategy, https://www.thebrooke.org/what-we-do/research, https://www.thebrooke.org/what-we-do/news-case-studies and https://www.thebrooke.org/about-us and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://www.thebrooke.org/about-us/contact-us, https://www.thebrooke.org/what-we-do, https://www.thebrooke.org/what-we-do/our-strategy, https://www.thebrooke.org/what-we-do/research, https://www.thebrooke.org/what-we-do/news-case-studies and https://www.thebrooke.org/about-us and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages with very little text
https://www.thebrooke.org/about-us/contact-us, https://www.thebrooke.org/what-we-do, https://www.thebrooke.org/what-we-do/our-strategy, https://www.thebrooke.org/what-we-do/research, https://www.thebrooke.org/what-we-do/news-case-studies and https://www.thebrooke.org/about-us and 9 others 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 33 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
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
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 10 testimonial or review blocks. 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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 817 words of copy
The homepage carries about 817 words of visible text.
4 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Contact us”, “Join our neighbourhood” and “Shop”.
2 short forms
2 short forms (5 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies, 1 of them by other companies (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: OneTrust
A consent management tool (OneTrust) 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 thebrooke.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Drupal
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- AWS
Company
- Employees
- 230
- Founded
- 1934
- Headquarters
- Elsayyida Zinab
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on thebrooke.org, including 19 speed issues, 3 SEO issues and 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.