Website review, no card needed
animalcenter.org website review
Visit site (opens in a new tab)Reviewed 22 October 202633 issues · 83 checks
This review found 33 issues worth fixing on animalcenter.org, 13 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.1 s |
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 112 ms |
| May 9, 2026 | 112 ms |
| May 16, 2026 | 113 ms |
| May 23, 2026 | 113 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 113 ms |
| Jul 4, 2026 | 113 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 116 ms |
| Jul 25, 2026 | 119 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 120 ms |
| Aug 22, 2026 | 117 ms |
| Aug 29, 2026 | 116 ms |
| Sep 5, 2026 | 113 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 115 ms |
| Sep 26, 2026 | 117 ms |
| Oct 3, 2026 | 119 ms |
| Oct 10, 2026 | 119 ms |
| Oct 17, 2026 | 114 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
2.7 s
5.5 s
8.2 s
11.0 s
13.7 s
16.5 s
19.2 s
21.9 s
Speed
Reduce unused JavaScript
8.1 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.1 s faster on a phone.
Render-blocking requests
5.0 s66 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.0 s.
Reduce unused CSS
1.2 s · 203 KiBAbout 203 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 43
43/100Your mobile performance score is 43 (desktop: 50). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,007 HTML elements
The page has 3,007 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (cloudfront.net, Google Tag Manager and fareharbor.com and others), adding 2.5 MB and 1.2 s of main-thread time.
Use efficient cache lifetimes
850 ms · 244 KiB10 files are served with short cache lifetimes, so returning visitors download them again (244 KiB).
cloudfront.net adds 389 ms
389 mscloudfront.net costs a phone 389 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.
Google Tag Manager adds 388 ms
388 msGoogle Tag Manager costs a phone 388 ms of main-thread work and 732 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: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
fareharbor.com adds 177 ms
177 msfareharbor.com costs a phone 177 ms of main-thread work and 361 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.
Improve image delivery
150 ms · 62 KiB2 images could be 62 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. 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 182 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb 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: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 14.2 s
14.2 sThe first text or image appears after 14.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 36.4 s
36.4 sYour largest element takes 36.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Helen Woodward Animal Center”.
Speed Index: 22.7 s
22.7 sVisually, the page fills in at 22.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 37.3 s
37.3 sThe page becomes fully interactive after 37.3 s. Good is under 3.8 s.
Total Blocking Time: 468 ms
468 msScripts block taps and scrolling for 468 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 112 ms to 114 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.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 103 ms
103 msReal visitors wait 103 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 299 ms
299 msReal visitors wait 299 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.9 MB in 176 requests
7.9 MBYour homepage downloads 7.9 MB in 176 requests on a phone: images 4.2 MB (23), scripts 2.9 MB (56) and stylesheets 340 KiB (65). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (315 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.
3 images below the first screen load straight away
3 images further down the page (107 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.2 g of CO₂ per visit
2.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.24 g of CO₂e: 269.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 images without alt text
9 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (28 elements)
All page content should be contained by landmarks: 28 elements on the page fail this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h6 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“San Diego Animal Shelter”, “Sign Up Today for” and “SUMMER CRITTER CAMP”). One clear main headline is easier for people and search engines.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
235 internal links, 60 external
The homepage links to 235 pages on animalcenter.org and 60 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Discover a world of compassion at the Animal Center. Our dedicated rescue team provides shelter, medical support, and l…”.
Title: 51 characters
Your title is a healthy 51 characters: “San Diego Animal Shelter: Dog and Cat Rescue | HWAC”.
Canonical URL set
The canonical URL is https://animalcenter.org/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.
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://animalcenter.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://animalcenter.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,604 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://animalcenter.org/fetch-bio-page has no meta description, so Google writes the search snippet from whatever text it finds.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://animalcenter.org/adopt-a-pet/adoptable-dogs, whose canonical is https://animalcenter.org/pet-adoption/adoptable-dogs. 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 104 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.
Titles are unique
Every page we checked has its own title.
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
5 small tap targets
5 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Identifier 'revokeListeners' has already been declared”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. 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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 349 words of copy
The homepage carries about 349 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “REGISTER TODAY” and “Sign Up For Our E-Newsletter!”.
7 calls to action
The homepage has 7 calls to action, for example “REGISTER TODAY”, “Help Orphan Pets While You Shop!” and “Contact Us”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before 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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
20 other companies contacted
Loading the homepage contacts 20 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 animalcenter.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
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
Company
- Founded
- 1972
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on animalcenter.org, including 16 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.