labconco.com website review

Reduce initial server response time. Google estimates savings of 2.8 s on a phone.

The HTML itself could arrive about 2.8 s sooner: redirects, a slow server response or missing compression delay everything after it.

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

Your server takes 2.9 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

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

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

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

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

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

4 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and Cloudflare and others), adding 297 KiB and 188 ms of main-thread time.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 100 ms.

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

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

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.

Your largest element takes 7.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Laboratory space with installed equipment, lab planning”. Most of its time is time to first byte (2.9 s).

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

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

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

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

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

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

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

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

Your homepage downloads 2.2 MB in 116 requests on a phone: scripts 961 KiB (72), HTML 534 KiB (1) and images 412 KiB (18). Under 2 MB keeps phones on slow connections fast.

50_Year_BSC_Homepage_Banner_Image_1920x1080_blue_tint.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).

2 images are downloaded at several times the size a phone draws them, for example freezonegroup-1000x1000.png at 1,000 px wide, shown at 200 px. Resized copies would save about 90 KiB.

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

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 5 <h1> headlines (“For the Love of the Lab”, “Direct Access to Peer-Reviewed Studies” and “A Legacy of Biosafety Innovation”). One clear main headline is easier for people and search engines.

Your meta description is 194 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 171 pages on labconco.com and 15 external pages.

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.

https://www.labconco.com/category/food-ag and https://www.labconco.com/food-bev-ag all use the title “Food, Bev & Ag”. Search engines can't tell which page to show for a search, so each competes with the others.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 739 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Microsoft Clarity (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.

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

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