smithey.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 3.3 s faster on a phone.

10 images could be 826 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and rebuyengine.com and others), adding 3.3 MB and 1.4 s of main-thread time.

Google Tag Manager costs a phone 543 ms of main-thread work and 749 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 90 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

alia-prod.com costs a phone 301 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.

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

rebuyengine.com costs a phone 158 ms of main-thread work and 332 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.

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

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

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

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

8 KiB could be saved by minifying JavaScript.

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

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

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

The first text or image appears after 3.0 s on a phone. Good is under 1.8 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-11-07, real Chrome visitors' tap response (inp) went from 111 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 11.5 MB in 366 requests on a phone: images 3.7 MB (34), media 3.4 MB (2) and scripts 2.6 MB (104). Under 2 MB keeps phones on slow connections fast.

09162019_-_Smithey_Ironware_Shop_Photoshoot_-_LIFESTYLE4541. weighs 577 KiB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example 09162019_-_Smithey_Ironware_Shop_Photoshoot_-_LIFESTYLE4541. at 3,500 px wide, shown at 370 px. Resized copies would save about 519 KiB.

5 images (250 KiB) are 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 3.27 g of CO₂e: 391.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 buttons have no accessible name, so screen readers announce just “button”.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

Links must have discernible text: 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.

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

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

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

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 158 pages on smithey.com and 13 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://smithey.com/collections/sets, https://smithey.com/pages/seasoning, https://smithey.com/pages/care, https://smithey.com/a/faq, https://smithey.com/pages/our-story and https://smithey.com/blogs/journal and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://smithey.com/pages/wholesale-gifting, whose canonical is https://smithey.com/pages/corporate-gifting. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://smithey.com/pages/message-from-founder has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

Large scripts ship without source maps.

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

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

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