Enter password to view Website Audit

Analysis

Website

Rivia

Analysis

Website

Rivia

Analysis

Website

Rivia

Published on

2026-03-17

For

Rivia

Score

38

Rivia is an AI-powered unified data and analytics platform for clinical trials — integrating fragmented data from EDC, CTMS, safety, biomarker, and other vendor sources into a standardised real-time database, with AI-assisted visual analytics (Rivia Spark) for clinical teams, safety monitors, and executives at early-phase biotech and biopharma companies.

Market

Clinical Trial Analytics / AI-Powered Clinical Data Integration / BioTech SaaS

Audience

CMOs, Heads of Clinical Operations, Medical Directors, Clinical Data Managers, Safety Officers — at biotech companies conducting Phase I-III clinical trials

CopyFreshnessUXCopyBrandSEOStructureEnterprise ReadinessPerformanceCopy

Copy

5

Freshness

32

UX

40

Copy

52

Brand

42

SEO

45

Structure

48

Enterprise Readiness

45

Performance

38

Copy

35

Copy

FAQ Section Contains Lorem Ipsum Placeholder Text — Live in Production

Score

5

Severity

High

Finding

The homepage FAQ section ('Everything you Need to Know') displays five accordion items on a live public website. Every single one has an identical title — 'What is Rivia and how does it benefit Biopharma companies?' — and identical body text containing classic Lorem ipsum placeholder copy: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim...' This is unfinished design scaffolding that was never replaced with real content before going live. For a platform selling data precision and integrity to CMOs, Heads of Clinical Operations, and CEOs of biotech companies, having Lorem ipsum body copy in the FAQ section of a live production website is a severe credibility failure — the equivalent of a biotech presenting a clinical data package with dummy data.

Recommendation

Replace all Lorem ipsum content immediately with genuine FAQ answers relevant to Rivia's ICP: 'What is Rivia and how does it benefit biopharma companies?', 'How long does integration take?', 'Which EDC and CTMS systems does Rivia integrate with?', 'Is Rivia 21 CFR Part 11 compliant?', 'How does pricing work?'. If real FAQ content isn't ready, remove the section entirely rather than leaving dummy text visible. This is the highest-priority issue on the site — a pharmaceutical executive evaluating Rivia for a clinical trial that may cost $50M+ will not accept placeholder copy as a signal of product maturity.

Copy

FAQ Section Contains Lorem Ipsum Placeholder Text — Live in Production

Score

5

Severity

High

Finding

The homepage FAQ section ('Everything you Need to Know') displays five accordion items on a live public website. Every single one has an identical title — 'What is Rivia and how does it benefit Biopharma companies?' — and identical body text containing classic Lorem ipsum placeholder copy: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim...' This is unfinished design scaffolding that was never replaced with real content before going live. For a platform selling data precision and integrity to CMOs, Heads of Clinical Operations, and CEOs of biotech companies, having Lorem ipsum body copy in the FAQ section of a live production website is a severe credibility failure — the equivalent of a biotech presenting a clinical data package with dummy data.

Recommendation

Replace all Lorem ipsum content immediately with genuine FAQ answers relevant to Rivia's ICP: 'What is Rivia and how does it benefit biopharma companies?', 'How long does integration take?', 'Which EDC and CTMS systems does Rivia integrate with?', 'Is Rivia 21 CFR Part 11 compliant?', 'How does pricing work?'. If real FAQ content isn't ready, remove the section entirely rather than leaving dummy text visible. This is the highest-priority issue on the site — a pharmaceutical executive evaluating Rivia for a clinical trial that may cost $50M+ will not accept placeholder copy as a signal of product maturity.

Copy

FAQ Section Contains Lorem Ipsum Placeholder Text — Live in Production

Score

5

Severity

High

Finding

The homepage FAQ section ('Everything you Need to Know') displays five accordion items on a live public website. Every single one has an identical title — 'What is Rivia and how does it benefit Biopharma companies?' — and identical body text containing classic Lorem ipsum placeholder copy: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim...' This is unfinished design scaffolding that was never replaced with real content before going live. For a platform selling data precision and integrity to CMOs, Heads of Clinical Operations, and CEOs of biotech companies, having Lorem ipsum body copy in the FAQ section of a live production website is a severe credibility failure — the equivalent of a biotech presenting a clinical data package with dummy data.

Recommendation

Replace all Lorem ipsum content immediately with genuine FAQ answers relevant to Rivia's ICP: 'What is Rivia and how does it benefit biopharma companies?', 'How long does integration take?', 'Which EDC and CTMS systems does Rivia integrate with?', 'Is Rivia 21 CFR Part 11 compliant?', 'How does pricing work?'. If real FAQ content isn't ready, remove the section entirely rather than leaving dummy text visible. This is the highest-priority issue on the site — a pharmaceutical executive evaluating Rivia for a clinical trial that may cost $50M+ will not accept placeholder copy as a signal of product maturity.

Freshness

Footer Copyright — © 2024 on a Site in 2026

Score

32

Severity

High

Finding

The footer shows '© 2024 Rivia. All Rights Reserved' — a copyright year that is now two years out of date. This is particularly jarring given that the blog and success stories show active content from 2025 (including ESMO AI 2025 coverage), suggesting the site is actively maintained yet the footer has not been updated since launch. For biopharma evaluators who scrutinise vendor due diligence — including checking whether a company is actively invested in its own operations — a 2-year-old copyright footer signals under-maintenance at a company asking to be trusted with phase II and III clinical trial data.

Recommendation

Update the footer to '© 2026 Rivia. All Rights Reserved' immediately and automate the year via JavaScript or a template variable. Given the Lorem ipsum issue coexisting with this footer error, conduct a full site audit for other placeholder or stale content across all pages. Two-year stale footer + live Lorem ipsum on the same site suggests a QA gap that buyers will generalise to the product's data quality practices.

Freshness

Footer Copyright — © 2024 on a Site in 2026

Score

32

Severity

High

Finding

The footer shows '© 2024 Rivia. All Rights Reserved' — a copyright year that is now two years out of date. This is particularly jarring given that the blog and success stories show active content from 2025 (including ESMO AI 2025 coverage), suggesting the site is actively maintained yet the footer has not been updated since launch. For biopharma evaluators who scrutinise vendor due diligence — including checking whether a company is actively invested in its own operations — a 2-year-old copyright footer signals under-maintenance at a company asking to be trusted with phase II and III clinical trial data.

Recommendation

Update the footer to '© 2026 Rivia. All Rights Reserved' immediately and automate the year via JavaScript or a template variable. Given the Lorem ipsum issue coexisting with this footer error, conduct a full site audit for other placeholder or stale content across all pages. Two-year stale footer + live Lorem ipsum on the same site suggests a QA gap that buyers will generalise to the product's data quality practices.

Freshness

Footer Copyright — © 2024 on a Site in 2026

Score

32

Severity

High

Finding

The footer shows '© 2024 Rivia. All Rights Reserved' — a copyright year that is now two years out of date. This is particularly jarring given that the blog and success stories show active content from 2025 (including ESMO AI 2025 coverage), suggesting the site is actively maintained yet the footer has not been updated since launch. For biopharma evaluators who scrutinise vendor due diligence — including checking whether a company is actively invested in its own operations — a 2-year-old copyright footer signals under-maintenance at a company asking to be trusted with phase II and III clinical trial data.

Recommendation

Update the footer to '© 2026 Rivia. All Rights Reserved' immediately and automate the year via JavaScript or a template variable. Given the Lorem ipsum issue coexisting with this footer error, conduct a full site audit for other placeholder or stale content across all pages. Two-year stale footer + live Lorem ipsum on the same site suggests a QA gap that buyers will generalise to the product's data quality practices.

UX

Book a Demo CTA Routes to Google Calendar App Link — Not a Branded Flow

Score

40

Severity

High

Finding

The primary CTA 'Book a demo' in the navigation routes to calendar.app.google/KxrhkRYcRKQLSMxeA — a raw Google Calendar appointment booking link. The footer CTA and the bottom-of-page CTA both route to calendly.com/rivia-platform/demo — a different destination from the nav CTA. Two different booking destinations for the same action creates inconsistency and brand fragility: if either link is deactivated or the calendar owner changes, every CTA on the site breaks. Additionally, a raw Google Calendar URL as a primary nav CTA signals that sales infrastructure is minimal — a deterrent for enterprise biopharma buyers evaluating vendor maturity.

Recommendation

Consolidate all 'Book a demo' CTAs to a single, consistent destination. Calendly is the stronger choice over Google Calendar App — it provides branded scheduling pages, time zone handling, and analytics. Ideally, build a dedicated /book-demo page on rivia.com that embeds the Calendly widget under Rivia branding, so the URL remains on-domain and consistent. A biotech CMO clicking 'Book a demo' should never see a raw Google Calendar URL — it undermines the product's promise of professional data infrastructure.

UX

Book a Demo CTA Routes to Google Calendar App Link — Not a Branded Flow

Score

40

Severity

High

Finding

The primary CTA 'Book a demo' in the navigation routes to calendar.app.google/KxrhkRYcRKQLSMxeA — a raw Google Calendar appointment booking link. The footer CTA and the bottom-of-page CTA both route to calendly.com/rivia-platform/demo — a different destination from the nav CTA. Two different booking destinations for the same action creates inconsistency and brand fragility: if either link is deactivated or the calendar owner changes, every CTA on the site breaks. Additionally, a raw Google Calendar URL as a primary nav CTA signals that sales infrastructure is minimal — a deterrent for enterprise biopharma buyers evaluating vendor maturity.

Recommendation

Consolidate all 'Book a demo' CTAs to a single, consistent destination. Calendly is the stronger choice over Google Calendar App — it provides branded scheduling pages, time zone handling, and analytics. Ideally, build a dedicated /book-demo page on rivia.com that embeds the Calendly widget under Rivia branding, so the URL remains on-domain and consistent. A biotech CMO clicking 'Book a demo' should never see a raw Google Calendar URL — it undermines the product's promise of professional data infrastructure.

UX

Book a Demo CTA Routes to Google Calendar App Link — Not a Branded Flow

Score

40

Severity

High

Finding

The primary CTA 'Book a demo' in the navigation routes to calendar.app.google/KxrhkRYcRKQLSMxeA — a raw Google Calendar appointment booking link. The footer CTA and the bottom-of-page CTA both route to calendly.com/rivia-platform/demo — a different destination from the nav CTA. Two different booking destinations for the same action creates inconsistency and brand fragility: if either link is deactivated or the calendar owner changes, every CTA on the site breaks. Additionally, a raw Google Calendar URL as a primary nav CTA signals that sales infrastructure is minimal — a deterrent for enterprise biopharma buyers evaluating vendor maturity.

Recommendation

Consolidate all 'Book a demo' CTAs to a single, consistent destination. Calendly is the stronger choice over Google Calendar App — it provides branded scheduling pages, time zone handling, and analytics. Ideally, build a dedicated /book-demo page on rivia.com that embeds the Calendly widget under Rivia branding, so the URL remains on-domain and consistent. A biotech CMO clicking 'Book a demo' should never see a raw Google Calendar URL — it undermines the product's promise of professional data infrastructure.

Copy

Hero Headline — Tagline and H1 Disconnected

Score

52

Severity

Medium

Finding

The page title and site tagline is 'Know better. Act better.' — a crisp, memorable clinical decision-making hook. However the homepage H1 is 'Know better. Act better. The unified data and analytics platform for clinical trials.' — padding the sharp tagline with a generic platform descriptor. The sub-headline then adds: 'Rivia integrates fragmented trial data and turns it into actionable insights, to drive more predictable operations and unlock hidden therapeutic potential.' 'Unlock hidden therapeutic potential' is the most evocative phrase on the page and should be near the hero — a drug that might not make it to Phase III because of data fragmentation, then does because of better visibility, is the emotional core of Rivia's value proposition.

Recommendation

Separate the tagline from the H1: use 'Know better. Act better.' as a standalone tagline and make the H1 outcome-focused: 'Stop losing clinical insights to fragmented data.' or 'Find the signals in your trial data before your competitors find theirs.' The '91% reduction in data review time' from the blog (citing ESMO AI 2025) is a specific, defensible metric that should anchor the hero — it transforms 'analytics platform' into a concrete time-saving claim that CMOs and Heads of Clinical Operations immediately translate to cost and speed.

Copy

Hero Headline — Tagline and H1 Disconnected

Score

52

Severity

Medium

Finding

The page title and site tagline is 'Know better. Act better.' — a crisp, memorable clinical decision-making hook. However the homepage H1 is 'Know better. Act better. The unified data and analytics platform for clinical trials.' — padding the sharp tagline with a generic platform descriptor. The sub-headline then adds: 'Rivia integrates fragmented trial data and turns it into actionable insights, to drive more predictable operations and unlock hidden therapeutic potential.' 'Unlock hidden therapeutic potential' is the most evocative phrase on the page and should be near the hero — a drug that might not make it to Phase III because of data fragmentation, then does because of better visibility, is the emotional core of Rivia's value proposition.

Recommendation

Separate the tagline from the H1: use 'Know better. Act better.' as a standalone tagline and make the H1 outcome-focused: 'Stop losing clinical insights to fragmented data.' or 'Find the signals in your trial data before your competitors find theirs.' The '91% reduction in data review time' from the blog (citing ESMO AI 2025) is a specific, defensible metric that should anchor the hero — it transforms 'analytics platform' into a concrete time-saving claim that CMOs and Heads of Clinical Operations immediately translate to cost and speed.

Copy

Hero Headline — Tagline and H1 Disconnected

Score

52

Severity

Medium

Finding

The page title and site tagline is 'Know better. Act better.' — a crisp, memorable clinical decision-making hook. However the homepage H1 is 'Know better. Act better. The unified data and analytics platform for clinical trials.' — padding the sharp tagline with a generic platform descriptor. The sub-headline then adds: 'Rivia integrates fragmented trial data and turns it into actionable insights, to drive more predictable operations and unlock hidden therapeutic potential.' 'Unlock hidden therapeutic potential' is the most evocative phrase on the page and should be near the hero — a drug that might not make it to Phase III because of data fragmentation, then does because of better visibility, is the emotional core of Rivia's value proposition.

Recommendation

Separate the tagline from the H1: use 'Know better. Act better.' as a standalone tagline and make the H1 outcome-focused: 'Stop losing clinical insights to fragmented data.' or 'Find the signals in your trial data before your competitors find theirs.' The '91% reduction in data review time' from the blog (citing ESMO AI 2025) is a specific, defensible metric that should anchor the hero — it transforms 'analytics platform' into a concrete time-saving claim that CMOs and Heads of Clinical Operations immediately translate to cost and speed.

Brand

Customer Logos — No Alt Text on Any

Score

42

Severity

Medium

Finding

The customer logo strip displays approximately 10 biotech company logos (Alentis Therapeutics, Syqe, Aspeya, Scancell, Calypso Biotech, Abcentra, Enyo, Omeicos, and others). Every logo is an image file with no alt text attribute. The logo filenames are UUIDs or CDN paths (e.g., 68a4ee33c6a68785c27654e4_Syqe_Logo.jpg) — the company names are invisible to screen readers and search engines. For a B2B platform in regulated healthcare where accessibility compliance (WCAG 2.1) and vendor due diligence both matter, untagged customer logos create both a legal risk and an SEO miss.

Recommendation

Add descriptive alt text to every customer logo: alt='Alentis Therapeutics — Rivia customer', alt='Scancell — Rivia customer', etc. This makes customer names indexable by Google (supporting 'Rivia [company] case study' searches), ensures accessibility compliance for screen reader users, and ensures visible fallback text if any CDN image fails to load. A 30-minute audit pass across all logo images would resolve this entirely.

Brand

Customer Logos — No Alt Text on Any

Score

42

Severity

Medium

Finding

The customer logo strip displays approximately 10 biotech company logos (Alentis Therapeutics, Syqe, Aspeya, Scancell, Calypso Biotech, Abcentra, Enyo, Omeicos, and others). Every logo is an image file with no alt text attribute. The logo filenames are UUIDs or CDN paths (e.g., 68a4ee33c6a68785c27654e4_Syqe_Logo.jpg) — the company names are invisible to screen readers and search engines. For a B2B platform in regulated healthcare where accessibility compliance (WCAG 2.1) and vendor due diligence both matter, untagged customer logos create both a legal risk and an SEO miss.

Recommendation

Add descriptive alt text to every customer logo: alt='Alentis Therapeutics — Rivia customer', alt='Scancell — Rivia customer', etc. This makes customer names indexable by Google (supporting 'Rivia [company] case study' searches), ensures accessibility compliance for screen reader users, and ensures visible fallback text if any CDN image fails to load. A 30-minute audit pass across all logo images would resolve this entirely.

Brand

Customer Logos — No Alt Text on Any

Score

42

Severity

Medium

Finding

The customer logo strip displays approximately 10 biotech company logos (Alentis Therapeutics, Syqe, Aspeya, Scancell, Calypso Biotech, Abcentra, Enyo, Omeicos, and others). Every logo is an image file with no alt text attribute. The logo filenames are UUIDs or CDN paths (e.g., 68a4ee33c6a68785c27654e4_Syqe_Logo.jpg) — the company names are invisible to screen readers and search engines. For a B2B platform in regulated healthcare where accessibility compliance (WCAG 2.1) and vendor due diligence both matter, untagged customer logos create both a legal risk and an SEO miss.

Recommendation

Add descriptive alt text to every customer logo: alt='Alentis Therapeutics — Rivia customer', alt='Scancell — Rivia customer', etc. This makes customer names indexable by Google (supporting 'Rivia [company] case study' searches), ensures accessibility compliance for screen reader users, and ensures visible fallback text if any CDN image fails to load. A 30-minute audit pass across all logo images would resolve this entirely.

SEO

Page Title vs Tagline — 'Biotech' vs 'Biopharma' Inconsistency

Score

45

Severity

Medium

Finding

The page meta description from search (confirmed via blog categories) uses 'biotech' while the FAQ placeholders repeatedly reference 'Biopharma'. The hero sub-headline says 'biotechs and pharma innovators'. The footer tagline says 'therapeutic innovators'. The About page may use different vocabulary. For a B2B SaaS in a highly specification-conscious industry, inconsistent ICP vocabulary across the site — 'biotech', 'biopharma', 'pharma', 'therapeutic innovators' — creates a search mismatch: a Head of Clinical Operations at a pharma company may search for 'clinical trial analytics pharma' and not associate Rivia with their specific industry segment if the primary vocabulary is 'biotech'.

Recommendation

Align ICP vocabulary site-wide with a deliberate keyword strategy. Research whether the primary acquisition target is 'biotech' (smaller, Series A-C companies, more likely early-phase) or 'pharma/biopharma' (larger, more integrated). Make the decision, standardise the language on the homepage, meta titles, and H1s, and build content around those terms. The success stories already use specific company names — ensure the category vocabulary on the homepage reflects the buyer's self-identity.

SEO

Page Title vs Tagline — 'Biotech' vs 'Biopharma' Inconsistency

Score

45

Severity

Medium

Finding

The page meta description from search (confirmed via blog categories) uses 'biotech' while the FAQ placeholders repeatedly reference 'Biopharma'. The hero sub-headline says 'biotechs and pharma innovators'. The footer tagline says 'therapeutic innovators'. The About page may use different vocabulary. For a B2B SaaS in a highly specification-conscious industry, inconsistent ICP vocabulary across the site — 'biotech', 'biopharma', 'pharma', 'therapeutic innovators' — creates a search mismatch: a Head of Clinical Operations at a pharma company may search for 'clinical trial analytics pharma' and not associate Rivia with their specific industry segment if the primary vocabulary is 'biotech'.

Recommendation

Align ICP vocabulary site-wide with a deliberate keyword strategy. Research whether the primary acquisition target is 'biotech' (smaller, Series A-C companies, more likely early-phase) or 'pharma/biopharma' (larger, more integrated). Make the decision, standardise the language on the homepage, meta titles, and H1s, and build content around those terms. The success stories already use specific company names — ensure the category vocabulary on the homepage reflects the buyer's self-identity.

SEO

Page Title vs Tagline — 'Biotech' vs 'Biopharma' Inconsistency

Score

45

Severity

Medium

Finding

The page meta description from search (confirmed via blog categories) uses 'biotech' while the FAQ placeholders repeatedly reference 'Biopharma'. The hero sub-headline says 'biotechs and pharma innovators'. The footer tagline says 'therapeutic innovators'. The About page may use different vocabulary. For a B2B SaaS in a highly specification-conscious industry, inconsistent ICP vocabulary across the site — 'biotech', 'biopharma', 'pharma', 'therapeutic innovators' — creates a search mismatch: a Head of Clinical Operations at a pharma company may search for 'clinical trial analytics pharma' and not associate Rivia with their specific industry segment if the primary vocabulary is 'biotech'.

Recommendation

Align ICP vocabulary site-wide with a deliberate keyword strategy. Research whether the primary acquisition target is 'biotech' (smaller, Series A-C companies, more likely early-phase) or 'pharma/biopharma' (larger, more integrated). Make the decision, standardise the language on the homepage, meta titles, and H1s, and build content around those terms. The success stories already use specific company names — ensure the category vocabulary on the homepage reflects the buyer's self-identity.

Structure

Pricing Page — Existence Unknown from Homepage Context

Score

48

Severity

Medium

Finding

The nav includes a Pricing link — positive transparency for a regulated biopharma SaaS. However the homepage provides no pricing signal or tier indication whatsoever before the nav link. For a buyer who is evaluating Rivia against building in-house or using a CRO's analytics stack, the complete absence of even a starting price or model type (per-trial, per-seat, per-integration) in the homepage body means the first price signal is gated behind a separate page click. Given the 20-day integration promise and the specific target of early-phase biotech companies (who are extremely cost-conscious), a homepage pricing anchor like 'pricing from $X/month per trial' would immediately qualify or disqualify visitors before they invest time in a demo.

Recommendation

Add a brief pricing signal to the homepage — either below the 'Minimal Effort, Maximum Output' onboarding section or near the bottom CTA: 'Flexible pricing from $X/month, scaled to your trials and team size.' Even 'contact us for trial-specific pricing' with a visible tier structure on the pricing page transforms price from an unknown (anxiety-inducing) to a framework (manageable). Early-phase biotechs evaluating three vendors will disqualify the one that won't tell them even a ballpark before a demo call.

Structure

Pricing Page — Existence Unknown from Homepage Context

Score

48

Severity

Medium

Finding

The nav includes a Pricing link — positive transparency for a regulated biopharma SaaS. However the homepage provides no pricing signal or tier indication whatsoever before the nav link. For a buyer who is evaluating Rivia against building in-house or using a CRO's analytics stack, the complete absence of even a starting price or model type (per-trial, per-seat, per-integration) in the homepage body means the first price signal is gated behind a separate page click. Given the 20-day integration promise and the specific target of early-phase biotech companies (who are extremely cost-conscious), a homepage pricing anchor like 'pricing from $X/month per trial' would immediately qualify or disqualify visitors before they invest time in a demo.

Recommendation

Add a brief pricing signal to the homepage — either below the 'Minimal Effort, Maximum Output' onboarding section or near the bottom CTA: 'Flexible pricing from $X/month, scaled to your trials and team size.' Even 'contact us for trial-specific pricing' with a visible tier structure on the pricing page transforms price from an unknown (anxiety-inducing) to a framework (manageable). Early-phase biotechs evaluating three vendors will disqualify the one that won't tell them even a ballpark before a demo call.

Structure

Pricing Page — Existence Unknown from Homepage Context

Score

48

Severity

Medium

Finding

The nav includes a Pricing link — positive transparency for a regulated biopharma SaaS. However the homepage provides no pricing signal or tier indication whatsoever before the nav link. For a buyer who is evaluating Rivia against building in-house or using a CRO's analytics stack, the complete absence of even a starting price or model type (per-trial, per-seat, per-integration) in the homepage body means the first price signal is gated behind a separate page click. Given the 20-day integration promise and the specific target of early-phase biotech companies (who are extremely cost-conscious), a homepage pricing anchor like 'pricing from $X/month per trial' would immediately qualify or disqualify visitors before they invest time in a demo.

Recommendation

Add a brief pricing signal to the homepage — either below the 'Minimal Effort, Maximum Output' onboarding section or near the bottom CTA: 'Flexible pricing from $X/month, scaled to your trials and team size.' Even 'contact us for trial-specific pricing' with a visible tier structure on the pricing page transforms price from an unknown (anxiety-inducing) to a framework (manageable). Early-phase biotechs evaluating three vendors will disqualify the one that won't tell them even a ballpark before a demo call.

Enterprise Readiness

Compliance and Regulatory Signals — Underpowered on Homepage

Score

45

Severity

Medium

Finding

Rivia integrates clinical trial data across EDC, CTMS, safety, and lab systems — all of which are subject to 21 CFR Part 11, ICH E6(R3), GDPR, and other regulatory requirements. The blog mentions ICH E6(R3) in passing, and the nav includes a /trust page, but the homepage contains no visible compliance badge, no regulatory framework callout, and no 21 CFR Part 11 mention. For a CMO evaluating Rivia before deploying it on a Phase II oncology trial, the first question is: 'Is this validated and compliant with the regulations governing clinical data?' This answer needs to be on the homepage, not discovered via nav exploration.

Recommendation

Add a compliance callout to the homepage trust section: 'ICH E6(R3) aligned · 21 CFR Part 11 capable · GDPR compliant · ISO 27001' with a link to the /trust page. Place this near the customer logo strip. For biopharma buyers, regulatory compliance is a prerequisite filter — it must be above the fold or within the first scroll. The Trust page exists; make it discoverable from the hero area, not only from the footer nav.

Enterprise Readiness

Compliance and Regulatory Signals — Underpowered on Homepage

Score

45

Severity

Medium

Finding

Rivia integrates clinical trial data across EDC, CTMS, safety, and lab systems — all of which are subject to 21 CFR Part 11, ICH E6(R3), GDPR, and other regulatory requirements. The blog mentions ICH E6(R3) in passing, and the nav includes a /trust page, but the homepage contains no visible compliance badge, no regulatory framework callout, and no 21 CFR Part 11 mention. For a CMO evaluating Rivia before deploying it on a Phase II oncology trial, the first question is: 'Is this validated and compliant with the regulations governing clinical data?' This answer needs to be on the homepage, not discovered via nav exploration.

Recommendation

Add a compliance callout to the homepage trust section: 'ICH E6(R3) aligned · 21 CFR Part 11 capable · GDPR compliant · ISO 27001' with a link to the /trust page. Place this near the customer logo strip. For biopharma buyers, regulatory compliance is a prerequisite filter — it must be above the fold or within the first scroll. The Trust page exists; make it discoverable from the hero area, not only from the footer nav.

Enterprise Readiness

Compliance and Regulatory Signals — Underpowered on Homepage

Score

45

Severity

Medium

Finding

Rivia integrates clinical trial data across EDC, CTMS, safety, and lab systems — all of which are subject to 21 CFR Part 11, ICH E6(R3), GDPR, and other regulatory requirements. The blog mentions ICH E6(R3) in passing, and the nav includes a /trust page, but the homepage contains no visible compliance badge, no regulatory framework callout, and no 21 CFR Part 11 mention. For a CMO evaluating Rivia before deploying it on a Phase II oncology trial, the first question is: 'Is this validated and compliant with the regulations governing clinical data?' This answer needs to be on the homepage, not discovered via nav exploration.

Recommendation

Add a compliance callout to the homepage trust section: 'ICH E6(R3) aligned · 21 CFR Part 11 capable · GDPR compliant · ISO 27001' with a link to the /trust page. Place this near the customer logo strip. For biopharma buyers, regulatory compliance is a prerequisite filter — it must be above the fold or within the first scroll. The Trust page exists; make it discoverable from the hero area, not only from the footer nav.

Performance

Contact Email in Footer — Inconsistency Between mailto and About

Score

38

Severity

Low

Finding

The footer displays the email address info@rivia.com as the visible text, but the mailto: link attribute contains mailto:info@rivia.ch — the Swiss domain (.ch) rather than the .com domain. This means a user who clicks 'email us' sends to info@rivia.ch, while a user who manually types the visible address info@rivia.com may reach a different inbox or get a bounce. For a company handling sensitive clinical trial data in a regulated industry, even a minor email routing inconsistency creates a trust gap — it implies the company has not fully aligned its .com and .ch presence.

Recommendation

Audit and reconcile all email addresses across the site. Either make info@rivia.com the canonical address (with .ch forwarding to it) or update all visible text to show info@rivia.ch consistently. The Hardturmstrasse 253, Zürich address in the footer confirms Swiss incorporation, so .ch is the likely primary domain — but rivia.com is the marketing presence. Clarify which inbox is monitored and ensure the visible address and mailto link match exactly.

Performance

Contact Email in Footer — Inconsistency Between mailto and About

Score

38

Severity

Low

Finding

The footer displays the email address info@rivia.com as the visible text, but the mailto: link attribute contains mailto:info@rivia.ch — the Swiss domain (.ch) rather than the .com domain. This means a user who clicks 'email us' sends to info@rivia.ch, while a user who manually types the visible address info@rivia.com may reach a different inbox or get a bounce. For a company handling sensitive clinical trial data in a regulated industry, even a minor email routing inconsistency creates a trust gap — it implies the company has not fully aligned its .com and .ch presence.

Recommendation

Audit and reconcile all email addresses across the site. Either make info@rivia.com the canonical address (with .ch forwarding to it) or update all visible text to show info@rivia.ch consistently. The Hardturmstrasse 253, Zürich address in the footer confirms Swiss incorporation, so .ch is the likely primary domain — but rivia.com is the marketing presence. Clarify which inbox is monitored and ensure the visible address and mailto link match exactly.

Performance

Contact Email in Footer — Inconsistency Between mailto and About

Score

38

Severity

Low

Finding

The footer displays the email address info@rivia.com as the visible text, but the mailto: link attribute contains mailto:info@rivia.ch — the Swiss domain (.ch) rather than the .com domain. This means a user who clicks 'email us' sends to info@rivia.ch, while a user who manually types the visible address info@rivia.com may reach a different inbox or get a bounce. For a company handling sensitive clinical trial data in a regulated industry, even a minor email routing inconsistency creates a trust gap — it implies the company has not fully aligned its .com and .ch presence.

Recommendation

Audit and reconcile all email addresses across the site. Either make info@rivia.com the canonical address (with .ch forwarding to it) or update all visible text to show info@rivia.ch consistently. The Hardturmstrasse 253, Zürich address in the footer confirms Swiss incorporation, so .ch is the likely primary domain — but rivia.com is the marketing presence. Clarify which inbox is monitored and ensure the visible address and mailto link match exactly.

Copy

Step 3 of Onboarding — Contradicts Step Description Title

Score

35

Severity

Medium

Finding

The 3-step onboarding timeline has a specific inconsistency: Step 1 is titled 'Access', Step 2 is 'Integration', and Step 3 is 'Configuration'. However the Step 3 description says 'Setting you up for a launch in under 30 days' — while the hero section above states 'Go live in under 20 days' as the headline claim. The homepage simultaneously claims both 20 days and 30 days as the deployment timeline on the same page. For biopharma buyers evaluating timeline promises for trial readiness — where timeline commitments are contractually significant — a self-contradictory timeline claim on the homepage creates credibility doubt about whether 20 days is a real commitment or a marketing number.

Recommendation

Reconcile the timeline claim to a single, consistent number across the entire homepage. If 20 days is the deployment target, update Step 3 to read 'Setting you up for a launch in under 20 days.' If 30 days is more accurate, update the hero badge. A single source of truth on timeline is especially critical for a product selling to regulated industries where deployment timelines feed into clinical trial planning documents and contracts.

Copy

Step 3 of Onboarding — Contradicts Step Description Title

Score

35

Severity

Medium

Finding

The 3-step onboarding timeline has a specific inconsistency: Step 1 is titled 'Access', Step 2 is 'Integration', and Step 3 is 'Configuration'. However the Step 3 description says 'Setting you up for a launch in under 30 days' — while the hero section above states 'Go live in under 20 days' as the headline claim. The homepage simultaneously claims both 20 days and 30 days as the deployment timeline on the same page. For biopharma buyers evaluating timeline promises for trial readiness — where timeline commitments are contractually significant — a self-contradictory timeline claim on the homepage creates credibility doubt about whether 20 days is a real commitment or a marketing number.

Recommendation

Reconcile the timeline claim to a single, consistent number across the entire homepage. If 20 days is the deployment target, update Step 3 to read 'Setting you up for a launch in under 20 days.' If 30 days is more accurate, update the hero badge. A single source of truth on timeline is especially critical for a product selling to regulated industries where deployment timelines feed into clinical trial planning documents and contracts.

Copy

Step 3 of Onboarding — Contradicts Step Description Title

Score

35

Severity

Medium

Finding

The 3-step onboarding timeline has a specific inconsistency: Step 1 is titled 'Access', Step 2 is 'Integration', and Step 3 is 'Configuration'. However the Step 3 description says 'Setting you up for a launch in under 30 days' — while the hero section above states 'Go live in under 20 days' as the headline claim. The homepage simultaneously claims both 20 days and 30 days as the deployment timeline on the same page. For biopharma buyers evaluating timeline promises for trial readiness — where timeline commitments are contractually significant — a self-contradictory timeline claim on the homepage creates credibility doubt about whether 20 days is a real commitment or a marketing number.

Recommendation

Reconcile the timeline claim to a single, consistent number across the entire homepage. If 20 days is the deployment target, update Step 3 to read 'Setting you up for a launch in under 20 days.' If 30 days is more accurate, update the hero badge. A single source of truth on timeline is especially critical for a product selling to regulated industries where deployment timelines feed into clinical trial planning documents and contracts.

Frequently asked

What kind of companies do you work with?

We work with ambitious tech companies typically Series A and B at the moment where the brand and website haven't kept pace with the business.

You've found product-market fit. Now you need to look the part, communicate clearly, and move fast enough to stay ahead.

That's the problem we're built for.

What does a typical project look like?
We've had bad experiences with agencies before. What's different?
Why Framer over other platforms?
How do we get started?
How does pricing work?

Recent work

V7 Labs

Utila

Buena

Enzai

Centific

trawa

Portex Global

Othello AI

Echo

Pools

Contentcloud

Wilson

Perspectives & Insights

Blazing fast brands &

Blazing fast brands &

Blazing fast brands &

websites for startups

websites for startups

websites for startups