Website review, no card needed
weareonecomposites.com website review
Visit site (opens in a new tab)Reviewed 12 November 202630 issues · 79 checks
This review found 30 issues worth fixing on weareonecomposites.com, 5 of them high impact, across 79 checks. The most urgent: 2 text elements with low contrast. 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
90A- #2,152 of 104,351 reviewed websitesbeats 97%
- #1,052 of 58,388 online storesbeats 97%
- #1,019 of 53,173 Shopify storesbeats 97%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.1 s |
| Oct 31, 2026 | 1.2 s |
| Nov 7, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 98 ms |
| May 30, 2026 | 97 ms |
| Jun 6, 2026 | 95 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 99 ms |
| Jul 18, 2026 | 99 ms |
| Jul 25, 2026 | 98 ms |
| Aug 1, 2026 | 98 ms |
| Aug 8, 2026 | 98 ms |
| Aug 15, 2026 | 99 ms |
| Aug 22, 2026 | 96 ms |
| Aug 29, 2026 | 100 ms |
| Sep 5, 2026 | 103 ms |
| Sep 12, 2026 | 104 ms |
| Sep 19, 2026 | 105 ms |
| Sep 26, 2026 | 107 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 104 ms |
| Oct 24, 2026 | 101 ms |
| Oct 31, 2026 | 104 ms |
| Nov 7, 2026 | 104 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.6 s
1.2 s
1.7 s
2.3 s
2.9 s
3.5 s
4.1 s
4.6 s
Speed
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Shopify and others), adding 2.0 MB and 976 ms of main-thread time.
Mobile performance score: 84
84/100Your mobile performance score is 84. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
919 KiBAbout 919 KiB of JavaScript is downloaded but never used on this page.
YouTube adds 384 ms
384 msYouTube costs a phone 384 ms of main-thread work and 1,005 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.
Render-blocking requests
300 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 218 ms
218 msGoogle Tag Manager costs a phone 218 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.
Shopify adds 133 ms
133 msShopify costs a phone 133 ms of main-thread work and 328 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
200 KiB11 files are served with short cache lifetimes, so returning visitors download them again (200 KiB).
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 157 ms. During a long task the page ignores taps.
Reduce unused CSS
141 KiBAbout 141 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need.
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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 19.4 s
19.4 sThe page becomes fully interactive after 19.4 s. Good is under 3.8 s.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 295 ms
295 msScripts block taps and scrolling for 295 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 98 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 1.9 s
1.9 sYour largest element renders in 1.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “INNOVATION IN EVERY LAYER, EXPERIENCE IN EVERY RIDE.”.
Cumulative Layout Shift: 0.034
0.034The layout barely moves while loading (CLS 0.034, good is under 0.1).
Images and page weight
Page weight: 3.3 MB in 216 requests
3.3 MBYour homepage downloads 3.3 MB in 216 requests on a phone: scripts 2.1 MB (81), other files 774 KiB (112) and fonts 142 KiB (4). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.93 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.93 g of CO₂e: 111.9 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
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 7 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (306 characters)
Your meta description is 306 characters; Google truncates after about 160, so the end of your pitch is cut.
74 internal links, 12 external
The homepage links to 74 pages on weareonecomposites.com and 12 external pages.
6 checks passed
One H1 headline
Your main headline reads: “We Are One Composites”.
Title: 64 characters
Your title is a healthy 64 characters: “We Are One Composites - Carbon Fibre Mountain Bike Rims & Wheels”.
Canonical URL set
The canonical URL is https://www.weareonecomposites.com/en-us.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.weareonecomposites.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
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.
llms.txt published
The site publishes https://www.weareonecomposites.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.weareonecomposites.com/en-us and https://www.weareonecomposites.com/en-us/products/coup-rim all use the title “We Are One Composites - Carbon Fibre Mountain Bike Rims & Wheels”. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://www.weareonecomposites.com/en-us/collections/xc-carbon-wheelsets, https://www.weareonecomposites.com/en-us/products/whisp-xc, https://www.weareonecomposites.com/en-us/collections/xc-trail-carbon-wheelsets, https://www.weareonecomposites.com/en-us/products/sector-wheelset, https://www.weareonecomposites.com/en-us/collections/enduro-carbon-wheelsets and https://www.weareonecomposites.com/en-us/products/triad-wheelset and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.weareonecomposites.com/en-us/products/coup-rim, whose canonical is https://www.weareonecomposites.com/en-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
7 pages without an H1
https://www.weareonecomposites.com/en-us/products/whisp-xc, https://www.weareonecomposites.com/en-us/products/sector-wheelset, https://www.weareonecomposites.com/en-us/products/triad-wheelset, https://www.weareonecomposites.com/en-us/products/deal-downhill, https://www.weareonecomposites.com/en-us/products/fuse-wheelset and https://www.weareonecomposites.com/en-us/products/revive2-0-gravel and 1 other 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 32 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Error initializing managers Error: Endpoint key not set”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
15 of 17 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 135 words
The homepage has only about 135 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP AT INDUSTRYNINE.COM” and “SHOP NOW”.
6 calls to action
The homepage has 6 calls to action, for example “Shop Arrival Parts”, “Shop at Industrynine.com” and “SHOP NOW”.
4 short forms
4 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.
16 cookies set on arrival
16Opening the homepage sets 16 cookies, 3 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.
28 other companies contacted
Loading the homepage contacts 28 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 weareonecomposites.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Powerful Form Builder · Klaviyo Email Marketing Sms · Password Lock Pages · Multifeeds · Specification And Compare · Upcart · gorgias.chat · luckyorange.com · digitaloceanspaces.com · 9gtb.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on weareonecomposites.com, including 12 speed issues, 2 SEO issues and 3 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.