tianello.com website review

About 3.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 25.0 s faster on a phone.

YouTube costs a phone 1.5 s of main-thread work and 4.8 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.

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

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

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

8 third-party services load with your homepage (YouTube, Shopify and Google Tag Manager and others), adding 7.1 MB and 2.7 s of main-thread time.

14 images could be 659 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

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

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

cloudfront.net costs a phone 116 ms of main-thread work and 425 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 238 ms. During a long task the page ignores taps.

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

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

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

Your largest element takes 44.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “FJAD-504-WAS-Front-CU.JPG”.

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

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

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

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

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

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

Your homepage downloads 10.2 MB in 409 requests on a phone: scripts 6.6 MB (143), images 1.4 MB (49) and other files 860 KiB (171). Under 2 MB keeps phones on slow connections fast.

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

20 buttons have no accessible name, so screen readers announce just “button”.

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

2 links inside paragraphs rely on colour alone to stand out.

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

10 images have no alt text, which hurts accessibility and image search.

41 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Your title is 83 characters, so Google will cut it off around 60: “Tencel Clothing - Washable Silk Clothing | Tianello by Steve Barraza – Tianello.com”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 18 <h1> headlines (“”, “Tianello "Oriana" French Knit "Siri" Tunic” and “Tianello - Sueded Japanese CUPRO Georgette L.S. "…”). One clear main headline is easier for people and search engines.

Your meta description is 316 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.

The homepage links to 154 pages on tianello.com and 5 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

/collections/jackets, /pages/prints-at-a-glance, /collections/burnout, /collections/linen and /collections/knits have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/prints-at-a-glance and /pages/fabrics have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 47 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=5857427&Ver=2&mid=31ff24a9-efee-45c5-a966-d8f0c634271c&bo=1&sid=2c41e9c0d8ae11f188eb054f61f3c8a3&vid=2c420150d8ae11f18b28f11ec1ff82a4&vids=1&msclkid=N&pi=918639831&lg=.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were 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”).

Requests the notification permission on page load.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 17 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 16 fields (0 required). Every extra field lowers completion.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 2 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 18 cookies, 1 of them by other companies (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 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.