tomsstudio.com website review

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

Shopify costs a phone 1.1 s of main-thread work and 1.2 MB 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.

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and konvoai.com and others), adding 2.2 MB and 2.1 s of main-thread time.

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

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

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

Klaviyo costs a phone 461 ms of main-thread work and 198 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.

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

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

konvoai.com costs a phone 219 ms of main-thread work and 458 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.

166 KiB could be saved by minifying JavaScript.

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

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

11 KiB JavaScript is shipped twice across bundles.

8 KiB could be saved by minifying CSS.

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.

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

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

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

Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slideshow Image 1”.

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

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

Your homepage downloads 4.5 MB in 306 requests on a phone: scripts 2.3 MB (148), images 1.3 MB (53) and fonts 273 KiB (8). Under 2 MB keeps phones on slow connections fast.

brass-wren-2.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

14 tap targets are too small or too close together to hit reliably with a finger.

1 image has no alt text, which hurts accessibility and image search.

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

Elements with visible text labels do not have matching accessible names. (21 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 67 characters, so Google will cut it off around 60: “Tom's Studio - Refillable pens, calligraphy pens and creative tools”.

Your meta description is 189 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link has no real href, so search engines can't follow it.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 434 pages on tomsstudio.com and 5 external pages.

https://tomsstudio.com/collections/studio-handmade and https://tomsstudio.com/collections/field-mouse-collection have no meta description, so Google writes the search snippet from whatever text it finds.

https://tomsstudio.com/products/the-everyday-writing-advent-calendar, https://tomsstudio.com/collections, https://tomsstudio.com/collections/all-pens, https://tomsstudio.com/collections/lumos, https://tomsstudio.com/collections/wren and https://tomsstudio.com/collections/studio-handmade and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://tomsstudio.com/products/the-everyday-writing-advent-calendar, https://tomsstudio.com/collections/all-pens, https://tomsstudio.com/collections/lumos, https://tomsstudio.com/collections/wren, https://tomsstudio.com/collections/studio-handmade and https://tomsstudio.com/collections/ori-collection and 4 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

18 of 51 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: the server responded with a status of 502 ()”.

1 image is served at too low a resolution for sharp phone screens.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 2,990 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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