Website review, no card needed

santateresagourmet.com logo

santateresagourmet.com website review

Visit site (opens in a new tab)Reviewed 19 November 202625 issues · 69 checks

This review found 25 issues worth fixing on santateresagourmet.com, 10 of them high impact, across 69 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.7 s1.4 sMay 30Nov 141.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.6 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.5 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Nov 14, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
202 ms144 msMay 30Nov 14195 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026151 ms
Jun 6, 2026151 ms
Jun 13, 2026158 ms
Jun 20, 2026161 ms
Jun 27, 2026163 ms
Jul 4, 2026173 ms
Jul 11, 2026165 ms
Jul 18, 2026161 ms
Jul 25, 2026160 ms
Aug 1, 2026159 ms
Aug 8, 2026167 ms
Aug 15, 2026165 ms
Aug 22, 2026159 ms
Aug 29, 2026154 ms
Sep 5, 2026152 ms
Sep 12, 2026163 ms
Sep 19, 2026162 ms
Sep 26, 2026161 ms
Oct 3, 2026158 ms
Oct 10, 2026158 ms
Oct 17, 2026169 ms
Oct 24, 2026183 ms
Oct 31, 2026191 ms
Nov 7, 2026195 ms
Nov 14, 2026195 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of santateresagourmet.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. santateresagourmet.com at 1.3 s1.3 s
  2. santateresagourmet.com at 2.5 s2.5 s
  3. santateresagourmet.com at 3.8 s3.8 s
  4. santateresagourmet.com at 5.1 s5.1 s
  5. santateresagourmet.com at 6.3 s6.3 s
  6. santateresagourmet.com at 7.6 s7.6 s
  7. santateresagourmet.com at 8.8 s8.8 s
  8. santateresagourmet.com at 10.1 s10.1 s

Speed

9 to fix60
  • Improve image delivery

    1.3 s · 2.2 MB

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

  • Render-blocking requests

    1.6 s

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

  • Main-thread work: 6.8 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Clarity and Google Tag Manager and others), adding 3.4 MB and 1.6 s of main-thread time.

  • Mobile performance score: 60

    60/100

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

  • Shopify adds 662 ms

    662 ms

    Shopify costs a phone 662 ms of main-thread work and 2.7 MB 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.

  • Reduce unused JavaScript

    300 ms · 562 KiB

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

  • Google Tag Manager adds 256 ms

    256 ms

    Google Tag Manager costs a phone 256 ms of main-thread work and 362 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.

  • Clarity adds 261 ms

    261 ms

    Clarity costs a phone 261 ms of main-thread work and 30 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.

  • Use efficient cache lifetimes

    100 ms · 245 KiB

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

  • 5 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 36 KiB

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

  • Legacy JavaScript

    150 ms · 17 KiB

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

  • Duplicated JavaScript

    41 KiB

    41 KiB JavaScript is shipped twice across bundles.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 78 ms

    78 ms

    Your server sent the HTML in 78 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 9.7 s

    9.7 s

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

  • Time to Interactive: 28.8 s

    28.8 s

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

  • Speed Index: 11.5 s

    11.5 s

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

  • Tap response (INP) got 29% slower for real visitors

    +29%

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 8 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 183 ms

    183 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 517 ms

    517 ms

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

  • Total Blocking Time: 114 ms

    114 ms

    Scripts block the page for only 114 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix0
  • Page weight: 6.3 MB in 503 requests

    6.3 MB

    Your homepage downloads 6.3 MB in 503 requests on a phone: images 2.8 MB (41), scripts 1.8 MB (129) and other files 1.4 MB (294). Under 2 MB keeps phones on slow connections fast.

  • About 1.8 g of CO₂ per visit

    1.79 g

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

Accessibility

4 to fix85
  • 2 images without alt text

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

  • 26 text elements with low contrast

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

  • 4 tap targets too small

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

  • Links do not have a discernible name

    Links do not have a discernible name (2 elements).

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

SEO

1 to fixGoogle 9295
  • 2 H1 headlines

    There are 2 <h1> headlines (“Santa Teresa Gourmet - Tienda Online de Alimentac…” and “Santa Manera de vivir”). One clear main headline is easier for people and search engines.

  • 84 internal links, 17 external

    The homepage links to 84 pages on santateresagourmet.com and 17 external pages.

7 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Compra online las Auténticas Yemas de Santa Teresa, Huevo Hilado, Membrillo, Gazpachos, Platos Preparados y más. Envío …”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Tienda Online de Alimentación Gourmet – Santa Teresa Gourmet”.

  • Canonical URL set

    The canonical URL is https://www.santateresagourmet.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.santateresagourmet.com/sitemap.xml.

AI search readiness

100
3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • llms.txt published

    The site publishes https://www.santateresagourmet.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.santateresagourmet.com/collections/come-bien-sin-cocinar-1 has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    4 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 4 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 7 console errors

    7 errors were logged to the browser console during Google's test (“%c14:36:41.360 PST %cPixel SDK %cERROR %cError waiting for Shopify color: gray color: magenta; font…”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix60
  • No calls to action

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 575 words of copy

    The homepage carries about 575 words of visible text.

3 checks passed
  • 17 short forms

    17 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at santateresagourmet.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 19 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Pagefly Ai Page Builder · Microsoft Clarity · Sami Wholesale · Tagfly Tag Manager · Helium Customer Fields · Musbu Wa Chat · Globo Product Options · Gdpr Backpack · Https Appointly Com · Automatic Discounts Upsells · Qikify Timer Announcement Bar · Freegifts · chimpstatic.com · b-cdn.net · cloudfront.net · pop-convert.com · sealsubscriptions.com · bogos.io

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on santateresagourmet.com, including 15 speed issues, 1 SEO issue and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25