curafyt.com website review

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

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

8 third-party services load with your homepage (alia-prod.com, loloyal.com and Trust Pilot and others), adding 2.7 MB and 1.5 s of main-thread time.

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

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

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

alia-prod.com costs a phone 542 ms of main-thread work and 1.1 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.

1 image could be 20 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

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

loloyal.com costs a phone 214 ms of main-thread work and 392 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.

Trust Pilot costs a phone 214 ms of main-thread work and 310 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.

cloudfront.net costs a phone 110 ms of main-thread work and 387 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.

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

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

Polyfills for old browsers add 47 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.

2 KiB JavaScript is shipped twice across bundles.

2 KiB could be saved by minifying CSS.

2 KiB could be saved by minifying JavaScript.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Alizée Froment smiling with her arm around her buckskin hor…”.

Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 203 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 131 ms to 197 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 2.2 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.

Real visitors wait 906 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Your homepage downloads 5.4 MB in 458 requests on a phone: scripts 1.9 MB (102), other files 1.4 MB (280) and images 1.1 MB (32). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.53 g of CO₂e: 183.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

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

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

The homepage links to 333 pages on curafyt.com and 32 external pages.

/customer_authentication/redirect has no <title>, so Google invents the link text in results.

/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

/nl took over 3 s to send its HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://d1npnstlfekkfz.cloudfront.net/zipify-oneclickupsell-single.bfbdb0cfc9f155eb.css' f…”.

1 link to other sites is dead, for example https://www.linkedin.com/curafyt (404).

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

4 links go through two or more redirects, for example https://curafyt.com/customer_authentication/redirect?locale=en&region_country=LU.

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.

curafyt.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

curafyt.com 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.

curafyt.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

DMARC is set to p=none, so mail pretending to be curafyt.com is still delivered. Reports are on, so moving to quarantine is the next step.

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