wedfettiuk.com website review

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

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

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

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

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

6 third-party services load with your homepage (Shopify, uploadly-cdn.com and cloudfront.net and others), adding 1.5 MB and 785 ms of main-thread time.

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

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

uploadly-cdn.com costs a phone 299 ms of main-thread work and 112 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 long tasks block the main thread while loading, the longest for 163 ms. During a long task the page ignores taps.

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

34 KiB could be saved by minifying JavaScript.

About 23 KiB of CSS is downloaded but never applied on this page.

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

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 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A couple being showered with Biodegradable paper Confetti”.

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

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

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

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

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

Your homepage downloads 5.9 MB in 323 requests on a phone: images 3.1 MB (33), scripts 1.2 MB (124) and other files 1.0 MB (113). Under 2 MB keeps phones on slow connections fast.

IMG-20261025-WA0007.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).

7 images are downloaded at several times the size a phone draws them, for example IMG-20261025-WA0007.jpg at 800 px wide, shown at 220 px. Resized copies would save about 337 KiB.

5 images further down the page (210 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (93 KiB) is 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 1.67 g of CO₂e: 200.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

4 frames have no title, so screen-reader users cannot tell what they contain.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 32 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.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

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

Your title is 84 characters, so Google will cut it off around 60: “Biodegradable paper & petal Confetti & wedding signage – WedFetti Confetti & Signage”.

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

The homepage links to 252 pages on wedfettiuk.com and 34 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.

Your homepage links to https://www.wedfettiuk.com/customer_authentication/redirect, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.wedfettiuk.com/en-us and / all use the title “Biodegradable paper & petal Confetti & wedding signage – WedFetti Con…”. Search engines can't tell which page to show for a search, so each competes with the others.

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

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /, whose canonical is https://www.wedfettiuk.com/en-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.wedfettiuk.com/en-us/collections/all, https://www.wedfettiuk.com/en-us/collections/petal-confetti-wedding, /, https://www.wedfettiuk.com/en-us/pages/petal-confetti-collections, https://www.wedfettiuk.com/en-us/collections/snow-petals%C2%AE and https://www.wedfettiuk.com/en-us/collections/flutterfly-petals and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://www.wedfettiuk.com/en-us.

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

Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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 2,992 words of visible text.

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