penningtons.com website review

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

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

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

8 third-party services load with your homepage (hcaptcha.com, Google Tag Manager and Clarity and others), adding 3.6 MB and 1.8 s of main-thread time.

About 1,016 KiB of JavaScript is downloaded but never used on this page.

hcaptcha.com costs a phone 893 ms of main-thread work and 1.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.

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

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

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

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

11 images could be 226 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

About 96 KiB of CSS is downloaded but never applied on this page.

11 KiB JavaScript is shipped twice across bundles.

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 32.0 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 6.0 MB in 521 requests on a phone: scripts 3.2 MB (240), other files 1.1 MB (183) and images 925 KiB (35). Under 2 MB keeps phones on slow connections fast.

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

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

1 form field has 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.

Your title is 66 characters, so Google will cut it off around 60: “Plus Size Clothing Canada – Stylish & Trendy Fashion | Penningtons”.

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

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

The homepage links to 503 pages on penningtons.com and 9 external pages.

There is no https://www.penningtons.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.

https://www.penningtons.com/pages/orders-delivery-pickup, https://www.penningtons.com/pages/vipenn-rewards, https://www.penningtons.com/pages/legal and https://www.penningtons.com/collections/promotions-promo-3 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.penningtons.com/pages/vipenn-rewards, https://www.penningtons.com/pages/legal, https://www.penningtons.com/collections/promotions-promo-3 and https://www.penningtons.com/collections/new-clothing-bottoms have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 402 ()”.

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 carries about 398 words of visible text.

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