aboca.it website review

22 images could be 5.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

63 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, digitaloceanspaces.com and iubenda and others), adding 1.5 MB and 1.3 s of main-thread time.

Google Tag Manager costs a phone 745 ms of main-thread work and 700 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 94 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

digitaloceanspaces.com costs a phone 424 ms of main-thread work and 650 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.

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

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

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

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.

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

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

Your largest element takes 46.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

Your homepage downloads 13.5 MB in 94 requests on a phone: images 11.5 MB (32), scripts 1.8 MB (34) and stylesheets 111 KiB (9). Under 2 MB keeps phones on slow connections fast.

4 images weigh 4.4 MB together. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example farfalla-low.jpeg at 8,368 px wide, shown at 390 px. Resized copies would save about 3.8 MB.

25 images (6.2 MB) 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.

farfalla-low.jpeg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

19 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

No XML sitemap at https://www.aboca.com/sitemap_index.xml, so Google discovers your pages only by following links.

The homepage links to 160 pages on aboca.it and 40 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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/trova-prodotto and /it/esigenze-di-salute have no meta description, so Google writes the search snippet from whatever text it finds.

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

/it/trova-prodotto took over 3 s to send its HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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

aboca.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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 875 words of visible text.

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

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 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 5 cookies (measured from a US location before any click).

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