jmpwood.com website review

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

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

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

About 202 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and Facebook and others), adding 847 KiB and 290 ms of main-thread time.

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

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

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

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

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.

Your largest element takes 9.2 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 9.9 s. Good is under 3.8 s.

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

2 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 3.1 MB in 322 requests on a phone: images 1.1 MB (78), other files 946 KiB (130) and scripts 861 KiB (103). Under 2 MB keeps phones on slow connections fast.

home-banner-steelx-3A-mobile.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).

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 434 pages on jmpwood.com and 3 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.jmpwood.com/collections/newel-posts, https://www.jmpwood.com/pin-top-newel-posts-menu and https://www.jmpwood.com/post-to-post-newel-posts-menu all use the title “Quality Wood Staircase Newel Posts - JMP Wood”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.jmpwood.com/collections/newels-main, https://www.jmpwood.com/collections/newel-post-best-sellers, https://www.jmpwood.com/collections/iron-newel-posts, https://www.jmpwood.com/collections/box-newel-caps, https://www.jmpwood.com/collections/baluster-sleeves and https://www.jmpwood.com/collections/newel-installation and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.jmpwood.com/collections/newel-posts, https://www.jmpwood.com/pin-top-newel-posts-menu and https://www.jmpwood.com/post-to-post-newel-posts-menu use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.jmpwood.com/pin-top-newel-posts-menu, whose canonical is https://www.jmpwood.com/collections/newel-posts. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.jmpwood.com/collections/free-gifts, https://www.jmpwood.com/collections/newels-main, https://www.jmpwood.com/collections/newel-posts, https://www.jmpwood.com/collections/newel-post-best-sellers, https://www.jmpwood.com/collections/box-newels and https://www.jmpwood.com/collections/modern-wood-newel-posts and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Large scripts ship without source maps.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

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

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

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