runnersplus.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Shopify and others), adding 1,002 KiB and 947 ms of main-thread time.

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

6 images could be 229 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

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

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

About 403 KiB of JavaScript is downloaded but never used on this page.

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

Google CDN costs a phone 219 ms of main-thread work and 300 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.

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

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

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

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

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

Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

Your homepage downloads 3.1 MB in 237 requests on a phone: scripts 1.2 MB (72), images 826 KiB (74) and other files 636 KiB (68). Under 2 MB keeps phones on slow connections fast.

Mount_to_Coast_BITR_H1_Pre-Sale.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Alternative text of images should not be repeated as text: 11 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 12 characters: “Runners Plus”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 348 pages on runnersplus.com and 37 external pages.

Your Organization JSON-LD is missing logo, 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.

https://www.runnersplus.com/pages/track-field and https://www.runnersplus.com/collections/track-field all use the title “Track & Field – Runners Plus”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.runnersplus.com/pages/track-field, https://www.runnersplus.com/collections/women, https://www.runnersplus.com/collections/womens-sale, https://www.runnersplus.com/collections/womens-road-running, https://www.runnersplus.com/collections/womens-shoes-trail and https://www.runnersplus.com/collections/x-country and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.runnersplus.com/pages/track-field, https://www.runnersplus.com/collections/womens-sale, https://www.runnersplus.com/collections/womens-road-running, https://www.runnersplus.com/collections/womens-shoes-trail, https://www.runnersplus.com/collections/x-country and https://www.runnersplus.com/collections/womens-x-training and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.runnersplus.com/collections/womens-sale 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.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97231661&Ver=2&mid=42d7d23b-a79f-4927-ba0c-01863a6c66b5&bo=1&sid=04f15bd0dce511f18f1a8d4b027e71f4&vid=04f18cf0dce511f1841643808f9a8411&vids=1&msclkid=N&pi=918639831&lg.

3 errors were logged to the browser console while the page loaded, for example “pageloadSnippet is not defined”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 517 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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.

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

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.

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