Website review, no card needed

ngbiotech.com logo

ngbiotech.com website review

Visit site (opens in a new tab)Reviewed 25 October 202635 issues · 79 checks

This review found 35 issues worth fixing on ngbiotech.com, 12 of them high impact, across 79 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
4.5 s2.4 sMay 2Oct 173.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.7 s
May 9, 20262.7 s
May 16, 20263.0 s
May 23, 20263.1 s
May 30, 20263.1 s
Jun 6, 20263.4 s
Jun 13, 20263.3 s
Jun 20, 20263.6 s
Jun 27, 20263.8 s
Jul 4, 20263.6 s
Jul 11, 20263.7 s
Jul 18, 20263.6 s
Jul 25, 20263.5 s
Aug 1, 20263.9 s
Aug 8, 20264.1 s
Aug 15, 20264.1 s
Aug 22, 20264.1 s
Aug 29, 20264.3 s
Sep 5, 20263.6 s
Sep 12, 20264.1 s
Sep 19, 20264.0 s
Sep 26, 20264.0 s
Oct 3, 20263.9 s
Oct 10, 20263.5 s
Oct 17, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
104 ms76 msMay 2Oct 1788 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202690 ms
May 9, 202690 ms
May 16, 202691 ms
May 23, 202692 ms
May 30, 202692 ms
Jun 6, 202690 ms
Jun 13, 202684 ms
Jun 20, 202682 ms
Jun 27, 202685 ms
Jul 4, 202679 ms
Jul 11, 202682 ms
Jul 18, 202687 ms
Jul 25, 202687 ms
Aug 1, 202689 ms
Aug 8, 202693 ms
Aug 15, 202693 ms
Aug 22, 202689 ms
Aug 29, 202694 ms
Sep 5, 202687 ms
Sep 12, 202686 ms
Sep 19, 202694 ms
Sep 26, 202694 ms
Oct 3, 2026101 ms
Oct 10, 202697 ms
Oct 17, 202688 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 ngbiotech.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix65
  • Use efficient cache lifetimes

    6.2 s · 3.3 MB

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

  • Improve image delivery

    3.2 s · 1.0 MB

    6 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.2 s faster on a phone.

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65 (desktop: 80). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    450 ms · 121 KiB

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

  • Cookiebot adds 345 ms

    345 ms

    Cookiebot costs a phone 345 ms of main-thread work and 155 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: 2.1 s

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Cookiebot and Google Tag Manager), adding 333 KiB and 345 ms of main-thread time.

  • 8 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Reduce unused JavaScript

    27 KiB

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

  • 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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 8.8 s

    8.8 s

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

  • Time to Interactive: 15.2 s

    15.2 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

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

    +24%

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

  • Real-user FCP: 2.8 s

    2.8 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Speed Index: 5.5 s

    5.5 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Total Blocking Time: 205 ms

    205 ms

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

  • Tap response (INP) held steady for real visitors

    +3%

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

3 checks passed
  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 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.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix53
  • 1 image over 500 KB

    Banner-homepage-3.png weighs 1.3 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.7 MB in 51 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 51 requests on a phone: images 2.9 MB (13), scripts 593 KiB (23) and stylesheets 126 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 10 images in older formats

    10 images (2.8 MB) are 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.

  • An image on the first screen is lazy-loaded

    3.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 1.1 g of CO₂ per visit

    1.05 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9694
  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious 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.

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

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

SEO

4 to fixGoogle 8576
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 5 links with vague text

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

  • 65 internal links, 18 external

    The homepage links to 65 pages on ngbiotech.com and 18 external pages.

5 checks passed
  • Title: 30 characters

    Your title is a healthy 30 characters: “NG Biotech - Home - NG Biotech”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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.ngbiotech.com/sitemap_index.xml.

AI search readiness

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

  • llms.txt published

    The site publishes https://www.ngbiotech.com/llms.txt (1 KiB, 15 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 15 pages without a meta description

    https://www.ngbiotech.com/about-us, https://www.ngbiotech.com/products, https://www.ngbiotech.com/antimicrobial-resistance, https://www.ngbiotech.com/ng-test-carba-5, https://www.ngbiotech.com/ng-test-ctx-m-multi and https://www.ngbiotech.com/ng-test-mcr-1 and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

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

    The homepage carries about 277 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “CONTACT US”.

  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 3 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 ngbiotech.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on ngbiotech.com, including 17 speed issues, 4 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