terrycycling.com website review

About 246 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

32 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

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

8 third-party services load with your homepage (replocdn.com, Shopify and userway.org and others), adding 1.3 MB and 573 ms of main-thread time.

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

Polyfills for old browsers add 49 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

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

replocdn.com costs a phone 238 ms of main-thread work and 399 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,679 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Shopify costs a phone 139 ms of main-thread work and 644 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.

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

About 11 KiB of CSS is downloaded but never applied on this page.

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.

3 KiB could be saved by minifying JavaScript.

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 visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.

Your largest element takes 18.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Your Season Isn’t Over”.

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

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

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

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

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

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

The first text or image appears after 2.1 s on a phone. Good is under 1.8 s.

Your homepage downloads 5.0 MB in 387 requests on a phone: images 2.2 MB (50), scripts 1.3 MB (137) and other files 1.0 MB (161). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (7 elements).

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

6 links have no real href, so search engines can't follow them.

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

The homepage links to 184 pages on terrycycling.com and 4 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.

There is no https://terrycycling.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.

https://terrycycling.com/collections/promotion-events and https://terrycycling.com/collections/pro-deal-monday have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage has only about 10 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.