Website review, no card needed

biocare.net logo

biocare.net website review

Visit site (opens in a new tab)Reviewed 30 October 202638 issues · 81 checks

This review found 38 issues worth fixing on biocare.net, 12 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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
5.6 s2.9 sMay 9Oct 243.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.9 s
May 16, 20265.2 s
May 23, 20265.2 s
May 30, 20265.2 s
Jun 6, 20265.0 s
Jun 13, 20264.2 s
Jun 20, 20263.6 s
Jun 27, 20263.4 s
Jul 4, 20263.4 s
Jul 11, 20263.4 s
Jul 18, 20263.3 s
Jul 25, 20263.2 s
Aug 1, 20263.3 s
Aug 8, 20263.4 s
Aug 15, 20263.4 s
Aug 22, 20263.6 s
Aug 29, 20263.7 s
Sep 5, 20263.6 s
Sep 12, 20263.7 s
Sep 19, 20263.7 s
Sep 26, 20263.8 s
Oct 3, 20263.9 s
Oct 10, 20263.9 s
Oct 17, 20263.9 s
Oct 24, 20263.9 s
Real-visitor tap response (INP)75th percentile, phones
135 ms110 msMay 9Oct 24126 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026122 ms
May 16, 2026122 ms
May 23, 2026122 ms
May 30, 2026123 ms
Jun 6, 2026121 ms
Jun 13, 2026120 ms
Jun 20, 2026124 ms
Jun 27, 2026125 ms
Jul 4, 2026129 ms
Jul 11, 2026129 ms
Jul 18, 2026121 ms
Jul 25, 2026119 ms
Aug 1, 2026114 ms
Aug 8, 2026113 ms
Aug 15, 2026117 ms
Aug 22, 2026115 ms
Aug 29, 2026123 ms
Sep 5, 2026127 ms
Sep 12, 2026128 ms
Sep 19, 2026132 ms
Sep 26, 2026127 ms
Oct 3, 2026119 ms
Oct 10, 2026119 ms
Oct 17, 2026122 ms
Oct 24, 2026126 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 biocare.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. biocare.net at 0.7 s0.7 s
  2. biocare.net at 1.4 s1.4 s
  3. biocare.net at 2.0 s2.0 s
  4. biocare.net at 2.7 s2.7 s
  5. biocare.net at 3.4 s3.4 s
  6. biocare.net at 4.1 s4.1 s
  7. biocare.net at 4.7 s4.7 s
  8. biocare.net at 5.4 s5.4 s

Speed

10 to fix41
  • Use efficient cache lifetimes

    14.6 s · 2.9 MB

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

  • Render-blocking requests

    3.3 s

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

  • Mobile performance score: 41

    41/100

    Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused JavaScript

    750 ms · 198 KiB

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

  • Improve image delivery

    918 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, searchiq.co and cdn-cookieyes.com and others), adding 577 KiB and 802 ms of main-thread time.

  • Google Tag Manager adds 491 ms

    491 ms

    Google Tag Manager costs a phone 491 ms of main-thread work and 362 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.

  • 9 long tasks on the main thread

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

  • Main-thread work: 3.4 s

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

  • 1,810 HTML elements

    The page has 1,810 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused CSS

    150 ms · 49 KiB

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

  • Legacy JavaScript

    8 KiB

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

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 82 ms

    82 ms

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

Core Web Vitals

12 to fix33
  • 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.

  • Largest Contentful Paint: 35.3 s

    35.3 s

    Your largest element takes 35.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Ready-to-use RNA-ISH probes for The NeoPATH Pro Automated S…”.

  • Time to Interactive: 35.7 s

    35.7 s

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

  • Speed Index: 8.9 s

    8.9 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user CLS: 0.13

    0.13

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Total Blocking Time: 503 ms

    503 ms

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

  • Cumulative Layout Shift: 0.154

    0.154

    The layout shifts by 0.154 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +2%

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

2 checks passed
  • Real-user INP: 123 ms

    123 ms

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

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

    -23%

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

Images and page weight

2 to fix55
  • Page weight: 6.9 MB in 141 requests

    6.9 MB

    Your homepage downloads 6.9 MB in 141 requests on a phone: images 5.8 MB (17), scripts 847 KiB (65) and stylesheets 112 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    NISH-Line-White.svg weighs 4.2 MB. On a phone connection a single image that size takes seconds.

  • About 2.0 g of CO₂ per visit

    1.96 g

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

9 to fixGoogle 9989
  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

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

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

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 13 links without text

    13 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 210 internal links, 11 external

    The homepage links to 210 pages on biocare.net and 11 external pages.

8 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “Biocare is a leading supplier and developer of primary antibodies and automated IHC medical equipment for lab testing. …”.

  • One H1 headline

    Your main headline reads: “NeoPATH Pro <img width="223" height="25" decoding="async" class="bc-home-hero__logoFallback" src="https://biocare.net/wp-content/uploads/n…”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “IHC Primary Antibody Supplier & Manufacturer | Biocare Medical”.

  • Canonical URL set

    The canonical URL is https://biocare.net/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, 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://biocare.net/product-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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

  • llms.txt published

    The site publishes https://biocare.net/llms.txt (7 KiB, 103 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 77 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 10093
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static.searchiq.co/css/latest/siq-mobile.css' from origin 'https://biocare.net' ha…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 15 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 9-field form

    Your longest form asks for 9 fields (0 required). Every extra field lowers completion.

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

    The homepage carries about 250 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: “Learn More”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Return to shop”, “Contact” and “Quick Order”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and The Trade Desk (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 20 cookies set on arrival

    20

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

  • 17 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

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

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 biocare.net, 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
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

Company

Employees
198

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on biocare.net, including 22 speed issues, 1 SEO issue 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