Programmable

Website review, no card needed

vero-biotech.com logo

vero-biotech.com website review

Visit site (opens in a new tab)Reviewed 2 November 202621 issues · 79 checks

This review found 21 issues worth fixing on vero-biotech.com, 6 of them high impact, across 79 checks. The most urgent: fails Core Web Vitals for real visitors. 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

Site score

89B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.8 s907 msMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.0 s
May 23, 20261.0 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jul 18, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.5 s
Sep 26, 20261.4 s
Oct 3, 20261.5 s
Oct 10, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
72 ms64 msMay 16Oct 3166 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202665 ms
May 23, 202670 ms
May 30, 202670 ms
Jun 6, 202671 ms
Oct 3, 202671 ms
Oct 10, 202665 ms
Oct 31, 202666 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

www.vero-biotech.com (opens in a new tab)
Full-page screenshot of vero-biotech.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

3 to fix91

  • Render-blocking requests

    700 ms

    10 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

  • Reduce unused JavaScript

    396 KiB

    About 396 KiB of JavaScript is downloaded but never used on this page.

  • Google CDN adds 315 ms

    315 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google CDN, Cookiebot and Other Google APIs/SDKs and others), adding 953 KiB and 459 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Improve image delivery

    67 KiB

    2 images could be 67 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    48 KiB

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

  • Use efficient cache lifetimes

    34 KiB

    3 files are served with short cache lifetimes, so returning visitors download them again (34 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.

3 checks passed

  • Mobile performance score: 91

    91/100

    Your mobile performance score is 91. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.3 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

6 to fix100

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

  • Time to Interactive: 9.3 s

    9.3 s

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

  • Largest content (LCP) got 63% slower for real visitors

    +63%

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • Speed Index: 4.9 s

    4.9 s

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Tap response (INP) held steady for real visitors

    -3%

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

7 checks passed

  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 66 ms

    66 ms

    Real visitors wait 66 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: 1.5 s

    1.5 s

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

  • Largest Contentful Paint: 2.2 s

    2.2 s

    Your largest element renders in 2.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Innovation in the Delivery of Inhaled Nitric Oxide”.

  • Total Blocking Time: 139 ms

    139 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100

  • About 0.5 g of CO₂ per visit

    0.48 g

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

4 checks passed

  • Page weight: 1.7 MB in 62 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 62 requests on a phone: scripts 1,004 KiB (35), other files 349 KiB (2) and fonts 144 KiB (7). That is a lean page.

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed

  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9291

  • 2 H1 headlines

    There are 2 <h1> headlines (“Innovation in the Delivery of Inhaled Nitric Oxide” and “Let’s Talk About Respiratory Care”). One clear main headline is easier for people and search engines.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 4 links with vague text

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

  • 21 internal links, 26 external

    The homepage links to 21 pages on vero-biotech.com and 26 external pages.

7 checks passed

  • Meta description: 103 characters

    Your meta description is 103 characters: “Our commitment is innovation in the life sciences space. See how GENOSYL DS epitomizes that commitment.”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “Inhaled Nitric Oxide Delivery System | VERO Biotech”.

  • Canonical URL set

    The canonical URL is https://www.vero-biotech.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.vero-biotech.com/sitemap_index.xml.

AI search readiness

100

  • No llms.txt

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

Other pages

2 to fix90

  • 7 pages without a meta description

    https://www.vero-biotech.com/contact-us, https://www.vero-biotech.com/press-releases/vero-biotechs-genosyl-delivery-system-recognized-as-a-technological-breakthrough-at-premier-inc-s-annual-supplier-innovation-celebration, https://www.vero-biotech.com/press-releases/vero-biotechs-second-generation-genosyl-delivery-system-ds-receives-fda-approval-in-anesthesia-in-the-surgical-suite, https://www.vero-biotech.com/press-releases/vero-biotech-raises-30-million-to-accelerate-commercialization-of-its-innovative-tankless-inhaled-nitric-oxide-delivery-system, https://www.vero-biotech.com/medical-information-request and https://www.vero-biotech.com/privacy-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.vero-biotech.com/news-events and https://www.vero-biotech.com/medical-information-request have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 internal pages checked

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

5 checks passed

  • Linked pages load

    All 11 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed

  • No console errors

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

  • Tap targets are thumb-sized

    12 of 13 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69

  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 612 words of visible text.

5 checks passed

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us”, “Learn More” and “Schedule my demo”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 5 other companies contacted

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

2 checks passed

  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 vero-biotech.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 Analytics
Hosting
Google Cloud

Hiring

Hiring
1 open role
Job board
smartrecruiters
Careers page
jobs.smartrecruiters.com/verobiotech (opens in a new tab)

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on vero-biotech.com, including 9 speed issues, 3 SEO issues 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