sculpd.eu website review

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

About 372 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

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

8 third-party services load with your homepage (sculpd.com, Shopify and cdn-cookieyes.com and others), adding 3.5 MB and 810 ms of main-thread time.

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

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

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

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

13 images could be 420 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

Shopify costs a phone 245 ms of main-thread work and 649 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 2.4 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

1 long task block the main thread while loading, the longest for 77 ms. During a long task the page ignores taps.

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

37 KiB JavaScript is shipped twice across bundles.

19 KiB could be saved by minifying JavaScript.

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

8 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.

Your largest element takes 19.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “2026 Black Friday Homepage Hero Banner”.

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

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

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

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

Your homepage downloads 4.2 MB in 381 requests on a phone: scripts 1.3 MB (129), other files 1.2 MB (164) and images 1.0 MB (44). Under 2 MB keeps phones on slow connections fast.

Photo_pouring_Playbook.webp weighs 495 KiB. On a phone connection a single image that size takes seconds.

6 images (813 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.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Structured data found (Brand, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://sculpd.com)”.

The homepage links to 146 pages on sculpd.eu and 19 external pages.

https://sculpd.eu/collections/all-pottery-kits and https://sculpd.eu/collections/candle-making-kits have no meta description, so Google writes the search snippet from whatever text it finds.

https://sculpd.eu/products/sculpd and https://sculpd.eu/products/pottery-date-night-bundle use the same meta description. A description written for each page earns more clicks.

https://sculpd.eu/products/sculpd, https://sculpd.eu/products/pottery-date-night-bundle and https://sculpd.eu/products/scented-candle-making-pottery-kit have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were 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”).

Your longest form asks for 11 fields (6 required). Every extra field lowers completion.

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

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

Opening the homepage sets 40 cookies, 7 of them by other companies (measured from a US location before any click).

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