purdyandfigg.com website review

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

The page goes through 1 redirect before it starts loading, costing about 1.2 s. Link and advertise the final URL directly.

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

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

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

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

12 images could be 1,002 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

Google Tag Manager costs a phone 874 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.

Klaviyo costs a phone 129 ms of main-thread work and 416 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.

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 27.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

Scripts block taps and scrolling for 488 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 195 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.4 MB in 594 requests on a phone: images 4.2 MB (134), scripts 2.9 MB (141) and other files 1.4 MB (281). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (140 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

58 images have no alt text, which hurts accessibility and image search.

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

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

Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

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.

3 links have no real href, so search engines can't follow them.

The homepage links to 135 pages on purdyandfigg.com and 11 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.

https://purdyandfigg.com/pages/memberoffer-summer-collection, https://purdyandfigg.com/pages/memberoffer-autumn-collection and https://purdyandfigg.com/products/floor-clean-starter-kit are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://purdyandfigg.com/pages/subscription-flow all use the title “Purdy & Figg | Who said cleaning had to be a chore”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://purdyandfigg.com/pages/memberoffer-summer-collection, https://purdyandfigg.com/pages/about-us, https://purdyandfigg.com/pages/subscription-flow, https://purdyandfigg.com/collections, https://purdyandfigg.com/pages/memberoffer-autumn-collection and https://purdyandfigg.com/products/floor-clean-starter-kit and 5 others use the same meta description. A description written for each page earns more clicks.

https://purdyandfigg.com/pages/memberoffer-summer-collection, https://purdyandfigg.com/blogs/natural-tips-and-tricks, https://purdyandfigg.com/pages/about-us, https://purdyandfigg.com/pages/subscription-flow, https://purdyandfigg.com/collections and https://purdyandfigg.com/pages/memberoffer-autumn-collection and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

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

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

8 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

The homepage carries about 565 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

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

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