propercloth.com website review

19 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

About 451 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

About 171 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.1 s.

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

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

8 third-party services load with your homepage (Google Tag Manager, runconverge.com and Facebook and others), adding 1.5 MB and 2.5 s of main-thread time.

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

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

runconverge.com costs a phone 623 ms of main-thread work and 428 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 388 ms. During a long task the page ignores taps.

Polyfills for old browsers add 50 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

Facebook costs a phone 291 ms of main-thread work and 277 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 264 ms of main-thread work and 194 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,565 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

12 KiB could be saved by minifying JavaScript.

Desktop scores 67 but mobile only 35. A gap that wide usually means heavy scripts and images that hit phones hardest.

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 19.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

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

Your homepage downloads 8.1 MB in 164 requests on a phone: media 2.9 MB (1), images 2.3 MB (37) and scripts 1.8 MB (60). Under 2 MB keeps phones on slow connections fast.

tile_suits_fa26b.jpg weighs 570 KiB. On a phone connection a single image that size takes seconds.

10 images are downloaded at several times the size a phone draws them, for example tile_suits_fa26b.jpg at 1,500 px wide, shown at 358 px. Resized copies would save about 964 KiB.

16 images (1.8 MB) 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 2.28 g of CO₂e: 274.0 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.

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

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

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

The homepage links to 316 pages on propercloth.com and 3 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.

Your homepage links to https://propercloth.com/shop, https://propercloth.com/shop/new-arrivals, https://propercloth.com/shop/seasonal-trends, https://propercloth.com/shop/wardrobe-essentials, https://propercloth.com/shop/weddings and https://propercloth.com/shop/the-indigo-shop and 6 others, which answer with an error. Visitors hit a dead end and search engines drop them.

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

3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=4013723&Ver=2&mid=787f4096-29bd-40c5-828d-f67f400003b6&bo=1&sid=846a4d50caec11f1887805dcce2cc51b&vid=846a5880caec11f19ede8574c7b91edf&vids=1&msclkid=N&pi=918639831&lg=.

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

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

The homepage carries about 353 words of visible text.

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