sculpd.fr website review

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

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

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

8 third-party services load with your homepage (sculpd.com, gettixel.com and Shopify and others), adding 4.2 MB and 1.4 s of main-thread time.

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

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

sculpd.com costs a phone 434 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 665 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

About 101 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.

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

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

gettixel.com costs a phone 325 ms of main-thread work and 7 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.

24 KiB could be saved by minifying JavaScript.

Attentive costs a phone 153 ms of main-thread work and 489 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.

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

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

37 KiB JavaScript is shipped twice across bundles.

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

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

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

Your largest element takes 12.6 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”.

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

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

The layout shifts by 0.317 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

5 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 5.6 MB in 438 requests on a phone: scripts 2.0 MB (149), images 1.6 MB (55) and other files 1.2 MB (178). 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.59 g of CO₂e: 191.3 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 2 problems, for example “Organization: url points at a different host (https://sculpd.com)”.

The homepage links to 143 pages on sculpd.fr and 21 external pages.

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

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

/collections/all-kits and /products/sculpd 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.

3 errors were logged to the browser console while the page loaded, for example “Failed to fetch”.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

sculpd.fr has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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.

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

sculpd.fr has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

sculpd.fr has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

sculpd.fr has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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 36 cookies, 6 of them by other companies (measured from a US location before any click).

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