thingtrax.com website review

16 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.9 s.

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

12 images could be 386 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and pipedriveassets.com and others), adding 954 KiB and 515 ms of main-thread time.

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

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

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

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

51 KiB could be saved by minifying CSS.

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

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

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

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

Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Computer vision–driven AI agents that observe production, r…”. Most of its time is element render delay (3.4 s).

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

22 images have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.5 MB in 106 requests on a phone: images 1.9 MB (54), scripts 1.2 MB (21) and stylesheets 330 KiB (12). Under 2 MB keeps phones on slow connections fast.

12 images (1.4 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.

19 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example 1.png at 960 px wide, shown at 100 px. Resized copies would save about 243 KiB.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

1 element hidden from screen readers can still receive keyboard focus.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

There are 7 <h1> headlines (“Agentic Manufacturing Operations Platform”, “How Agentic Manufacturing Operations Work” and “A Composable Agentic Operations Platform”). One clear main headline is easier for people and search engines.

The homepage links to 29 pages on thingtrax.com and 0 external pages.

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://thingtrax.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://thingtrax.com/count, https://thingtrax.com/quality-agent, https://thingtrax.com/label-agent, https://thingtrax.com/line-efficiency, https://thingtrax.com/about and https://thingtrax.com/privacy have no meta description, so Google writes the search snippet from whatever text it finds.

https://thingtrax.com/demo and https://thingtrax.com/privacy have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 8 pages linked from your homepage and read each the way a search engine does.

Social proof on the homepage: 1 trust badge. 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 716 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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 6 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.