smolproducts.com website review

12 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.0 s faster on a phone.

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

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

7 third-party services load with your homepage (Google Tag Manager, Convert Insights and termly.io and others), adding 3.1 MB and 442 ms of main-thread time.

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

Google Tag Manager costs a phone 237 ms of main-thread work and 396 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.

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

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

Vimeo costs a phone 0 ms of main-thread work and 2.1 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.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “a smiling woman stirring a pot over a hob while holding a g…”.

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

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

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

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

Your homepage downloads 7.1 MB in 88 requests on a phone: images 3.3 MB (26), media 2.1 MB (1) and scripts 1.2 MB (34). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.2 MB together. On a phone connection a single image that size takes seconds.

4 images (2.5 MB) 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.

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

4 images are downloaded at several times the size a phone draws them, for example ahlmtweQX7-eWbKF_MP_PLPhero_joy_touch.jpg at 1,200 px wide, shown at 390 px. Resized copies would save about 424 KiB.

1 image further down the page (362 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 2.02 g of CO₂e: 242.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

30 tap targets are too small or too close together to hit reliably with a finger.

2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

The homepage links to 26 pages on smolproducts.com and 14 external pages.

A phone browser shows 1,398 words, but the HTML your server sends has only 313. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

Your Organization JSON-LD is missing url, logo, 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.

There is no https://smol.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://smol.com/uk/mission, https://smol.com/uk/products, https://smol.com/uk/refer-a-friend and https://smol.com/uk/policies-and-commitments have no <h1> headline, so visitors and search engines get no clear main topic.

https://smol.com/uk/policies-and-commitments has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

There is no form on the homepage, so every lead has to click through to another page first.

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 1,398 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager and Meta Pixel (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie (measured from a US location before any click).

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.