currentbody.it website review

Signyfyd costs a phone 2.4 s of main-thread work and 476 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 12.6 s on main-thread work while loading, 8.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

8 third-party services load with your homepage (Signyfyd, Google Tag Manager and Klaviyo and others), adding 2.1 MB and 4.7 s of main-thread time.

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

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

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

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

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

Klaviyo costs a phone 376 ms of main-thread work and 326 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.

returngo.ai costs a phone 337 ms of main-thread work and 218 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.

Facebook costs a phone 293 ms of main-thread work and 216 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.

12 images could be 106 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

7 KiB could be saved by minifying JavaScript.

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.

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

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

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

Your largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “La prima maschera LED totalmente personalizzabile”.

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

Your homepage downloads 7.3 MB in 299 requests on a phone: media 3.0 MB (8), scripts 2.2 MB (117) and other files 756 KiB (108). Under 2 MB keeps phones on slow connections fast.

4 images (164 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 (27 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.08 g of CO₂e: 249.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

The homepage links to 155 pages on currentbody.it and 11 external pages.

/products/currentbody-skin-complete-led-kit, /collections/led and /collections/radio-frequency are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=85087016&tm=gtm002&Ver=2&mid=c127f630-69bd-4017-9cd9-3ab7c91a2ac0&bo=1&sid=0f4daaa0d8f111f19fa787b2ea284849&vid=0f4dd080d8f111f19dfb6be635444ae3&vids=1&msclkid=N&pi=91.

6 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

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

1 link go through two or more redirects, for example https://www.currentbody.it/customer_authentication/redirect?locale=it&region_country=IT.

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.

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

currentbody.it 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.

currentbody.it 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.

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 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 21 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 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.