smiffys.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, loox.io and Shopify and others), adding 1.9 MB and 827 ms of main-thread time.

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

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

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

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

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

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

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

78 KiB could be saved by minifying JavaScript.

8 long tasks block the main thread while loading, the longest for 162 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

Your homepage downloads 5.9 MB in 370 requests on a phone: images 2.7 MB (60), scripts 2.0 MB (160) and other files 864 KiB (124). Under 2 MB keeps phones on slow connections fast.

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

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

3 elements use ARIA attributes their role does not allow, which confuses screen readers.

28 elements hidden from screen readers can still receive keyboard focus.

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

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 976 pages on smiffys.com and 5 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.smiffys.com/pages/black-friday-offers, https://www.smiffys.com/collections/adult-fancy-dress, https://www.smiffys.com/collections/mens-fancy-dress, https://www.smiffys.com/collections/womens-fancy-dress, https://www.smiffys.com/collections/plus-size-fancy-dress and https://www.smiffys.com/collections/sexy-costumes 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 200 found) and read each the way a search engine does.

6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

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

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

The page uses urgency cues (a countdown or limited-time wording).

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