shopstickley.com website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.8 s faster on a phone.

The page goes through 2 redirects before it starts loading, costing about 9.3 s. Link and advertise the final URL directly.

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

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

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

Your mobile performance score is 32. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 3.8 MB and 2.2 s of main-thread time.

About 225 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

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

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

Shopify costs a phone 449 ms of main-thread work and 1.4 MB 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.

28 KiB could be saved by minifying JavaScript.

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

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

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

azurefd.net costs a phone 80 ms of main-thread work and 334 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.

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

The HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

6 KiB could be saved by minifying CSS.

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 39.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Stay connected with Stickley to be entered for a chance to …”.

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

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

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

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

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

Your homepage downloads 32.2 MB in 775 requests on a phone: media 23.8 MB (2), scripts 4.1 MB (321) and other files 1.7 MB (333). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (54 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 9.13 g of CO₂e: 1095.0 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: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

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

There are 2 <h1> headlines (“” and “A Gus original has new life”). One clear main headline is easier for people and search engines.

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

The homepage links to 298 pages on shopstickley.com and 16 external pages.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://www.stickley.com/pages/about-us, https://www.stickley.com/collections/made-in-america, https://www.stickley.com/collections/catalogs, https://www.stickley.com/pages/delivery-shipping, https://www.stickley.com/collections/in-stock-living-room and https://www.stickley.com/collections/in-stock-dining-room and 6 others use the same meta description. A description written for each page earns more clicks.

https://www.stickley.com/collections/made-in-america, https://www.stickley.com/products/2026-ce-lasalle-rocker and https://www.stickley.com/products/leopolds-chair-and-ottoman-set have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://d3k81ch9hvuctc.cloudfront.net/company/TnWM8C/images/3667a918-968a-4e07-9644-c5d508425d05.jpeg.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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