Website review, no card needed

rapid-medical.com logo

rapid-medical.com website review

Visit site (opens in a new tab)Reviewed 17 November 202622 issues · 74 checks

This review found 22 issues worth fixing on rapid-medical.com, 4 of them high impact, across 74 checks. The most urgent: page weight: 5.6 MB in 57 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
963 ms643 msMay 30Nov 14785 ms
Show as table
DateReal-visitor load time (LCP)
May 30, 2026926 ms
Jun 6, 2026897 ms
Jun 13, 2026823 ms
Jun 20, 2026777 ms
Jun 27, 2026724 ms
Jul 4, 2026755 ms
Jul 11, 2026694 ms
Jul 18, 2026680 ms
Jul 25, 2026699 ms
Aug 1, 2026694 ms
Aug 8, 2026729 ms
Aug 15, 2026797 ms
Aug 22, 2026829 ms
Aug 29, 2026821 ms
Sep 5, 2026800 ms
Sep 12, 2026761 ms
Sep 19, 2026761 ms
Sep 26, 2026775 ms
Oct 3, 2026798 ms
Oct 10, 2026779 ms
Oct 17, 2026767 ms
Oct 24, 2026756 ms
Oct 31, 2026773 ms
Nov 7, 2026794 ms
Nov 14, 2026785 ms
Real-visitor tap response (INP)75th percentile, phones
82 ms56 msMay 30Nov 1471 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202670 ms
Jun 6, 202671 ms
Jun 13, 202669 ms
Jun 20, 202670 ms
Jun 27, 202667 ms
Jul 4, 202663 ms
Jul 11, 202662 ms
Jul 18, 202659 ms
Jul 25, 202661 ms
Aug 1, 202662 ms
Aug 8, 202662 ms
Aug 15, 202667 ms
Aug 22, 202668 ms
Aug 29, 202669 ms
Sep 5, 202671 ms
Sep 12, 202672 ms
Sep 19, 202679 ms
Sep 26, 202679 ms
Oct 3, 202677 ms
Oct 10, 202675 ms
Oct 17, 202670 ms
Oct 24, 202673 ms
Oct 31, 202675 ms
Nov 7, 202676 ms
Nov 14, 202671 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 rapid-medical.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. rapid-medical.com at 0.4 s0.4 s
  2. rapid-medical.com at 0.8 s0.8 s
  3. rapid-medical.com at 1.1 s1.1 s
  4. rapid-medical.com at 1.5 s1.5 s
  5. rapid-medical.com at 1.9 s1.9 s
  6. rapid-medical.com at 2.3 s2.3 s
  7. rapid-medical.com at 2.6 s2.6 s
  8. rapid-medical.com at 3.0 s3.0 s

Speed

4 to fix75
  • Mobile performance score: 75

    75/100

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

  • Reduce unused JavaScript

    760 ms · 174 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (cdn-website.com, Google Tag Manager and userway.org and others), adding 5.6 MB and 254 ms of main-thread time.

  • cdn-website.com adds 123 ms

    123 ms

    cdn-website.com costs a phone 123 ms of main-thread work and 5.2 MB 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.

  • Reduce unused CSS

    180 ms · 51 KiB

    About 51 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 180 ms faster on a phone.

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    11 KiB

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

  • Use efficient cache lifetimes

    10 KiB

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

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

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

2 to fix100
  • Largest Contentful Paint: 6.2 s

    6.2 s

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

  • Time to Interactive: 6.2 s

    6.2 s

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

  • Tap response (INP) held steady for real visitors

    +4%

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

11 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.0 s

    1.0 s

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

  • Real-user INP: 61 ms

    61 ms

    Real visitors wait 61 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.7 s

    0.7 s

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

  • Real-user TTFB: 637 ms

    637 ms

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

  • Largest content (LCP) got 13% faster for real visitors

    -13%

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

  • Cumulative Layout Shift: 0.096

    0.096

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

  • First Contentful Paint: 0.9 s

    0.9 s

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

  • Speed Index: 1.6 s

    1.6 s

    Visually, the page fills in at 1.6 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 15 ms

    15 ms

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

Images and page weight

1 to fix70
  • Page weight: 5.6 MB in 57 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 57 requests on a phone: media 4.7 MB (2), scripts 547 KiB (26) and fonts 273 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.59 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.59 g of CO₂e: 190.8 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

4 to fixGoogle 8592
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h1 → h3, h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 32 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 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

2 to fixGoogle 9291
  • No structured data

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

  • 7 H1 headlines

    There are 7 <h1> headlines (“EXPAND”, “WHAT’S POSSIBLE” and “EXPAND”). One clear main headline is easier for people and search engines.

  • 25 internal links, 11 external

    The homepage links to 25 pages on rapid-medical.com and 11 external pages.

6 checks passed
  • Meta description: 98 characters

    Your meta description is 98 characters: “Purpose-built devices for stroke intervention. Personalized tools for patient anatomy. Learn more!”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Neurovascular Therapy Solutions | Rapid Medical™​ | Worldwide”.

  • Canonical URL set

    The canonical URL is https://www.rapid-medical.com/.

  • 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.rapid-medical.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

3 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 (315 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.rapid-medical.com/llms.txt (4 KiB, 28 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 4 pages share 2 titles

    / and https://www.rapid-medical.com/welcome_d all use the title “Neurovascular Therapy Solutions | Rapid Medical™​ | Worldwide”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.rapid-medical.com/our-solutions and https://www.rapid-medical.com/evidence use the same meta description. A description written for each page earns more clicks.

  • 8 pages without an H1

    https://www.rapid-medical.com/our-solutions, https://www.rapid-medical.com/evidence, https://www.rapid-medical.com/about-us, https://www.rapid-medical.com/contact-us, https://www.rapid-medical.com/choose-your-location and https://www.rapid-medical.com/privacy-statement and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://www.rapid-medical.com/our-solutions, https://www.rapid-medical.com/evidence, https://www.rapid-medical.com/choose-your-location and https://www.rapid-medical.com/patents have 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.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 12 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 12 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 5 small tap targets

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

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: “50K+ patients”. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 198 words

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

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “Request a demo”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us” and “Request a demo”.

  • Analytics in place

    Analytics detected: Google Analytics.

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.

  • 9 cookies set on arrival

    9

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

  • 11 other companies contacted

    Loading the homepage contacts 11 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 rapid-medical.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on rapid-medical.com, including 6 speed issues, 2 SEO issues and 2 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