Website review, no card needed
consensus.com website review
Visit site (opens in a new tab)Reviewed 20 November 202624 issues · 73 checks
This review found 24 issues worth fixing on consensus.com, 12 of them high impact, across 73 checks. The most urgent: fails Core Web Vitals for real visitors. 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.0 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 4.1 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 4.1 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.6 s |
| Aug 15, 2026 | 4.8 s |
| Aug 22, 2026 | 5.1 s |
| Aug 29, 2026 | 5.2 s |
| Sep 5, 2026 | 5.2 s |
| Sep 12, 2026 | 5.4 s |
| Sep 19, 2026 | 5.2 s |
| Sep 26, 2026 | 5.2 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.3 s |
| Oct 17, 2026 | 4.1 s |
| Oct 24, 2026 | 3.9 s |
| Oct 31, 2026 | 3.7 s |
| Nov 7, 2026 | 3.7 s |
| Nov 14, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 106 ms |
| Jun 6, 2026 | 110 ms |
| Jun 13, 2026 | 116 ms |
| Jun 20, 2026 | 118 ms |
| Jun 27, 2026 | 123 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 133 ms |
| Jul 18, 2026 | 134 ms |
| Jul 25, 2026 | 134 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 122 ms |
| Aug 22, 2026 | 121 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 121 ms |
| Sep 12, 2026 | 118 ms |
| Sep 19, 2026 | 115 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 117 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 113 ms |
| Oct 24, 2026 | 111 ms |
| Oct 31, 2026 | 108 ms |
| Nov 7, 2026 | 109 ms |
| Nov 14, 2026 | 114 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.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.4 s
2.8 s
3.2 s
Speed
Mobile performance score: 87
87/100Your mobile performance score is 87. Pages that score under 90 lose visitors before the first paint.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 326 ms. During a long task the page ignores taps.
Reduce unused JavaScript
49 KiBAbout 49 KiB of JavaScript is downloaded but never used on this page.
1 third-party service on the page
1 third-party service load with your homepage (cloudflare.com), adding 28 KiB and 25 ms of main-thread time.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 849 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 LCP: 4.7 s
4.7 sReal visitors wait 4.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.6 s
3.6 sReal visitors see the first content after 3.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.2 s
2.2 sReal visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 518 ms
518 msScripts block taps and scrolling for 518 ms in total while the page loads. Good is under 200 ms.
Time to Interactive: 4.3 s
4.3 sThe page becomes fully interactive after 4.3 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 106 ms to 114 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 135 ms
135 msReal visitors wait 135 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
First Contentful Paint: 0.8 s
0.8 sThe first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 0.8 s
0.8 sYour largest element renders in 0.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “www.consensus.com”.
Speed Index: 1.4 s
1.4 sVisually, the page fills in at 1.4 s (Speed Index), inside the 3.4 s “good” threshold.
Images and page weight
Page weight: 2.2 MB in 9 requests
2.2 MBYour homepage downloads 2.2 MB in 9 requests on a phone: other files 1.7 MB (4), scripts 250 KiB (2) and HTML 209 KiB (2). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 73.2 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 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
The document uses <meta http-equiv="refresh">
The document uses <meta http-equiv="refresh"> (1 element).
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails 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 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
46 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: 46 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Blocked from indexing
Google's crawler is blocked from indexing this page.
Error status code
The page answers with an error status, so search engines may drop it.
37 internal links, 48 external
The homepage links to 37 pages on consensus.com and 48 external pages.
8 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “We deliver comprehensive cloud-based, healthcare data interoperability platforms, with streamlined workflows to power t…”.
One H1 headline
Your main headline reads: “Transmit. Connect. Act.”.
Title: 50 characters
Your title is a healthy 50 characters: “Consensus | Healthcare Interoperability Simplified”.
Canonical URL set
The canonical URL is https://www.consensus.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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.consensus.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.consensus.com/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.
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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (945 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.consensus.com/products/harmony, which answers with an error. Visitors hit a dead end and search engines drop it.
2 pages share a title
https://www.consensus.com/news and https://www.consensus.com/newsletter all use the title “- Consensus”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.consensus.com/news and https://www.consensus.com/newsletter have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.consensus.com/blog and https://www.consensus.com/events 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 22 found) and read each the way a search engine does.
3 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
32 of 35 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 851 words of copy
The homepage carries about 851 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Request a Demo” and “Learn More”.
16 calls to action
The homepage has 16 calls to action, for example “Request a Demo” and “Learn More”.
Social proof on the page
Social proof on the homepage: 20 testimonial or review blocks, 11 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 consensus.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Hiring
- Hiring
- 1 open role
- Teams
- Creative Team (1)
- Job board
- bamboohr
- Careers page
- www.consensus.com/careers (opens in a new tab)
Company
- Employees
- 418
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on consensus.com, including 9 speed issues and 2 SEO issues. 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.