theneapolitanjacket.it website review

9 images could be 629 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

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

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

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

8 third-party services load with your homepage (hsappstatic.net, Hubspot and Shopify and others), adding 1.9 MB and 1.0 s of main-thread time.

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

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

hsappstatic.net costs a phone 332 ms of main-thread work and 731 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.

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

Hubspot costs a phone 268 ms of main-thread work and 381 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 206 ms of main-thread work and 369 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 78 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.

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

Polyfills for old browsers add 26 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 22.2 s. Good is under 3.8 s.

Your largest element takes 7.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Three men in suits walking through a maze-like landscape.”.

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

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

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

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 8.6 MB in 336 requests on a phone: media 4.1 MB (2), scripts 1.8 MB (162) and images 1.4 MB (32). Under 2 MB keeps phones on slow connections fast.

1 image (275 KiB) is 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 2.44 g of CO₂e: 293.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

6 elements hidden from screen readers can still receive keyboard focus.

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 19 characters: “Theneapolitanjacket”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your canonical URL points to theneapolitanjacket.com, not theneapolitanjacket.it, so Google may credit that host instead.

There are 2 <h1> headlines (“Theneapolitanjacket” and “SPRING SUMMER 26”). One clear main headline is easier for people and search engines.

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

No XML sitemap at https://theneapolitanjacket.it/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 82 pages on theneapolitanjacket.it and 7 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.

There is no https://theneapolitanjacket.it/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://theneapolitanjacket.it/collections/giacche, https://theneapolitanjacket.it/collections/all, https://theneapolitanjacket.it/collections/giacche-eleganti, https://theneapolitanjacket.it/collections/giacche-casual, https://theneapolitanjacket.it/collections/spring-summer-26 and https://theneapolitanjacket.it/pages/lookbook have no meta description, so Google writes the search snippet from whatever text it finds.

https://theneapolitanjacket.it/collections/giacche, https://theneapolitanjacket.it/collections/all, https://theneapolitanjacket.it/collections/giacche-eleganti, https://theneapolitanjacket.it/collections/giacche-casual, https://theneapolitanjacket.it/collections/leather-collection-26 and https://theneapolitanjacket.it/collections/spring-summer-26 and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://theneapolitanjacket.it/collections/giacche, https://theneapolitanjacket.it/collections/all, https://theneapolitanjacket.it/collections/giacche-eleganti, https://theneapolitanjacket.it/collections/giacche-casual, https://theneapolitanjacket.it/pages/lookbook and https://theneapolitanjacket.it/products/single-breasted-jacket-light-blue and 2 others took over 3 s to send their HTML from our server.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 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”).

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

The homepage has only about 194 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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