irondoor.com website review

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

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

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

8 third-party services load with your homepage (Shopify, LiveChat and synctrack.io and others), adding 1.2 MB and 405 ms of main-thread time.

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

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

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

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

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

LiveChat costs a phone 93 ms of main-thread work and 367 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 25 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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.

3 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

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

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

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

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

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

The layout shifts by 0.137 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 9.3 MB in 413 requests on a phone: images 6.6 MB (60), scripts 1.4 MB (160) and other files 948 KiB (150). Under 2 MB keeps phones on slow connections fast.

32 images are downloaded at several times the size a phone draws them, for example Liteair-43-2.jpg at 1,200 px wide, shown at 168 px. Resized copies would save about 3.7 MB.

small-slide-001.jpg 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).

1 image (389 KiB) is 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.

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

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

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

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

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

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

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

Structured data found (Organization and WebSite) but with 3 problems, for example “Organization: sameAs is not an absolute URL ("#")”.

Your <h1> is empty.

The homepage links to 168 pages on irondoor.com and 2 external pages.

There is no https://irondoor.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://irondoor.com/collections/double-exterior has no meta description, so Google writes the search snippet from whatever text it finds.

https://irondoor.com/collections/in-stock-doors, https://irondoor.com/collections/all, https://irondoor.com/collections/exterior-doors, https://irondoor.com/collections/interior-french-doors, https://irondoor.com/collections/transoms-sidelights and https://irondoor.com/collections/double-exterior have no <h1> headline, so visitors and search engines get no clear main topic.

https://irondoor.com/collections/all, https://irondoor.com/collections/exterior-doors and https://irondoor.com/collections/interior-french-doors took over 3 s to send their HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load script”.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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