ironcladpan.com website review

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

24 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

8 third-party services load with your homepage (posthog.com, Facebook and Google Tag Manager and others), adding 1.6 MB and 563 ms of main-thread time.

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

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

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

About 286 KiB of JavaScript is downloaded but never used on this page.

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

9 KiB could be saved by minifying JavaScript.

4 long tasks block the main thread while loading, the longest for 135 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 39 KiB JavaScript that modern phones do not need.

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

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 16.3 MB in 416 requests on a phone: media 10.5 MB (2), images 3.2 MB (128) and scripts 1.1 MB (82). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example ac.svg at 16,250 px wide, shown at 22 px. Resized copies would save about 121 KiB.

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

Some list items are not inside a list.

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

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

All page content should be contained by landmarks: 17 elements on the page fail this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Headings skip levels (h3 → 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.

Your title is 68 characters, so Google will cut it off around 60: “Cast Iron Cookware & Cooking Sets for Sale Online | The Ironclad Co.”.

The homepage links to 114 pages on ironcladpan.com and 16 external pages.

https://ironcladpan.com/products/gift-card declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

https://ironcladpan.com/collections/ironclub-only-access is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://ironcladpan.com/products/gift-card all use the title “Cast Iron Cookware & Cooking Sets for Sale Online | The Ironclad Co.”. Search engines can't tell which page to show for a search, so each competes with the others.

https://ironcladpan.com/policies/shipping-policy, https://ironcladpan.com/collections/all-presses, https://ironcladpan.com/collections/limited-edition-collaborations, https://ironcladpan.com/collections/ironclub-only-access and https://ironcladpan.com/blogs/heirloom-recipes have no meta description, so Google writes the search snippet from whatever text it finds.

https://ironcladpan.com/products/gift-card and https://ironcladpan.com/collections/ironclub-only-access have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 11 fields (6 required). Every extra field lowers completion.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 521 words of visible text.

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