Website review, no card needed
alltrails.com website review
Visit site (opens in a new tab)Reviewed 11 October 202635 issues · 82 checks
This review found 35 issues worth fixing on alltrails.com, 11 of them high impact, across 82 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 1.8 s |
| Apr 25, 2026 | 1.8 s |
| May 2, 2026 | 1.7 s |
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 205 ms |
| Apr 25, 2026 | 205 ms |
| May 2, 2026 | 204 ms |
| May 9, 2026 | 203 ms |
| May 16, 2026 | 205 ms |
| May 23, 2026 | 203 ms |
| May 30, 2026 | 203 ms |
| Jun 6, 2026 | 205 ms |
| Jun 13, 2026 | 208 ms |
| Jun 20, 2026 | 213 ms |
| Jun 27, 2026 | 219 ms |
| Jul 4, 2026 | 223 ms |
| Jul 11, 2026 | 229 ms |
| Jul 18, 2026 | 234 ms |
| Jul 25, 2026 | 227 ms |
| Aug 1, 2026 | 216 ms |
| Aug 8, 2026 | 208 ms |
| Aug 15, 2026 | 202 ms |
| Aug 22, 2026 | 199 ms |
| Aug 29, 2026 | 197 ms |
| Sep 5, 2026 | 192 ms |
| Sep 12, 2026 | 183 ms |
| Sep 19, 2026 | 177 ms |
| Sep 26, 2026 | 171 ms |
| Oct 3, 2026 | 169 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.6 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
cloudfront.net adds 1.4 s
1.4 scloudfront.net costs a phone 1.4 s of main-thread work and 487 KiB 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.
Mobile performance score: 48
48/100Your mobile performance score is 48 (desktop: 48). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 2.9 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 (cloudfront.net, captcha-delivery.com and Google Tag Manager and others), adding 1.4 MB and 2.1 s of main-thread time.
Improve image delivery
450 ms · 1.4 MB13 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Use efficient cache lifetimes
600 ms · 598 KiB23 files are served with short cache lifetimes, so returning visitors download them again (598 KiB).
Reduce unused JavaScript
450 ms · 556 KiBAbout 556 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Legacy JavaScript
300 ms · 59 KiBPolyfills for old browsers add 59 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
captcha-delivery.com adds 301 ms
301 mscaptcha-delivery.com costs a phone 301 ms of main-thread work and 270 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.
1,810 HTML elements
The page has 1,810 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Tag Manager adds 89 ms
89 msGoogle Tag Manager costs a phone 89 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 203 ms. During a long task the page ignores taps.
Reduce unused CSS
22 KiBAbout 22 KiB of CSS is downloaded but never applied on this page.
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.
Duplicated JavaScript
3 KiB3 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 19.3 s
19.3 sThe page becomes fully interactive after 19.3 s. Good is under 3.8 s.
Largest Contentful Paint: 6.8 s
6.8 sYour largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A hiker seen from behind, walking on a trail surrounded by …”.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.207
0.207The layout shifts by 0.207 while loading, so content jumps under the reader's thumb. Good is under 0.1.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s 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: 128 ms
128 msReal visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 666 ms
666 msReal visitors wait 666 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 205 ms to 169 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 194 ms
194 msScripts block the page for only 194 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.0 MB in 139 requests
4.0 MBYour homepage downloads 4.0 MB in 139 requests on a phone: images 1.9 MB (24), scripts 1.8 MB (51) and fonts 151 KiB (3). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.13 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.13 g of CO₂e: 135.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
[aria-*] attributes do not have valid values
[aria-*] attributes do not have valid values (1 element).
1 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
SEO
Title is long (75 characters)
Your title is 75 characters, so Google will cut it off around 60: “AllTrails: Trail Guides & Maps for Hiking, Camping, and Running | AllTrails”.
Meta description is long (174 characters)
Your meta description is 174 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
542 internal links, 16 external
The homepage links to 542 pages on alltrails.com and 16 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Find your next adventure”.
Canonical URL set
The canonical URL is https://www.alltrails.com/.
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://www.alltrails.com/sitemap/secure/rails/index.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.alltrails.com/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,820 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.alltrails.com/trip-assistant is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://www.alltrails.com/partner-collections/florida-favorites-scenic-trails-locals-love and https://www.alltrails.com/partner-collections/going-ultralight-backpacking-rei have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.alltrails.com/trip-assistant and https://www.alltrails.com/explore use the same meta description. A description written for each page earns more clicks.
12 pages without an H1
https://www.alltrails.com/trip-assistant, https://www.alltrails.com/explore, https://www.alltrails.com/partner-collections/8-trails-that-reflect-americas-tribal-and-indigenous-heritage, https://www.alltrails.com/partner-collections/heart-of-the-beast-dog-friendly-trails, https://www.alltrails.com/partner-collections/adventures-for-better-health and https://www.alltrails.com/partner-collections/destination-canadas-must-hike-trails and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.alltrails.com/explore has 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 198 found) and read each the way a search engine does.
4 checks passed
Linked pages load
12 pages of 15 loaded without an error (the rest turned automated requests away).
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.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
16 of 17 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.
Thin social proof
Social proof on the homepage: 15 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 558 words of copy
The homepage carries about 558 words of visible text.
2 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Learn more”, “Torrey Pines State Natural Reserve” and “Point Lobos State Natural Reserve”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and TikTok Pixel.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 5 mores (measured from a US location before any click). A consent tool (Osano) is installed; check it blocks these until visitors agree where the law requires it.
26 cookies set on arrival
26Opening the homepage sets 26 cookies (measured from a US location before any click).
47 other companies contacted
Loading the homepage contacts 47 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Osano
A consent management tool (Osano) 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 alltrails.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Analytics
Hiring
- Hiring
- 1 open role
- Teams
- Marketing (1)
- Job board
- lever
- Careers page
- jobs.lever.co/alltrails (opens in a new tab)
Company
- Founded
- 2010
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 alltrails.com, including 18 speed issues, 4 SEO issues and 3 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.