chicmatchy.com website review

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

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

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

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

25 images could be 676 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.

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

cloudfront.net costs a phone 163 ms of main-thread work and 1.5 MB 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.

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 5.4 MB in 295 requests on a phone: images 2.5 MB (32), scripts 1.7 MB (88) and other files 811 KiB (135). Under 2 MB keeps phones on slow connections fast.

93aaaeffb9d9f0f83b778d330c10fe1f.png weighs 1.2 MB. On a phone connection a single image that size takes seconds.

1 image (1.2 MB) 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.

1 image is downloaded at several times the size a phone draws it, for example 93aaaeffb9d9f0f83b778d330c10fe1f.png at 1,024 px wide, shown at 270 px. Resized copies would save about 442 KiB.

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

35 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

autocomplete attribute must be used correctly: 1 element on the page fails this check, rated serious by axe-core.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings skip levels (h1 → h3), 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 10 characters: “Chicmatchy”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 153 pages on chicmatchy.com and 1 external page.

https://chicmatchy.com/collections/christmas-family-pajamas, https://chicmatchy.com/collections/matching-pajamas-with-baby, https://chicmatchy.com/collections/button-down-pajamas, https://chicmatchy.com/collections/classic-pullover-pajamas, https://chicmatchy.com/collections/henley-3-button-pjs and https://chicmatchy.com/collections/loungewear-jumpsuit and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://chicmatchy.com/collections/classic-pullover-pajamas has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 60 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=343074910&tm=shpfy_ui&Ver=2&mid=b95a88af-c102-4765-8e9f-2843925344ef&bo=1&sid=766baea0deae11f1b1d41b4cd9009c18&vid=766c0b60deae11f18a6303dc0db0d029&vids=1&msclkid=N&pi.

6 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://ipinfo.io/json' from origin 'https://chicmatchy.com' has been blocked by CORS poli…”.

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

The homepage carries about 586 words of visible text.

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