benchsci.com website review

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

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

About 215 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.

3 third-party services load with your homepage (Google Tag Manager, Optanon and Google Analytics), adding 384 KiB and 209 ms of main-thread time.

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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

Your homepage downloads 38.4 MB in 69 requests on a phone: media 32.5 MB (8), images 5.0 MB (12) and scripts 626 KiB (20). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example image at 2,928 px wide, shown at 350 px. Resized copies would save about 177 KiB.

1 image further down the page (203 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

29 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

The homepage links to 35 pages on benchsci.com and 5 external pages.

There is no /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.

/get-started has no <h1> headline, so visitors and search engines get no clear main topic.

/contact and /get-started have 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.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 link to other sites is dead, for example https://emet.benchsci.com/ (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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 812 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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