newport.com website review

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

About 772 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

About 185 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Adobe Tag Manager and Google Analytics and others), adding 1.9 MB and 335 ms of main-thread time.

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

Google Tag Manager costs a phone 234 ms of main-thread work and 318 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.

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

site.com costs a phone 10 ms of main-thread work and 677 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.

mks.com costs a phone 0 ms of main-thread work and 647 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.

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

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

Desktop scores 75 but mobile only 19. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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.

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

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

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

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

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

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

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

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

The layout shifts by 0.361 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Scripts block taps and scrolling for 775 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' largest content (lcp) went from 4.2 s to 8.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.4 MB in 178 requests on a phone: scripts 2.9 MB (92), images 649 KiB (26) and fonts 422 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is 68 characters, so Google will cut it off around 60: “Newport - Photonics Solutions for Extending the Frontiers of Science”.

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

There are 10 <h1> headlines (“MKS to sell Ophir® Optics Business”, “HybrYX-HD® with DynaQuiet™ Soft Isolation System” and “Photonics Spectra - Asphere Optics: Advancements …”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), 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 1,372 pages on newport.com and 41 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.

There is no https://www.newport.com/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.

https://www.newport.com/c/manual-positioning, https://www.newport.com/c/manual-linear-stages, https://www.newport.com/f/anti-backlash-goniometric-rotation-stages, https://www.newport.com/c/motorized-positioning, https://www.newport.com/c/motorized-linear-stages and https://www.newport.com/c/linear-motor-linear-stages and 2 others all use the title “MKS Inc.”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.newport.com/o/special-offers, https://www.newport.com/c/manual-positioning, https://www.newport.com/c/manual-linear-stages, https://www.newport.com/c/manual-rotation-stages, https://www.newport.com/f/anti-backlash-goniometric-rotation-stages and https://www.newport.com/c/motorized-positioning and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.newport.com/o/special-offers, https://www.newport.com/c/manual-positioning, https://www.newport.com/c/manual-linear-stages, https://www.newport.com/c/manual-rotation-stages, https://www.newport.com/f/anti-backlash-goniometric-rotation-stages and https://www.newport.com/c/motorized-positioning and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.newport.com/c/manual-positioning, https://www.newport.com/c/manual-linear-stages, https://www.newport.com/c/manual-rotation-stages, https://www.newport.com/f/anti-backlash-goniometric-rotation-stages, https://www.newport.com/c/motorized-positioning and https://www.newport.com/c/motorized-linear-stages and 4 others took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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 403 (Forbidden)”.

Large scripts ship without source maps.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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

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

Opening the homepage sets 1 cookie (measured from a US location before any click).

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.