Website review, no card needed
aleo.org website review
Visit site (opens in a new tab)Reviewed 19 October 202631 issues · 79 checks
This review found 31 issues worth fixing on aleo.org, 9 of them high impact, across 79 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
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 2.4 s |
| May 2, 2026 | 2.5 s |
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 4.2 s |
| Sep 5, 2026 | 4.2 s |
| Sep 12, 2026 | 4.1 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.9 s |
| Oct 3, 2026 | 3.9 s |
| Oct 10, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 149 ms |
| May 2, 2026 | 145 ms |
| May 9, 2026 | 144 ms |
| May 16, 2026 | 152 ms |
| May 23, 2026 | 148 ms |
| May 30, 2026 | 177 ms |
| Jun 6, 2026 | 155 ms |
| Jun 13, 2026 | 147 ms |
| Jun 20, 2026 | 162 ms |
| Jun 27, 2026 | 150 ms |
| Jul 4, 2026 | 163 ms |
| Jul 11, 2026 | 176 ms |
| Jul 18, 2026 | 179 ms |
| Jul 25, 2026 | 191 ms |
| Aug 1, 2026 | 198 ms |
| Aug 8, 2026 | 218 ms |
| Aug 15, 2026 | 218 ms |
| Aug 22, 2026 | 205 ms |
| Aug 29, 2026 | 188 ms |
| Sep 5, 2026 | 168 ms |
| Sep 12, 2026 | 166 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 178 ms |
| Oct 3, 2026 | 179 ms |
| Oct 10, 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
Speed
Render-blocking requests
1.7 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Improve image delivery
700 ms · 950 KiB4 images could be 950 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
Mobile performance score: 70
70/100Your mobile performance score is 70 (desktop: 91). Pages that score under 90 lose visitors before the first paint.
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 378 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
6 third-party services on the page
6 third-party services load with your homepage (Matomo, Twitter Online Conversion Tracking and LinkedIn Ads and others), adding 144 KiB and 224 ms of main-thread time.
Reduce unused JavaScript
150 ms · 48 KiBAbout 48 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 18 KiB3 files are served with short cache lifetimes, so returning visitors download them again (18 KiB).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 95 ms. During a long task the page ignores taps.
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.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 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.9 s
4.9 sReal visitors wait 4.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 9.2 s
9.2 sYour largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Move money anywhere in the world in seconds, for less than …”.
Time to Interactive: 9.4 s
9.4 sThe page becomes fully interactive after 9.4 s. Good is under 3.8 s.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 149 ms to 179 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 57% slower for real visitors
+57%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.4 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 809 ms
809 msReal visitors wait 809 ms for your server to start answering (75th percentile). Good is under 800 ms.
36 images without width and height
36 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
5 checks passed
Real-user INP: 196 ms
196 msReal visitors wait 196 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
1 image far larger than shown
94 KiB1 image is downloaded at several times the size a phone draws it, for example stablecoin-whitepaper-banner.jpg at 1,500 px wide, shown at 318 px. Resized copies would save about 94 KiB.
1 image in older formats
1 image (158 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.
2 images below the first screen load straight away
2 images further down the page (65 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 51.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.5 MB in 49 requests
1.5 MBYour homepage downloads 1.5 MB in 49 requests on a phone: images 1.1 MB (24), scripts 188 KiB (9) and fonts 138 KiB (4). That is a lean page.
Accessibility
19 text elements with low contrast
19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
<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.
All page content should be contained by landmarks (53 elements)
All page content should be contained by landmarks: 53 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.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h1 → h3), 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. (5 elements).
2 checks passed
Every image has alt text
All 43 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (207 characters)
Your meta description is 207 characters; Google truncates after about 160, so the end of your pitch is cut.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
34 internal links, 21 external
The homepage links to 34 pages on aleo.org and 21 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Private StablecoinPayments.”.
Title: 33 characters
Your title is a healthy 33 characters: “Aleo: Private Stablecoin Payments”.
Canonical URL set
The canonical URL is https://www.aleo.org/.
Structured data in place
Structured data found: BreadcrumbList.
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://aleo.org/sitemap-index.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://aleo.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 (832 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages without a title
https://aleo.org/post/private-usdcx-ledger, https://aleo.org/post/stablecoin-privacy-paper, https://aleo.org/usdcx, https://aleo.org/post/usdcx-case-study, https://aleo.org/usad and https://aleo.org/post/usad-case-study and 6 others have no <title>, so Google invents the link text in results.
2 pages share a meta description
https://aleo.org/usdcx and https://aleo.org/usad use the same meta description. A description written for each page earns more clicks.
12 pages without an H1
https://aleo.org/post/private-usdcx-ledger, https://aleo.org/post/stablecoin-privacy-paper, https://aleo.org/usdcx, https://aleo.org/post/usdcx-case-study, https://aleo.org/usad and https://aleo.org/post/usad-case-study and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 25 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.
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
5 of 5 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 33 customer or partner logos. 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 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 743 words of copy
The homepage carries about 743 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “TALK TO AN EXPERT”.
4 calls to action
The homepage has 4 calls to action, for example “Talk to An Expert”, “Learn More→” and “Subscribe”.
3 short forms
3 short forms (5 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Matomo and LinkedIn Insight.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads LinkedIn Insight and X (Twitter) Ads (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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
10 other companies contacted
Loading the homepage contacts 10 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 aleo.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
- Gatsby
- Analytics
- Matomo
- Hosting
- Netlify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on aleo.org, including 14 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.