tuttiandco.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and Google CDN and others), adding 1.3 MB and 390 ms of main-thread time.

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

Shopify costs a phone 191 ms of main-thread work and 720 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 173 ms of main-thread work and 400 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.

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

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

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

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

32 KiB could be saved by minifying JavaScript.

About 28 KiB of CSS is downloaded but never applied on this page.

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

Polyfills for old browsers add 19 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.

5 KiB JavaScript is shipped twice across bundles.

2 KiB could be saved by minifying CSS.

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

The layout shifts by 0.292 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.3 MB in 500 requests on a phone: other files 1.3 MB (250), scripts 1.2 MB (171) and images 1.1 MB (17). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example 98dd8c1c-107a-4221-b2f2-2b760e1bc830.jpeg at 1,080 px wide, shown at 184 px. Resized copies would save about 255 KiB.

2 images (317 KiB) 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.

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

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

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 204 pages on tuttiandco.com and 10 external pages.

https://www.tuttiandco.com/pages/leather-clutch, https://www.tuttiandco.com/pages/restore, https://www.tuttiandco.com/collections/hoops, https://www.tuttiandco.com/collections/studs, https://www.tuttiandco.com/collections/drops and https://www.tuttiandco.com/collections/huggies-small-hoops have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tuttiandco.com/collections/new-arrivals-copy, https://www.tuttiandco.com/collections/new-in-earrings, https://www.tuttiandco.com/collections/new-in-earrings-copy and https://www.tuttiandco.com/collections/new-in-necklaces-copy use the same meta description. A description written for each page earns more clicks.

https://www.tuttiandco.com/pages/leather-clutch and https://www.tuttiandco.com/pages/restore have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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