benchling.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user CLS: 0.36

  0.36

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

• Real-user INP: 304 ms

  304 ms

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

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

  +11%

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

• Page weight: 7.1 MB

  7.1 MB

  Your homepage downloads 7.1 MB on a phone, 4.4 MB of it images (63%). Under 2 MB keeps phones on slow connections fast.

• 4 images over 500 KB

  4 images weigh 2.2 MB together. On a phone connection a single image that size takes seconds.

  Elements (4)

• 5 images far larger than shown

  916 KiB

  5 images are downloaded at several times the size a phone draws them, for example Scientific_context.png at 1,252 px wide, shown at 303 px. Resized copies would save about 916 KiB.

  Elements (5)

• 6 images in older formats

  6 images (2.3 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.

  Elements (5)

• About 2.0 g of CO₂ per visit

  2.00 g

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

• 5 tap targets too small

  5 tap targets are too small or too close together to hit reliably with a finger.

  Elements (3)

• ARIA commands must have an accessible name (1 element)

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

  Elements (1)

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

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

  Elements (3)

• 5 links without text

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

  Elements (3)

• No structured data

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

• Meta description is long (164 characters)

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

  View source

• 87 internal links, 8 external

  The homepage links to 87 pages on benchling.com and 8 external pages.

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

• No llms.txt

  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.

• 1 page without a meta description

  /request-demo has no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (1)

• 2 pages share a meta description

  /biologics and /pipebio use the same meta description. A description written for each page earns more clicks.

• 1 page without an H1

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

• 15 internal pages checked

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

• 1 broken image

  1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=136011854&tm=gtm002&Ver=2&mid=ff91b1c1-0c11-4386-8486-41b75f58c6fe&bo=1&sid=981c8690d68d11f186bc7d7fabbe3dc1&vid=981cd330d68d11f19726e55e45445aee&vids=1&msclkid=N&pi=9.

• 15 small tap targets

  15 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

• 1 JavaScript error while loading

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

• 1 link through redirect chains

  1 link go through two or more redirects, for example https://help.benchling.com/.

• No Referrer-Policy

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

• No security.txt

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

• DNSSEC is off

  benchling.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• 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 phone number on the homepage

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

• 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 opening hours

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

• No form on the homepage

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

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

  The homepage carries about 583 words of visible text.

• Email authentication score: 95/100

  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.

• 8 trackers load before any consent

  8

  Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 3 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

• 39 cookies set on arrival

  39

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

• No consent tool detected

  No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

• 42 other companies contacted

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