thomasarts.com website review

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

Google Tag Manager costs a phone 1.6 s of main-thread work and 495 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

Google CDN costs a phone 1.1 s of main-thread work and 753 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Other Google APIs/SDKs and others), adding 1.8 MB and 4.2 s of main-thread time.

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

Other Google APIs/SDKs costs a phone 897 ms of main-thread work and 301 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.

About 782 KiB of JavaScript is downloaded but never used on this page.

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

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

Accessibe Accessibility Overlay costs a phone 339 ms of main-thread work and 243 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 150 ms).

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

1 image could be 16 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

9 KiB could be saved by minifying CSS.

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

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.

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

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

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

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

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

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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 24.6 MB in 124 requests on a phone: media 21.5 MB (2), scripts 1.9 MB (46) and images 405 KiB (34). Under 2 MB keeps phones on slow connections fast.

5 images further down the page (132 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h3 → h5), 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.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 25 pages on thomasarts.com and 5 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://www.thomasarts.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.thomasarts.com/get-in-touch, https://www.thomasarts.com/work, https://www.thomasarts.com/expertise, https://www.thomasarts.com/careers, https://www.thomasarts.com/team and https://www.thomasarts.com/insights and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.thomasarts.com/work, https://www.thomasarts.com/expertise, https://www.thomasarts.com/careers, https://www.thomasarts.com/team, https://www.thomasarts.com/contact and https://www.thomasarts.com/diversity-inclusion and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

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 349 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

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

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