Website review, no card needed

bioventus.com logo

bioventus.com website review

Visit site (opens in a new tab)Reviewed 18 November 202630 issues · 80 checks

This review found 30 issues worth fixing on bioventus.com, 12 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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
2.9 s2.1 sMay 30Nov 142.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.4 s
Jun 6, 20262.3 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.3 s
Jul 4, 20262.3 s
Jul 11, 20262.4 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.8 s
Oct 3, 20262.6 s
Oct 10, 20262.5 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.3 s
Nov 7, 20262.3 s
Nov 14, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
89 ms79 msMay 30Nov 1485 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202680 ms
Jun 6, 202682 ms
Jun 13, 202681 ms
Jun 20, 202685 ms
Jun 27, 202685 ms
Jul 4, 202686 ms
Jul 11, 202684 ms
Jul 18, 202685 ms
Jul 25, 202684 ms
Aug 1, 202680 ms
Aug 8, 202681 ms
Aug 15, 202680 ms
Aug 22, 202682 ms
Aug 29, 202686 ms
Sep 5, 202686 ms
Sep 12, 202685 ms
Sep 19, 202684 ms
Sep 26, 202682 ms
Oct 3, 202680 ms
Oct 10, 202682 ms
Oct 17, 202682 ms
Oct 24, 202686 ms
Oct 31, 202688 ms
Nov 7, 202685 ms
Nov 14, 202685 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 bioventus.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bioventus.com at 0.6 s0.6 s
  2. bioventus.com at 1.3 s1.3 s
  3. bioventus.com at 1.9 s1.9 s
  4. bioventus.com at 2.6 s2.6 s
  5. bioventus.com at 3.2 s3.2 s
  6. bioventus.com at 3.9 s3.9 s
  7. bioventus.com at 4.5 s4.5 s
  8. bioventus.com at 5.2 s5.2 s

Speed

9 to fix51
  • Reduce unused JavaScript

    6.8 s · 963 KiB

    About 963 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.8 s faster on a phone.

  • Render-blocking requests

    4.3 s

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

  • Minify JavaScript

    1.1 s · 220 KiB

    220 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    900 ms · 216 KiB

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

  • Mobile performance score: 51

    51/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google CDN, Optanon and Other Google APIs/SDKs and others), adding 1.1 MB and 671 ms of main-thread time.

  • Use efficient cache lifetimes

    500 ms · 72 KiB

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

  • Google CDN adds 495 ms

    495 ms

    Google CDN costs a phone 495 ms of main-thread work and 742 KiB 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.

  • Main-thread work: 3.8 s

    A phone's processor spends 3.8 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Improve image delivery

    250 ms · 188 KiB

    2 images could be 188 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • Legacy JavaScript

    150 ms · 44 KiB

    Polyfills for old browsers add 44 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 14 long tasks on the main thread

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

  • Minify CSS

    150 ms · 20 KiB

    20 KiB could be saved by minifying CSS.

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

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

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

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

  • First Contentful Paint: 10.9 s

    10.9 s

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

  • Largest Contentful Paint: 16.6 s

    16.6 s

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

  • Time to Interactive: 18.5 s

    18.5 s

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

  • Speed Index: 10.9 s

    10.9 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Total Blocking Time: 253 ms

    253 ms

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

5 checks passed
  • Real-user INP: 83 ms

    83 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 563 ms

    563 ms

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

  • Cumulative Layout Shift: 0.041

    0.041

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

Images and page weight

2 to fix60
  • Page weight: 20.6 MB in 92 requests

    20.6 MB

    Your homepage downloads 20.6 MB in 92 requests on a phone: media 17.0 MB (2), scripts 1.9 MB (31) and images 693 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    17 KiB

    1 image is downloaded at several times the size a phone draws it, for example website-image-uai-1032x310.jpg at 1,032 px wide, shown at 318 px. Resized copies would save about 17 KiB.

  • 1 image in older formats

    1 image (118 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.

  • About 5.8 g of CO₂ per visit

    5.84 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

2 to fixGoogle 9797
  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

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

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

2 checks passed
  • Every image has alt text

    All 7 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9288
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 9 links with vague text

    9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 54 internal links, 14 external

    The homepage links to 54 pages on bioventus.com and 14 external pages.

7 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Bioventus products, orthobiologics, biologics and devices for bone healing and osteoartritis pain relief are known as i…”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “Bioventus - Innovations For Active Healing”.

  • Canonical URL set

    The canonical URL is https://www.bioventus.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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 http://www.bioventus.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

Other pages

4 to fix81
  • 4 pages share a title

    /, https://www.bioventus.com/de, https://www.bioventus.com/fr and https://www.bioventus.com/es all use the title “Bioventus - Innovations For Active Healing”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://www.bioventus.com/about-us, https://www.bioventus.com/about-us/board-members, https://www.bioventus.com/about-us/grants-committee, https://www.bioventus.com/about-us/compliance, https://www.bioventus.com/acquisitions and https://www.bioventus.com/about-us/bio-dei and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.bioventus.com/de, https://www.bioventus.com/fr and https://www.bioventus.com/es use the same meta description. A description written for each page earns more clicks.

  • 11 pages without an H1

    https://www.bioventus.com/de, https://www.bioventus.com/fr, https://www.bioventus.com/es, https://www.bioventus.com/about-us, https://www.bioventus.com/about-us/leadership and https://www.bioventus.com/about-us/board-members and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.bioventus.com/about-us/board-members 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 33 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.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 12 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'toLowerCase')”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • 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 326 words of copy

    The homepage carries about 326 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: “CONTACT US”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Grants & Donations Request Process”, “Investigator Initiated Study Request” and “Contact Us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 6 cookies set on arrival

    6

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

  • 8 other companies contacted

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

2 checks passed
  • Consent tool: OneTrust

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

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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on bioventus.com, including 16 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