dotmatics.com website review

8 third-party services load with your homepage (Google Tag Manager, Facebook and Optanon and others), adding 1.3 MB and 942 ms of main-thread time.

Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.

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

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

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

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

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

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

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

Polyfills for old browsers add 65 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

Scripts block taps and scrolling for 692 ms in total while the page loads. Good is under 200 ms.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 156 ms to 174 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 2.9 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.7 MB in 134 requests on a phone: scripts 1.8 MB (54), images 453 KiB (20) and fonts 203 KiB (3). Under 2 MB keeps phones on slow connections fast.

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

13 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 154 pages on dotmatics.com and 19 external pages.

/workflows/chromatography is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/whitepapers/the-state-of-chemicals-and-materials-today has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=136020000&Ver=2&mid=f48efca1-716c-454a-a7e4-1ed39c94f752&bo=1&sid=5326f1c0d55111f18960bf3b03808946&vid=532726a0d55111f1bebffd79071ca6a7&vids=1&msclkid=N&pi=918639831&l.

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

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

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

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

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

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

Social proof on the homepage: 6 trust badges. 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.

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

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 859 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 Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 3 mores (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 22 cookies (measured from a US location before any click).

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