tin-haus.com website review

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

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

8 third-party services load with your homepage (Facebook, POWr and TikTok and others), adding 1.4 MB and 790 ms of main-thread time.

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

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

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

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

Mailchimp costs a phone 118 ms of main-thread work and 347 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.

Shopify costs a phone 78 ms of main-thread work and 325 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 23 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

6 long tasks block the main thread while loading, the longest for 150 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 21 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.

3 KiB could be saved by minifying JavaScript.

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

Your largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A New Chapter is Taking Shape We are Rebranding with Intent…”.

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

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

1 image 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 4.1 MB in 369 requests on a phone: images 1.4 MB (31), scripts 1.2 MB (144) and other files 1,015 KiB (174). Under 2 MB keeps phones on slow connections fast.

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

ARIA attributes must conform to valid values: 8 elements on the page fail this check, rated critical by axe-core.

4 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

The homepage links to 85 pages on tin-haus.com and 4 external pages.

https://tin-haus.com/collections/rings, https://tin-haus.com/collections/rings/Women's-Rings, https://tin-haus.com/collections/rings/Men's-Rings, https://tin-haus.com/collections/earrings, https://tin-haus.com/collections/bracelet and https://tin-haus.com/collections/necklace and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://tin-haus.com/collections/rings/Women's-Rings, whose canonical is https://tin-haus.com/collections/rings/women%27s-rings. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

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.

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

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