esi.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 LCP: 6.5 s

  6.5 s

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

• Real-user FCP: 5.2 s

  5.2 s

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

• Real-user TTFB: 3.8 s

  3.8 s

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

• Real-user CLS: 0.25

  0.25

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

• Largest content (LCP) held steady for real visitors

  -1%

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

• Page weight: 2.4 MB

  2.4 MB

  Your homepage downloads 2.4 MB on a phone. Under 2 MB keeps phones on slow connections fast.

• About 0.7 g of CO₂ per visit

  0.69 g

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

• ARIA attributes must conform to valid values (1 element)

  ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

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

  Elements (1)

• 2 links without text

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

  Elements (2)

• Headings skip levels

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

  View source

• No structured data

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

• 6 H1 headlines

  There are 6 <h1> headlines (“MKS to sell Ophir® Optics Business”, “The Next Generation has arrived” and “Better. Faster. Consistent.”). One clear main headline is easier for people and search engines.

• No social preview image

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

• No X (Twitter) card tag

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

• 188 internal links, 5 external

  The homepage links to 188 pages on esi.com and 5 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.

• 2 pages share a title

  /f/allegro-xp-mlcc-testing-system and /f/mlcc-machine-tooling all use the title “MKS Inc.”. Search engines can't tell which page to show for a search, so each competes with the others.

  Elements (2)

• 5 pages without a meta description

  /f/capstone-laser-system, /f/geode-g2-laser-via-drilling-system, /f/allegro-xp-mlcc-testing-system, /f/mlcc-machine-tooling and /f/replacement-carrier-plates have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (5)

• 2 pages without an H1

  /f/allegro-xp-mlcc-testing-system and /f/mlcc-machine-tooling have no <h1> headline, so visitors and search engines get no clear main topic.

• 4 pages slow to respond

  /f/geode-g2-laser-via-drilling-system, /s/mlcc-testing, /f/allegro-xp-mlcc-testing-system and /f/mlcc-machine-tooling took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• 10 broken images

  10 images failed to load on a phone, for example https://api.p1.mks.com/medias/sys_master/logos/logos/hf0/hd4/9850584498206/logo-mks-esi-wht.png.

• 6 small tap targets

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

• 4 JavaScript errors while loading

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

• Short HSTS lifetime

  HSTS is set, but max-age is 182 days; one year is the recommended minimum.

• No Referrer-Policy

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

• No Permissions-Policy

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

• No CAA record

  esi.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

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

• 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 analytics detected

  No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

• Only about 104 words

  The homepage has only about 104 words of visible text; thin pages give Google and first-time buyers little to go on.

• Phone number is not tap-to-call

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

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

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

• Email authentication score: 75/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.

• 3 cookies set on arrival

  3

  Opening the homepage sets 3 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.

• 1 other company contacted

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