Website review, no card needed
apopo.org website review
Visit site (opens in a new tab)Reviewed 23 October 202635 issues · 79 checks
This review found 35 issues worth fixing on apopo.org, 18 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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
74C- #82,811 of 117,924 reviewed websitesbeats 26%
- #52,489 of 67,048 online storesbeats 18%
- #1,476 of 2,705 WooCommerce storesbeats 39%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.6 s |
| May 9, 2026 | 5.2 s |
| May 16, 2026 | 5.2 s |
| May 23, 2026 | 5.2 s |
| May 30, 2026 | 5.1 s |
| Jun 6, 2026 | 5.3 s |
| Jun 13, 2026 | 5.3 s |
| Jun 20, 2026 | 5.3 s |
| Jun 27, 2026 | 5.3 s |
| Jul 4, 2026 | 5.3 s |
| Jul 11, 2026 | 5.2 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 4.9 s |
| Aug 1, 2026 | 4.8 s |
| Aug 8, 2026 | 4.8 s |
| Aug 15, 2026 | 4.8 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 5.0 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 4.9 s |
| Sep 26, 2026 | 4.9 s |
| Oct 3, 2026 | 4.9 s |
| Oct 10, 2026 | 4.9 s |
| Oct 17, 2026 | 5.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 117 ms |
| May 9, 2026 | 110 ms |
| May 16, 2026 | 113 ms |
| May 23, 2026 | 107 ms |
| May 30, 2026 | 105 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 102 ms |
| Jun 20, 2026 | 101 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 124 ms |
| Jul 11, 2026 | 129 ms |
| Jul 18, 2026 | 130 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 123 ms |
| Aug 15, 2026 | 124 ms |
| Aug 22, 2026 | 122 ms |
| Aug 29, 2026 | 122 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 117 ms |
| Sep 19, 2026 | 120 ms |
| Sep 26, 2026 | 125 ms |
| Oct 3, 2026 | 127 ms |
| Oct 10, 2026 | 135 ms |
| Oct 17, 2026 | 136 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
Speed
Use efficient cache lifetimes
2.9 s · 4.3 MB202 files are served with short cache lifetimes, so returning visitors download them again (4.3 MB).
Render-blocking requests
6.0 s89 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.0 s.
Reduce unused CSS
1.1 s · 240 KiBAbout 240 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 43
43/100Your mobile performance score is 43 (desktop: 64). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.5 s
A phone's processor spends 5.5 s on main-thread work while loading, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, stape.io and Other Google APIs/SDKs and others), adding 3.8 MB and 1.8 s of main-thread time.
Reduce unused JavaScript
300 ms · 1.9 MBAbout 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google CDN adds 999 ms
999 msGoogle CDN costs a phone 999 ms of main-thread work and 2.6 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.
Improve image delivery
1.0 MB11 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
500 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).
stape.io adds 377 ms
377 msstape.io costs a phone 377 ms of main-thread work and 543 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.
2,834 HTML elements
The page has 2,834 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Other Google APIs/SDKs adds 206 ms
206 msOther Google APIs/SDKs costs a phone 206 ms of main-thread work and 316 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 147 ms. During a long task the page ignores taps.
Minify JavaScript
14 KiB14 KiB could be saved by minifying JavaScript.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 233 ms
233 msYour server sent the HTML in 233 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.
Real-user LCP: 5.1 s
5.1 sReal visitors wait 5.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.6 s
4.6 sReal visitors see the first content after 4.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.1 s
3.1 sReal visitors wait 3.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 41.7 s
41.7 sThe page becomes fully interactive after 41.7 s. Good is under 3.8 s.
Speed Index: 13.5 s
13.5 sVisually, the page fills in at 13.5 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 6.6 s
6.6 sYour largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We save lives by training animals to help rid the world of …”. Most of its time is resource load delay (3.8 s).
First Contentful Paint: 4.7 s
4.7 sThe first text or image appears after 4.7 s on a phone. Good is under 1.8 s.
Total Blocking Time: 603 ms
603 msScripts block taps and scrolling for 603 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 117 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.6 s to 5.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 133 ms
133 msReal visitors wait 133 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.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 9.7 MB in 268 requests
9.7 MBYour homepage downloads 9.7 MB in 268 requests on a phone: scripts 4.6 MB (120), images 2.7 MB (23) and other files 1.0 MB (17). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (42 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.
5 images below the first screen load straight away
5 images further down the page (136 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.7 g of CO₂ per visit
2.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.74 g of CO₂e: 328.9 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
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
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.
16 links without text
16 visible links have no text or label, so screen readers cannot say where they go.
11 form fields without a label
11 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
43 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: 43 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
112 internal links, 13 external
The homepage links to 112 pages on apopo.org and 13 external pages.
7 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Discover how APOPO's scent detection animals, known as HeroRATs and HeroDOGs, help rid the world of the scourge of land…”.
Title: 38 characters
Your title is a healthy 38 characters: “Training Animals To Save Lives • APOPO”.
Canonical URL set
The canonical URL is https://apopo.org/.
Structured data in place
Structured data found: AnimalShelter, Article, ImageObject, Organization and Person.
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://apopo.org/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://apopo.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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (664 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 84 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
4 small tap targets
4 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://apopo.org' has been blocked by…”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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.
Thin social proof
Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 477 words of copy
The homepage carries about 477 words of visible text.
4 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Shop”, “Newsletter Signup” and “Contact us”.
3 short forms
3 short forms (5 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics and Plausible.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
18 cookies set on arrival
18Opening the homepage sets 18 cookies (measured from a US location before any click).
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.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 apopo.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
- Vue.js
- E-commerce
- WooCommerce
- Analytics
- Google Analytics | Plausible
Company
- Founded
- 1997
- Headquarters
- Morogoro
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on apopo.org, including 22 speed issues, 1 SEO issue 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.