sardimar.com website review

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

YouTube costs a phone 6.1 s of main-thread work and 16.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

About 8.9 MB of JavaScript is downloaded but never used on this page.

8 third-party services load with your homepage (YouTube, Google CDN and Other Google APIs/SDKs and others), adding 17.6 MB and 7.0 s of main-thread time.

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

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

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

Google CDN costs a phone 315 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

Other Google APIs/SDKs costs a phone 174 ms of main-thread work and 452 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.

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

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

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

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

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

Your largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “1 / 1”.

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

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

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

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

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

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

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

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

Your homepage downloads 34.0 MB in 407 requests on a phone: scripts 15.8 MB (153), media 11.9 MB (2) and images 2.0 MB (28). Under 2 MB keeps phones on slow connections fast.

8 images are downloaded at several times the size a phone draws them, for example sombra-latas.png at 1,381 px wide, shown at 168 px. Resized copies would save about 716 KiB.

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

7 images (1.4 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.

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

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

1 button has no accessible name, so screen readers announce just “button”.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

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

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

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

Your title is only 8 characters: “Sardimar”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 43 pages on sardimar.com and 5 external pages.

There is no https://sardimar.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.

https://sardimar.com/sardi-y-sus-amigos, https://sardimar.com/contact, https://sardimar.com/receta/chalupas, https://sardimar.com/receta/arroz-primavera, https://sardimar.com/receta/pasta-fria-con-atun-y-pesto and https://sardimar.com/el-viaje-del-atun-desde-el-oceano-hasta-tu-plato have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://sardimar.com/contact, whose canonical is https://sardimar.com/contactenos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://sardimar.com/sobre-nosotros, https://sardimar.com/calidad, https://sardimar.com/portafolio, https://sardimar.com/lanzamientos, https://sardimar.com/recetas and https://sardimar.com/blog and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://sardimar.com/lanzamientos, https://sardimar.com/recetas, https://sardimar.com/contact and https://sardimar.com/campanas have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://sardimar.com/sobre-nosotros, https://sardimar.com/calidad, https://sardimar.com/portafolio, https://sardimar.com/lanzamientos, https://sardimar.com/recetas and https://sardimar.com/blog and 6 others took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://sardimar.com/wp-content/uploads/2024/11/elementor/thumbs/Logo-Sardi-qxqaqr5oaq2h9b3oy8xt5k76rwr17xsk5nm143cze0.webp.

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

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

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

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

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

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