Website review, no card needed
ridingculture.com website review
Visit site (opens in a new tab)Reviewed 16 November 202637 issues · 85 checks
This review found 37 issues worth fixing on ridingculture.com, 9 of them high impact, across 85 checks. The most urgent: page weight: 33.0 MB in 229 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
87B- #8,084 of 116,487 reviewed websitesbeats 90%
- #4,750 of 66,776 online storesbeats 89%
- #4,609 of 60,929 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
| Nov 7, 2026 | 1.2 s |
| Nov 14, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 91 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 96 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 97 ms |
| Jul 18, 2026 | 95 ms |
| Jul 25, 2026 | 95 ms |
| Aug 1, 2026 | 95 ms |
| Aug 8, 2026 | 96 ms |
| Aug 15, 2026 | 104 ms |
| Aug 22, 2026 | 109 ms |
| Aug 29, 2026 | 113 ms |
| Sep 5, 2026 | 114 ms |
| Sep 12, 2026 | 117 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 120 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 115 ms |
| Oct 17, 2026 | 120 ms |
| Oct 24, 2026 | 123 ms |
| Oct 31, 2026 | 127 ms |
| Nov 7, 2026 | 127 ms |
| Nov 14, 2026 | 119 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.8 s
1.6 s
2.4 s
3.2 s
4.0 s
4.8 s
5.6 s
6.4 s
Speed
Shopify adds 1.1 s
1.1 sShopify costs a phone 1.1 s of main-thread work and 207 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.
5,347 HTML elements
The page has 5,347 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 2.3 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 (Shopify, Google Tag Manager and Klaviyo and others), adding 1.1 MB and 1.7 s of main-thread time.
Mobile performance score: 68
68/100Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
405 KiBAbout 405 KiB of JavaScript is downloaded but never used on this page.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 315 ms. During a long task the page ignores taps.
Google Tag Manager adds 270 ms
270 msGoogle Tag Manager costs a phone 270 ms of main-thread work and 249 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.
Use efficient cache lifetimes
269 KiB16 files are served with short cache lifetimes, so returning visitors download them again (269 KiB).
Klaviyo adds 142 ms
142 msKlaviyo costs a phone 142 ms of main-thread work and 309 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.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Reduce unused CSS
41 KiBAbout 41 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Minify JavaScript
11 KiB11 KiB could be saved by minifying JavaScript.
Improve image delivery
7 KiB1 image could be 7 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
1 checks passed
Server response: 65 ms
65 msYour server sent the HTML in 65 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 13.5 s
13.5 sThe page becomes fully interactive after 13.5 s. Good is under 3.8 s.
Total Blocking Time: 987 ms
987 msScripts block taps and scrolling for 987 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 37% slower for real visitors
+37%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 91 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 2.6 s
2.6 sYour largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DURABLE RIDING GEAR”. Most of its time is element render delay (1.2 s).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 119 ms
119 msReal visitors wait 119 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 419 ms
419 msReal visitors wait 419 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.018
0.018The layout barely moves while loading (CLS 0.018, good is under 0.1).
Images and page weight
Page weight: 33.0 MB in 229 requests
33.0 MBYour homepage downloads 33.0 MB in 229 requests on a phone: media 30.0 MB (2), scripts 1.2 MB (85) and other files 716 KiB (86). Under 2 MB keeps phones on slow connections fast.
About 9.3 g of CO₂ per visit
9.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 9.34 g of CO₂e: 1121.3 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
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.ridingculture.com/sitemap.xml, so Google discovers your pages only by following links.
188 internal links, 6 external
The homepage links to 188 pages on ridingculture.com and 6 external pages.
6 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “Casual looks with protection and lifestyle design. ✓abrasion-resistant protective clothing ✓developed with athletes ✓ce…”.
One H1 headline
Your main headline reads: “RIDING CULTURE”.
Title: 54 characters
Your title is a healthy 54 characters: “abrasion-resistant motorcycle, MTB and skater clothing”.
Canonical URL set
The canonical URL is https://www.ridingculture.com/en-us.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, 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.ridingculture.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,428 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages share a title
https://www.ridingculture.com/en-us, https://www.ridingculture.com/en and / all use the title “abrasion-resistant motorcycle, MTB and skater clothing”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://www.ridingculture.com/en-us/pages/hilfe-kontakt-1, https://www.ridingculture.com/en-us/pages/uber-uns and https://www.ridingculture.com/en-us/blogs/riding-culture-magazine have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.ridingculture.com/en and / use the same meta description. A description written for each page earns more clicks.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.ridingculture.com/en, whose canonical is https://www.ridingculture.com/en-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://www.ridingculture.com/pages/usa-shipment, https://www.ridingculture.com/en-us/pages/hilfe-kontakt-1 and https://www.ridingculture.com/en-us/pages/uber-uns have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 75 found) and read each the way a search engine does.
3 checks passed
Linked pages load
6 pages of 15 loaded without an error (the rest turned automated requests away).
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 6 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
85 of 106 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.
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: “Over 10,000 satisfied customers”. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 1,966 words of copy
The homepage carries about 1,966 words of visible text.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Help & Contact”, “Subscribe” and “Contact”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Klaviyo (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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies, 2 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
27 other companies contacted
Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 ridingculture.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on ridingculture.com, including 16 speed issues, 2 SEO issues and 6 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.