vicens.com website review

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and logicommerce.cloud and others), adding 2.4 MB and 1.9 s of main-thread time.

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

Google CDN costs a phone 436 ms of main-thread work and 734 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.

logicommerce.cloud costs a phone 423 ms of main-thread work and 615 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.

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

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

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

Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

3 KiB could be saved by minifying JavaScript.

Your largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Diálogos, entre Perú y el Mediterráneo”.

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

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

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

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

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

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

Your homepage downloads 5.7 MB in 103 requests on a phone: images 2.9 MB (38), scripts 1.9 MB (37) and other files 363 KiB (13). Under 2 MB keeps phones on slow connections fast.

11 images (1.9 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.

turron-nocilla-mobile-esp-720-v01.jpg 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).

1 image is downloaded at several times the size a phone draws it, for example logo-vicens-filete-gran.png at 1,565 px wide, shown at 58 px. Resized copies would save about 137 KiB.

1 image further down the page (45 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.61 g of CO₂e: 192.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

46 buttons have no accessible name, so screen readers announce just “button”.

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

Links must have discernible text: 4 elements on the page fail this check, rated serious by axe-core.

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

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

Alternative text of images should not be repeated as text: 16 elements on the page fail this check, rated minor by axe-core.

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

3 links have no real href, so search engines can't follow them.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 354 pages on vicens.com and 3 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 https://www.vicens.com/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.

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

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

Before a visitor clicks anything, the page loads Google Tag Manager, Hotjar and Meta Pixel (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 19 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.