Website review, no card needed

rapha.cc logo

rapha.cc website review

Visit site (opens in a new tab)Reviewed 31 October 202625 issues · 74 checks

This review found 25 issues worth fixing on rapha.cc, 7 of them high impact, across 74 checks. The most urgent: render-blocking requests. 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
3.7 s3.3 sMay 9Oct 243.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.4 s
May 23, 20263.5 s
May 30, 20263.6 s
Jun 6, 20263.6 s
Jun 13, 20263.6 s
Jun 20, 20263.5 s
Jun 27, 20263.4 s
Jul 4, 20263.3 s
Jul 11, 20263.4 s
Jul 18, 20263.6 s
Jul 25, 20263.7 s
Aug 1, 20263.6 s
Aug 8, 20263.6 s
Aug 15, 20263.6 s
Aug 22, 20263.5 s
Aug 29, 20263.5 s
Sep 5, 20263.5 s
Sep 12, 20263.5 s
Sep 19, 20263.4 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.4 s
Oct 17, 20263.5 s
Oct 24, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
268 ms201 msMay 9Oct 24231 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026209 ms
May 16, 2026214 ms
May 23, 2026222 ms
May 30, 2026226 ms
Jun 6, 2026234 ms
Jun 13, 2026238 ms
Jun 20, 2026242 ms
Jun 27, 2026245 ms
Jul 4, 2026244 ms
Jul 11, 2026241 ms
Jul 18, 2026244 ms
Jul 25, 2026244 ms
Aug 1, 2026245 ms
Aug 8, 2026247 ms
Aug 15, 2026253 ms
Aug 22, 2026258 ms
Aug 29, 2026260 ms
Sep 5, 2026257 ms
Sep 12, 2026246 ms
Sep 19, 2026229 ms
Sep 26, 2026216 ms
Oct 3, 2026219 ms
Oct 10, 2026220 ms
Oct 17, 2026223 ms
Oct 24, 2026231 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 rapha.cc (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rapha.cc at 0.9 s0.9 s
  2. rapha.cc at 1.8 s1.8 s
  3. rapha.cc at 2.6 s2.6 s
  4. rapha.cc at 3.5 s3.5 s
  5. rapha.cc at 4.4 s4.4 s
  6. rapha.cc at 5.3 s5.3 s
  7. rapha.cc at 6.1 s6.1 s
  8. rapha.cc at 7.0 s7.0 s

Speed

6 to fix58
  • Render-blocking requests

    1.9 s

    55 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.

  • Reduce unused JavaScript

    750 ms · 783 KiB

    About 783 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Improve image delivery

    850 ms · 165 KiB

    4 images could be 165 KiB 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.

  • Mobile performance score: 58

    58/100

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

  • Use efficient cache lifetimes

    372 KiB

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

  • Main-thread work: 2.8 s

    A phone's processor spends 2.8 s on main-thread work while loading, 1.7 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 (TikTok, Facebook and Optanon and others), adding 758 KiB and 326 ms of main-thread time.

  • 15 long tasks on the main thread

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

  • Legacy JavaScript

    79 KiB

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

  • Reduce unused CSS

    21 KiB

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

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

1 checks passed
  • Server response: 459 ms

    459 ms

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

Core Web Vitals

9 to fix33
  • Fails Core Web Vitals for real visitors

    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-user TTFB: 1.9 s

    1.9 s

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

  • Time to Interactive: 20.9 s

    20.9 s

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

  • Largest Contentful Paint: 8.0 s

    8.0 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user INP: 205 ms

    205 ms

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Total Blocking Time: 408 ms

    408 ms

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

  • Tap response (INP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 209 ms to 231 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-10-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user CLS: 0.04

    0.04

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.3 MB in 180 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 180 requests on a phone: scripts 2.0 MB (56), fonts 588 KiB (16) and images 518 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (53 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 1 image below the first screen load straight away

    1 image further down the page (44 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.93 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

1 to fixGoogle 10099
  • 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. (1 element).

2 checks passed
  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 52 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: 52 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 71 internal links, 34 external

    The homepage links to 71 pages on rapha.cc and 34 external pages.

8 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “We exist to inspire the world to live life by bike, because it’s never just a ride. Shop the world’s finest riding appa…”.

  • One H1 headline

    Your main headline reads: “AGAINST BETTER JUDGEMENT”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “The World's Finest Cycling Clothing and Accessories | Rapha”.

  • Canonical URL set

    The canonical URL is https://www.rapha.cc/rd/en.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.rapha.cc/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    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.

  • No llms.txt

    There is no https://www.rapha.cc/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 (791 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 13 pages share 5 titles

    https://www.rapha.cc/rd/en/product/BAA02XXCHB and https://www.rapha.cc/rd/en/product/BAA02XXBLF all use the title “Men's Brevet Gore-Tex Rain Jacket | Rapha”, and 4 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages share a meta description

    https://www.rapha.cc/rd/en/product/BAA02XXCHB and https://www.rapha.cc/rd/en/product/BAA02XXBLF use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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 10093
  • 59 small tap targets

    59 of 95 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

  • About 995 words of copy

    The homepage carries about 995 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “New In | Shop Now” and “Join the RCC | Discover benefits”.

  • 28 calls to action

    The homepage has 28 calls to action, for example “New In | Shop Now”, “Join the RCC | Discover benefits” and “AGAINST BETTER JUDGEMENT: Shop Now”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • 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

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 14 cookies set on arrival

    14

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

  • 19 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 rapha.cc, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Netlify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on rapha.cc, including 15 speed issues, 1 SEO issue 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

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