jlmatthews.com website review

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

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

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

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

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

8 third-party services load with your homepage (growave.io, Klaviyo and userway.org and others), adding 1.1 MB and 662 ms of main-thread time.

growave.io costs a phone 313 ms of main-thread work and 275 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 long tasks block the main thread while loading, the longest for 305 ms. During a long task the page ignores taps.

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

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

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

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

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

2 KiB could be saved by minifying JavaScript.

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

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.

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

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

1 image 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 109 ms to 100 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.1 MB in 367 requests on a phone: images 1.6 MB (45), other files 1.1 MB (160) and scripts 1,003 KiB (111). Under 2 MB keeps phones on slow connections fast.

6 images are downloaded at several times the size a phone draws them, for example Copy_of_JL_Matthews_Collections_Square_Image_-_Lineman_9454b at 4,000 px wide, shown at 175 px. Resized copies would save about 926 KiB.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (5 elements).

Your title is 69 characters, so Google will cut it off around 60: “Lineman Tools, Arborist and Ironworker Gear - J.L. Matthews Co., Inc.”.

The homepage links to 266 pages on jlmatthews.com and 12 external pages.

https://jlmatthews.com/collections/all and https://jlmatthews.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

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

The homepage carries about 709 words of visible text.

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