jeanpatrique.com website review

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

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

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

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

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

6 third-party services load with your homepage (Google Tag Manager, wonderpush.com and Cloudflare and others), adding 312 KiB and 278 ms of main-thread time.

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

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

Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need.

24 KiB could be saved by minifying JavaScript.

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

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 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Shop with confidence thanks to our 100-day money-back guara…”.

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

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

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

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 2.5 MB in 101 requests on a phone: images 1.4 MB (10), scripts 739 KiB (45) and stylesheets 315 KiB (37). Under 2 MB keeps phones on slow connections fast.

2 images (137 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 0.72 g of CO₂e: 85.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

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

Headings skip levels (h2 → h6), 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 24 characters: “Homepage - Jean Patrique”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“The Griddle Me This Cast Aluminium Griddle Plate …”, “Bio Supreme Ceramic Frying Pan Set” and “The Whatever Pan – Cast Aluminium Griddle Pan wit…”). One clear main headline is easier for people and search engines.

The homepage links to 167 pages on jeanpatrique.com and 3 external pages.

There is no https://jeanpatrique.com/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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://jeanpatrique.com/product-category/cookware, https://jeanpatrique.com/product-category/cookware/grill-griddle-pans, https://jeanpatrique.com/product-category/cookware/frying-pans-skillets, https://jeanpatrique.com/product-category/cookware/saucepans-stockpots, https://jeanpatrique.com/product-category/cookware/casserole-dutch-ovens and https://jeanpatrique.com/product-category/cookware/woks-sizzlers and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

24 of 50 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

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 1,244 words of visible text.

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