Website review, no card needed
a21.org website review
Visit site (opens in a new tab)Reviewed 19 October 202663 issues · 96 checks
This review found 63 issues worth fixing on a21.org, 24 of them high impact, across 96 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 4.0 s |
| May 2, 2026 | 3.9 s |
| May 9, 2026 | 3.9 s |
| May 16, 2026 | 3.8 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 3.8 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.8 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 4.1 s |
| Aug 22, 2026 | 4.2 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.3 s |
| Sep 12, 2026 | 4.5 s |
| Sep 19, 2026 | 4.4 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 204 ms |
| May 2, 2026 | 197 ms |
| May 9, 2026 | 196 ms |
| May 16, 2026 | 196 ms |
| May 23, 2026 | 182 ms |
| May 30, 2026 | 184 ms |
| Jun 6, 2026 | 189 ms |
| Jun 13, 2026 | 194 ms |
| Jun 20, 2026 | 192 ms |
| Jun 27, 2026 | 197 ms |
| Jul 4, 2026 | 195 ms |
| Jul 11, 2026 | 196 ms |
| Jul 18, 2026 | 206 ms |
| Jul 25, 2026 | 196 ms |
| Aug 1, 2026 | 193 ms |
| Aug 8, 2026 | 185 ms |
| Aug 15, 2026 | 180 ms |
| Aug 22, 2026 | 192 ms |
| Aug 29, 2026 | 205 ms |
| Sep 5, 2026 | 227 ms |
| Sep 12, 2026 | 215 ms |
| Sep 19, 2026 | 220 ms |
| Sep 26, 2026 | 230 ms |
| Oct 3, 2026 | 236 ms |
| Oct 10, 2026 | 246 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
1.6 s · 8.3 MB105 files are served with short cache lifetimes, so returning visitors download them again (8.3 MB).
Render-blocking requests
5.7 s34 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.7 s.
Google CDN adds 1.9 s
1.9 sGoogle CDN costs a phone 1.9 s of main-thread work and 3.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 13.6 s
A phone's processor spends 13.6 s on main-thread work while loading, 9.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 18
18/100Your mobile performance score is 18 (desktop: 64). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Facebook and others), adding 5.3 MB and 4.4 s of main-thread time.
Reduce unused JavaScript
2.8 MBAbout 2.8 MB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 870 ms
870 msGoogle Tag Manager costs a phone 870 ms of main-thread work and 819 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
850 ms · 88 KiBAbout 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 850 ms faster on a phone.
Improve image delivery
697 KiB9 images could be 697 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
600 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 581 ms. During a long task the page ignores taps.
Facebook adds 484 ms
484 msFacebook costs a phone 484 ms of main-thread work and 252 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.
Stripe adds 407 ms
407 msStripe costs a phone 407 ms of main-thread work and 272 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.
Other Google APIs/SDKs adds 318 ms
318 msOther Google APIs/SDKs costs a phone 318 ms of main-thread work and 284 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,391 HTML elements
The page has 2,391 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
240 ms · 7 KiB7 KiB could be saved by minifying CSS.
Minify JavaScript
150 ms · 3 KiB3 KiB could be saved by minifying JavaScript.
Legacy JavaScript
78 KiBPolyfills for old browsers add 78 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 64 but mobile only 18. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 16 ms
16 msYour server sent the HTML in 16 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: 4.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.7 s
3.7 sReal visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 27.5 s
27.5 sVisually, the page fills in at 27.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 77.3 s
77.3 sThe page becomes fully interactive after 77.3 s. Good is under 3.8 s.
Total Blocking Time: 3.3 s
3.3 sScripts block taps and scrolling for 3.3 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 5.8 s
5.8 sThe first text or image appears after 5.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 6.5 s
6.5 sYour largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Abolish Slavery Everywhere, Forever.”. Most of its time is element render delay (2.8 s).
Real-user INP: 237 ms
237 msReal visitors wait 237 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 204 ms to 246 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.212
0.212The layout shifts by 0.212 while loading, so content jumps under the reader's thumb. Good is under 0.1.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 4.0 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 16.5 MB in 245 requests
16.5 MBYour homepage downloads 16.5 MB in 245 requests on a phone: scripts 7.1 MB (75), images 6.3 MB (62) and other files 1.5 MB (58). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.0 MB together. On a phone connection a single image that size takes seconds.
23 images in older formats
23 images (5.8 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.
12 images below the first screen load straight away
12 images further down the page (2.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
76 KiB1 image is downloaded at several times the size a phone draws it, for example GFS2025-fundraising-campaign-fundraise-sm.jpg at 1,220 px wide, shown at 311 px. Resized copies would save about 76 KiB.
About 4.7 g of CO₂ per visit
4.68 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.68 g of CO₂e: 561.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
Unlabelled dropdowns
1 dropdown has no label.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
18 images without alt text
18 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (43 elements)
All page content should be contained by landmarks: 43 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.
16 form fields without a label
16 form fields have no label, so screen readers announce an empty box and autofill guesses.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 12 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (10 characters)
Your title is only 10 characters: “Home | A21”. 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.
3 H1 headlines
There are 3 <h1> headlines (“Abolish Slavery Everywhere, Forever.”, “Abolish Slavery Everywhere, Forever.” and “Join the movement toend human trafficking”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (211 characters)
Your meta description is 211 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://www.a21.org/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at a21.org/robots.txt, the first file search crawlers ask for.
12 links crawlers can't follow
12 links have no real href, so search engines can't follow them.
74 internal links, 4 external
The homepage links to 74 pages on a21.org and 4 external pages.
1 checks passed
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.a21.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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (3,904 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 38 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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
4 distorted images
4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
15 of 16 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: 2 trust badges. 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.
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 1,073 words of copy
The homepage carries about 1,073 words of visible text.
4 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Shop”, “Join The Fight” and “Contact Us”.
1 short form
A short form (6 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
13 cookies set on arrival
13Opening 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.
37 other companies contacted
Loading the homepage contacts 37 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 a21.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
Company
- Founded
- 2008
- Headquarters
- Baulkham Hills
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 63 issues on a21.org, including 29 speed issues, 8 SEO issues and 4 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.