peasedoors.com website review

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 718 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.

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

8 third-party services load with your homepage (Google Tag Manager, negate.io and loox.io and others), adding 1.6 MB and 2.7 s of main-thread time.

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

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

negate.io costs a phone 651 ms of main-thread work and 40 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.

loox.io costs a phone 395 ms of main-thread work and 221 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.

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

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

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

narvar.com costs a phone 136 ms of main-thread work and 316 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.

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

23 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

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

Your homepage downloads 3.1 MB in 221 requests on a phone: scripts 1.5 MB (76), images 676 KiB (32) and other files 639 KiB (84). Under 2 MB keeps phones on slow connections fast.

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

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

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

Your title is only 27 characters: “Pease Doors: The Door Store”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 315 pages on peasedoors.com and 5 external pages.

https://peasedoors.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://peasedoors.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://peasedoors.com/customer_authentication/redirect and https://peasedoors.com/collections/patio-doors have no meta description, so Google writes the search snippet from whatever text it finds.

https://peasedoors.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17411389&Ver=2&mid=272c77d5-c23b-440e-a2af-b78520b21257&bo=1&sid=b6d88330d90011f1b6e225075fdb3aaa&vid=b6d8b270d90011f19cf11fdc0795193a&vids=1&msclkid=N&pi=918639831&lg.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

The homepage carries about 1,035 words of visible text.

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