cdpeacock.com website review

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

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

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

6 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

8 third-party services load with your homepage (Shopify, Osano CMP and Google Maps and others), adding 3.1 MB and 931 ms of main-thread time.

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

About 142 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

Shopify costs a phone 361 ms of main-thread work and 2.2 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.

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

Google Maps costs a phone 184 ms of main-thread work and 406 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.

10 long tasks block the main thread while loading, the longest for 219 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).

25 KiB could be saved by minifying JavaScript.

17 KiB could be saved by minifying CSS.

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 image “Rolex”.

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

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

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

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

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

2 images have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 5.1 MB in 292 requests on a phone: images 2.5 MB (105), scripts 1.4 MB (79) and other files 673 KiB (63). Under 2 MB keeps phones on slow connections fast.

600x600_72.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

6 images (646 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.

1 image is downloaded at several times the size a phone draws it, for example Glashuette-Original-W13724201271-W13724010264.avif at 1,920 px wide, shown at 362 px. Resized copies would save about 87 KiB.

3 images further down the page (245 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

Alternative text of images should not be repeated as text: 78 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Your meta description is 312 characters; Google truncates after about 160, so the end of your pitch is cut.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 553 pages on cdpeacock.com and 5 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.

/customer_authentication/redirect has no <title>, so Google invents the link text in results.

/collections/all and /customer_authentication/redirect are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/collections/all, /customer_authentication/redirect, /policies/shipping-policy and /pages/swym-wishlist have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/all, /customer_authentication/redirect, /policies/shipping-policy, /pages/location, /pages/about-c-d-peacock and /pages/swym-wishlist and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://cdpeacock.com/cdn/shop/t/148/assets/component-rte.css?v=105863' because its MIME t…”.

Large scripts ship without source maps.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://cdpeacock.com/customer_authentication/redirect?locale=en&region_country=US.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

cdpeacock.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

cdpeacock.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Opening the homepage sets 5 cookies (measured from a US location before any click).

Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.