shopjourney.com website review

A phone's processor spends 6.3 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, ContentSquare and rebuyengine.com and others), adding 2.0 MB and 1.4 s of main-thread time.

Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.

12 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

35 files are served with short cache lifetimes, so returning visitors download them again (473 KiB).

About 180 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

Google Tag Manager costs a phone 324 ms of main-thread work and 353 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.

The page has 2,363 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

rebuyengine.com costs a phone 182 ms of main-thread work and 329 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.

Klaviyo costs a phone 163 ms of main-thread work and 403 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.

14 long tasks block the main thread while loading, the longest for 228 ms. During a long task the page ignores taps.

6 images could be 111 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 88 KiB JavaScript that modern phones do not need.

24 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB JavaScript is shipped twice across bundles.

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.

Your largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We and our partners, including Shopify, use cookies and oth…”.

The page becomes fully interactive after 28.5 s. Good is under 3.8 s.

Scripts block taps and scrolling for 711 ms in total while the page loads. Good is under 200 ms.

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

Visually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.

1 image have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 5.2 MB in 417 requests on a phone: scripts 2.5 MB (144), images 1.0 MB (59) and other files 925 KiB (138). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (32 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Elements must only use permitted ARIA attributes: 6 elements on the page fail this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

3 visible links have no text or label, so screen readers cannot say where they go.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 70 characters, so Google will cut it off around 60: “Power Chairs, Upright Rollators and Mobility Scooters | Journey Health”.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 130 pages on shopjourney.com and 13 external pages.

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.

https://www.shopjourney.com/pages/shipping-delivery, https://www.shopjourney.com/pages/contact, https://www.shopjourney.com/products/journey-air-elite, https://www.shopjourney.com/products/zoomer-electric-mobility-chair, https://www.shopjourney.com/products/so-lite-c2-ultra-lightweight-wheelchair and https://www.shopjourney.com/collections/power-chair-parts-accessories and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.shopjourney.com/collections/power-chair-parts-accessories and https://www.shopjourney.com/products/perfect-sleep-chair have 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.

We fetched 15 pages linked from your homepage (of 63 found) and read each the way a search engine does.

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=5012831&tm=gtm002&Ver=2&mid=bf71140e-d205-4787-810d-dcaa2691a2e3&bo=2&sid=637854c0d9f111f1872807ef0f5dcdb4&vid=63787fc0d9f111f1a6349d47f8e75552&vids=1&msclkid=N&pi=918.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

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.

The homepage shows no opening hours. If customers visit or call, show when.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 967 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 4 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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