fluentis.com website review

About 2.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.0 s faster on a phone.

The page goes through 1 redirect before it starts loading, costing about 5.6 s. Link and advertise the final URL directly.

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, iubenda and AddToAny and others), adding 441 KiB and 466 ms of main-thread time.

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

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

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 could be saved by minifying JavaScript.

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

Your largest element takes 23.4 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 17.5 MB in 397 requests on a phone: other files 10.4 MB (85), scripts 3.4 MB (91) and images 2.8 MB (195). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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.

11 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. (2 elements).

There are 2 <h1> headlines (“Fluentis ERP” and “Fluentis ERP”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 199 pages on fluentis.com and 14 external pages.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/it/prova-gratis-software-gestionale is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/it/prova-gratis-software-gestionale and /it/configura-cloud have no meta description, so Google writes the search snippet from whatever text it finds.

/it/software-gestionali took over 3 s to send its HTML from our server.

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

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

18 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

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.

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

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your longest form asks for 9 fields (3 required). Every extra field lowers completion.

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

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 and Google Tag Manager (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

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

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