pittconrad.com website review

Other Google APIs/SDKs costs a phone 1.5 s of main-thread work and 154 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.

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

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

7 third-party services load with your homepage (Other Google APIs/SDKs, Google CDN and Shopify and others), adding 1.3 MB and 2.0 s of main-thread time.

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

About 60 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 CDN costs a phone 222 ms of main-thread work and 320 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 209 ms of main-thread work and 438 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 2,460 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

8 files are served with short cache lifetimes, so returning visitors download them again (53 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.

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

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

Your largest element takes 4.7 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 6.0 s (Speed Index). Good is under 3.4 s.

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

Your homepage downloads 15.2 MB in 507 requests on a phone: media 11.9 MB (1), scripts 1.2 MB (173) and other files 1.1 MB (256). Under 2 MB keeps phones on slow connections fast.

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

5 text elements don'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.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

Your title is 83 characters, so Google will cut it off around 60: “Pitt Conrad | Artisan Accessories | Handcrafted | Made in Italy – Pitt Conrad Group”.

There are 2 <h1> headlines (“Pitt Conrad Group” and “Pre-Black Friday · 27.11.2026Cappelli e capi cuci…”). One clear main headline is easier for people and search engines.

The homepage links to 154 pages on pittconrad.com and 0 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.

https://pittconrad.com/en-us/collections/uomo-felpe, https://pittconrad.com/en-us/collections/uomo-t-shirt-e-maglie, https://pittconrad.com/en-us/collections/uomo-maglieria, https://pittconrad.com/en-us/collections/uomo-pantaloni-e-jogger, https://pittconrad.com/en-us/collections/uomo-camicie and https://pittconrad.com/en-us/collections/uomo-capispalla and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://pittconrad.com/en-us/collections, https://pittconrad.com/en-us/collections/uomo, https://pittconrad.com/en-us/collections/uomo-felpe, https://pittconrad.com/en-us/collections/uomo-t-shirt-e-maglie, https://pittconrad.com/en-us/collections/uomo-maglieria and https://pittconrad.com/en-us/collections/uomo-pantaloni-e-jogger and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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