Website review, no card needed

journeys.com logo

journeys.com website review

Visit site (opens in a new tab)Reviewed 12 October 202621 issues · 53 checks

This review found 21 issues worth fixing on journeys.com, 7 of them high impact, across 53 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.7 sApr 18Oct 31.7 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.7 s
Apr 25, 20261.7 s
May 2, 20261.7 s
May 9, 20261.7 s
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
251 ms198 msApr 18Oct 3245 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026204 ms
Apr 25, 2026208 ms
May 2, 2026211 ms
May 9, 2026212 ms
May 16, 2026212 ms
May 23, 2026212 ms
May 30, 2026213 ms
Jun 6, 2026219 ms
Jun 13, 2026221 ms
Jun 20, 2026227 ms
Jun 27, 2026229 ms
Jul 4, 2026230 ms
Jul 11, 2026232 ms
Jul 18, 2026231 ms
Jul 25, 2026233 ms
Aug 1, 2026237 ms
Aug 8, 2026238 ms
Aug 15, 2026239 ms
Aug 22, 2026238 ms
Aug 29, 2026237 ms
Sep 5, 2026235 ms
Sep 12, 2026232 ms
Sep 19, 2026235 ms
Sep 26, 2026238 ms
Oct 3, 2026245 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

No screenshot is available for this review.

Speed

Not measured in this review.

Core Web Vitals

2 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user INP: 248 ms

    248 ms

    Real visitors wait 248 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 17% slower for real visitors

    +17%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 204 ms to 245 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

    Real visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.08

    0.08

    For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

    Real visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 335 ms

    335 ms

    Real visitors wait 335 ms for your server to start answering (75th percentile). Good is under 800 ms.

Images and page weight

4 to fix43
  • Page weight: 8.2 MB

    8.2 MB

    Your homepage downloads 8.2 MB on a phone, 4.1 MB of it images (50%). Under 2 MB keeps phones on slow connections fast.

  • 15 images in older formats

    15 images (2.5 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.

  • 9 images below the first screen load straight away

    9 images further down the page (996 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 5 images far larger than shown

    455 KiB

    5 images are downloaded at several times the size a phone draws them, for example pfbMU.jpg at 700 px wide, shown at 181 px. Resized copies would save about 455 KiB.

  • About 2.3 g of CO₂ per visit

    2.32 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.32 g of CO₂e: 278.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

7 to fix90
  • Required ARIA attributes must be provided (5 elements)

    Required ARIA attributes must be provided: 5 elements on the page fail this check, rated critical by axe-core.

  • 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 names (1 element)

    ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.

  • 17 tap targets too small

    17 tap targets are too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (13 elements)

    All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.

  • 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.

2 checks passed
  • Every image has alt text

    All 44 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fix91
  • Meta description is long (187 characters)

    Your meta description is 187 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: missing name”.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • 212 internal links, 10 external

    The homepage links to 212 pages on journeys.com and 10 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Footwear for Men, Women, and Kids. Boots and Sneakers from UGG, Adidas, and More at Journeys Shoes.”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Journeys Shoes | Sneakers, Boots, Slides & Trendy Footwear”.

  • Canonical URL set

    The canonical URL is https://www.journeys.com/.

  • 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.journeys.com/sitemap_xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 6 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed
  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives url, logo, sameAs (social profiles) and contact details; name and description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,022 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes /llms.txt (11 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 80 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

3 to fix71
  • 9 broken images

    9 images failed to load on a phone, for example https://mnrddc.journeys.com/g/uids?pld=yiSJAnmqikB3RkeRnGA0gZiz5oAJXT67or5riHx-DmNaD3fmuR1X3NhL4CQMDgq5NvVp_8IW2E-ixdzJ98LVhRMXuBsTFeVdyL-NymW17Jdef0giYdFCQr0hZlO7SjjHB3hHN5D4ZCW1MWxXUkwC1CQq1IUhwfBZQ.

  • 50 small tap targets

    50 of 127 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 9-field form

    Your longest form asks for 9 fields (8 required). Every extra field lowers completion.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 803 words of copy

    The homepage carries about 803 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: “Order Tracking” and “Join Rewards for Free”.

  • 28 calls to action

    The homepage has 28 calls to action, for example “Order Tracking”, “Shop By Shoe Size” and “Shop All”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Criteo, Google Tag Manager, Meta Pixel, Microsoft Ads and Snap Pixel and 1 more (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.

  • 34 cookies set on arrival

    34

    Opening the homepage sets 34 cookies (measured from a US location before any click).

  • 68 other companies contacted

    Loading the homepage contacts 68 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: TrustArc

    A consent management tool (TrustArc) 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 journeys.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on journeys.com, including 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25