saltenias.com website review

9 images could be 437 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.

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

About 27 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

2 third-party services load with your homepage (Shopify and Instagram), adding 36 KiB and 2 ms of main-thread time.

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.

Your largest element takes 9.2 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 9.3 s. Good is under 3.8 s.

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

3 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 2.5 MB in 135 requests on a phone: images 1.3 MB (18), other files 782 KiB (96) and scripts 183 KiB (13). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example saltena-recipe-dark_1920x1080.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 138 KiB.

5 images further down the page (341 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images (299 KiB) 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 0.70 g of CO₂e: 83.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Your title is only 28 characters: “Bolivian Saltenas – saltenas”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“<img src="//saltenias.com/cdn/shop/files/saltenas…”, “Recipes, news and more about Bolivian Salteñas” and “Offer of the Week”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 25 pages on saltenias.com and 4 external pages.

Your homepage links to https://saltenias.com/pages/products, which answers with an error. Visitors hit a dead end and search engines drop it.

https://saltenias.com/collections/all, https://saltenias.com/blogs/news and https://saltenias.com/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

https://saltenias.com/pages/about, https://saltenias.com/products/bolivian-saltena-traditional and https://saltenias.com/products/saltena-special use the same meta description. A description written for each page earns more clicks.

https://saltenias.com/pages/about has no <h1> headline, so visitors and search engines get no clear main topic.

https://saltenias.com/collections/all, https://saltenias.com/blogs/news and https://saltenias.com/pages/contact 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.

We fetched 9 pages linked from your homepage and read each the way a search engine does.

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

Social proof on the homepage: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Opening the homepage sets 5 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.