Website review, no card needed

cloud-9.bike logo

cloud-9.bike website review

Visit site (opens in a new tab)Reviewed 8 November 202623 issues · 73 checks

This review found 23 issues worth fixing on cloud-9.bike, 3 of them high impact, across 73 checks. The most urgent: hidden but focusable. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
706 ms509 msMay 16Oct 31642 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026537 ms
May 23, 2026537 ms
May 30, 2026545 ms
Jun 6, 2026580 ms
Jun 13, 2026576 ms
Jun 20, 2026575 ms
Jun 27, 2026584 ms
Jul 4, 2026604 ms
Jul 11, 2026624 ms
Jul 18, 2026624 ms
Jul 25, 2026562 ms
Aug 1, 2026548 ms
Aug 8, 2026532 ms
Aug 15, 2026538 ms
Aug 22, 2026574 ms
Aug 29, 2026592 ms
Sep 5, 2026613 ms
Sep 12, 2026615 ms
Sep 19, 2026623 ms
Sep 26, 2026615 ms
Oct 3, 2026622 ms
Oct 10, 2026627 ms
Oct 17, 2026667 ms
Oct 24, 2026683 ms
Oct 31, 2026642 ms
Real-visitor tap response (INP)75th percentile, phones
72 ms53 msMay 16Oct 3169 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202662 ms
May 23, 202662 ms
May 30, 202663 ms
Jun 6, 202663 ms
Jun 13, 202663 ms
Jun 20, 202662 ms
Jun 27, 202662 ms
Jul 4, 202662 ms
Jul 11, 202662 ms
Jul 18, 202662 ms
Jul 25, 202655 ms
Aug 1, 202655 ms
Aug 8, 202655 ms
Aug 15, 202655 ms
Aug 22, 202660 ms
Aug 29, 202658 ms
Sep 5, 202661 ms
Sep 12, 202661 ms
Sep 19, 202663 ms
Sep 26, 202662 ms
Oct 3, 202663 ms
Oct 10, 202663 ms
Oct 17, 202667 ms
Oct 24, 202670 ms
Oct 31, 202669 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

Full-page screenshot of cloud-9.bike (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cloud-9.bike at 0.6 s0.6 s
  2. cloud-9.bike at 1.2 s1.2 s
  3. cloud-9.bike at 1.8 s1.8 s
  4. cloud-9.bike at 2.4 s2.4 s
  5. cloud-9.bike at 3.0 s3.0 s
  6. cloud-9.bike at 3.6 s3.6 s
  7. cloud-9.bike at 4.2 s4.2 s
  8. cloud-9.bike at 4.8 s4.8 s

Speed

1 to fix92
  • Improve image delivery

    258 KiB

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

  • Reduce unused JavaScript

    51 KiB

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

  • Render-blocking requests

    50 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 50 ms.

  • Reduce unused CSS

    31 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Shopify, nfcube.com and shop.app), adding 78 KiB and 21 ms of main-thread time.

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

  • Use efficient cache lifetimes

    2 KiB

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

3 checks passed
  • Mobile performance score: 92

    92/100

    Your mobile performance score is 92. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 202 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest content (LCP) got 23% slower for real visitors

    +23%

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

  • Speed Index: 5.3 s

    5.3 s

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • 3 images without width and height

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

  • Tap response (INP) got 12% slower for real visitors

    +12%

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

10 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: 0.6 s

    0.6 s

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

  • Real-user INP: 71 ms

    71 ms

    Real visitors wait 71 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.5 s

    0.5 s

    Real visitors see the first content after 0.5 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 341 ms

    341 ms

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

  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Find the saddle that's perfect for you and your ride- we ha…”.

  • Time to Interactive: 2.2 s

    2.2 s

    The page is fully interactive after 2.2 s.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    Commuter_Part_Number_-_50460_LR_-_1.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).

  • About 0.4 g of CO₂ per visit

    0.41 g

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

3 checks passed
  • Page weight: 1.4 MB in 112 requests

    1.4 MB

    Your homepage downloads 1.4 MB in 112 requests on a phone: other files 654 KiB (64), images 497 KiB (11) and scripts 213 KiB (29). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 8994
  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 6 links without text

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

  • Alternative text of images should not be repeated as text (3 elements)

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

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 44 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: 44 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

3 to fixGoogle 10084
  • Title is short (15 characters)

    Your title is only 15 characters: “Cloud-9 Saddles”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

  • 44 internal links, 2 external

    The homepage links to 44 pages on cloud-9.bike and 2 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Cloud-9 Saddles”.

  • Canonical URL set

    The canonical URL is https://cloud-9.bike/.

  • 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://cloud-9.bike/sitemap.xml.

AI search readiness

1 to fix83
  • 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://cloud-9.bike/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix85
  • 6 pages without a meta description

    https://cloud-9.bike/collections/cloud-9-saddles-and-covers, https://cloud-9.bike/collections/saddle-covers, https://cloud-9.bike/blogs/how-to, https://cloud-9.bike/collections/kush-plus, https://cloud-9.bike/collections/featured-products and https://cloud-9.bike/pages/contact-us 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://cloud-9.bike/collections/featured-products/products/comfort-airflow, whose canonical is https://cloud-9.bike/products/comfort-airflow. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://cloud-9.bike/pages/contact-us has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://cloud-9.bike/blogs/how-to 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.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was 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

    16 of 19 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • Only about 148 words

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP COMFORT SADDLES” and “SHOP CRUISER SADDLES”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “shop comfort saddles”, “Shop Cruiser Saddles” and “*LEARN MORE”.

  • 3 short forms

    3 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

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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

    7

    Opening the homepage sets 7 cookies (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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 cloud-9.bike, 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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

nfcube.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
Hosting
Shopify

Hiring

Hiring
4 open roles
Teams
Retail (4)
Job board
greenhouse

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on cloud-9.bike, including 5 speed issues, 3 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25