vimafoods.com website review

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

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

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

Your mobile performance score is 61 (desktop: 93). Pages that score under 90 lose visitors before the first paint.

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

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

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 182 KiB and 123 ms of main-thread time.

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

Desktop scores 93 but mobile only 61. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “banner-pescados”.

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 140 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.8 MB in 125 requests on a phone: images 2.5 MB (13), scripts 566 KiB (39) and other files 346 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

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

[role="img"] and [role="image"] elements must have alternative text: 7 elements on the page fail this check, rated serious by axe-core.

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Headings skip levels (h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

Your page has no <title>, so Google has to invent the blue link in search results.

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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.

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

The homepage links to 175 pages on vimafoods.com and 10 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.

/quienes-somos, /productos, /pescados, /mariscos, /papas and /frutas and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/quienes-somos, /pescados, /mariscos, /papas, /frutas and /vegetales and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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