thepolishedjar.com website review

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

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

Signyfyd costs a phone 1.0 s of main-thread work and 266 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Signyfyd, Clarity and tncapp.com and others), adding 5.6 MB and 2.0 s of main-thread time.

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

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

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

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

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

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

Clarity costs a phone 254 ms of main-thread work and 29 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.

rebuyengine.com costs a phone 132 ms of main-thread work and 698 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.

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

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

11 KiB could be saved by minifying JavaScript.

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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying CSS.

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

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

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

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

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

7 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' tap response (inp) went from 128 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 10.0 MB in 458 requests on a phone: scripts 3.9 MB (133), media 2.4 MB (1) and other files 1.4 MB (246). Under 2 MB keeps phones on slow connections fast.

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

7 elements hidden from screen readers can still receive keyboard focus.

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.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your title is 78 characters, so Google will cut it off around 60: “Soap Dispensers | Custom Bathroom & Kitchen Soap Dispensers – The Polished Jar”.

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

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected ',' or '}' after property value in JSON at position)”.

The homepage links to 259 pages on thepolishedjar.com and 7 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://thepolishedjar.com/collections/astor-holiday-collection/dispenser is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://thepolishedjar.com/collections/laundry-containers has no meta description, so Google writes the search snippet from whatever text it finds.

https://thepolishedjar.com/collections/astor-holiday-collection and https://thepolishedjar.com/collections/astor-holiday-collection/dispenser use the same meta description. A description written for each page earns more clicks.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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 559 words of visible text.

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