systron.com website review

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

3 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

Your mobile performance score is 72 (desktop: 83). Pages that score under 90 lose visitors before the first paint.

About 130 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 740 ms faster on a phone.

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

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

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

10 KiB could be saved by minifying CSS.

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

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

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

6 KiB could be saved by minifying JavaScript.

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 see the first content after 3.1 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “EMCORE”. Most of its time is resource load delay (1.9 s).

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

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

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

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

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

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

1 image is downloaded at several times the size a phone draws it, for example SDI-logo2-scaled.jpg at 2,560 px wide, shown at 366 px. Resized copies would save about 108 KiB.

1 image (133 KiB) is 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.

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

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

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

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

Your title is only 23 characters: “Systron Donner - EMCORE”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Systron Donner Inertial is Now EMCORE” and “EMCORE acquired Systron Donner Inertial in 2019, …”). One clear main headline is easier for people and search engines.

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

The homepage links to 115 pages on systron.com and 1 external page.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://www.emcore.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.emcore.com/solutions/military-ground-vehicle-navigation and https://www.emcore.com/applications/navigation-control/military-ground-vehicle-navigation all use the title “Military Ground Vehicle Navigation - EMCORE”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.emcore.com/products, https://www.emcore.com/gyros-multi-axis-sensors, https://www.emcore.com/inertial-measurement-units-imu, https://www.emcore.com/inertial-navigation-systems-ins and https://www.emcore.com/tacnav-tactical-navigation have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.emcore.com/products has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage has only about 231 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.

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

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

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