Website review, no card needed

ambientegourmet.com logo

ambientegourmet.com website review

Visit site (opens in a new tab)Reviewed 19 October 202650 issues · 91 checks

This review found 50 issues worth fixing on ambientegourmet.com, 24 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. 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
4.5 s3.6 sMay 2Oct 174.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.2 s
May 9, 20264.2 s
May 16, 20264.3 s
May 23, 20264.3 s
May 30, 20263.9 s
Jun 6, 20263.7 s
Jun 13, 20263.7 s
Jun 20, 20263.7 s
Jun 27, 20264.0 s
Jul 4, 20264.1 s
Jul 11, 20264.1 s
Jul 18, 20264.1 s
Jul 25, 20264.2 s
Aug 1, 20264.3 s
Aug 8, 20264.3 s
Aug 15, 20264.4 s
Aug 22, 20264.2 s
Aug 29, 20264.1 s
Sep 5, 20264.0 s
Sep 12, 20263.9 s
Sep 19, 20264.0 s
Sep 26, 20264.0 s
Oct 3, 20264.1 s
Oct 10, 20264.3 s
Oct 17, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
357 ms281 msMay 2Oct 17348 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026292 ms
May 9, 2026301 ms
May 16, 2026306 ms
May 23, 2026305 ms
May 30, 2026293 ms
Jun 6, 2026290 ms
Jun 13, 2026292 ms
Jun 20, 2026297 ms
Jun 27, 2026318 ms
Jul 4, 2026322 ms
Jul 11, 2026324 ms
Jul 18, 2026325 ms
Jul 25, 2026326 ms
Aug 1, 2026330 ms
Aug 8, 2026328 ms
Aug 15, 2026328 ms
Aug 22, 2026331 ms
Aug 29, 2026334 ms
Sep 5, 2026336 ms
Sep 12, 2026343 ms
Sep 19, 2026332 ms
Sep 26, 2026330 ms
Oct 3, 2026331 ms
Oct 10, 2026327 ms
Oct 17, 2026348 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 ambientegourmet.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ambientegourmet.com at 0.7 s0.7 s
  2. ambientegourmet.com at 1.5 s1.5 s
  3. ambientegourmet.com at 2.2 s2.2 s
  4. ambientegourmet.com at 2.9 s2.9 s
  5. ambientegourmet.com at 3.7 s3.7 s
  6. ambientegourmet.com at 4.4 s4.4 s
  7. ambientegourmet.com at 5.2 s5.2 s
  8. ambientegourmet.com at 5.9 s5.9 s

Speed

13 to fix32
  • Reduce unused JavaScript

    6.0 s · 1.6 MB

    About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.0 s faster on a phone.

  • Improve image delivery

    2.0 s · 789 KiB

    5 images could be 789 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

  • Use efficient cache lifetimes

    1.8 s · 525 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 32

    32/100

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

  • Main-thread work: 6.6 s

    A phone's processor spends 6.6 s on main-thread work while loading, 4.1 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 (Google CDN, Google Tag Manager and vtexassets.com and others), adding 4.6 MB and 2.9 s of main-thread time.

  • Google CDN adds 829 ms

    829 ms

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

  • Google Tag Manager adds 786 ms

    786 ms

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

  • vtexassets.com adds 630 ms

    630 ms

    vtexassets.com costs a phone 630 ms of main-thread work and 1.8 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 CSS

    600 ms · 71 KiB

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

  • Legacy JavaScript

    300 ms · 76 KiB

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

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Duplicated JavaScript

    17 KiB

    17 KiB JavaScript is shipped twice across bundles.

  • Phones get a much slower page than desktops

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

  • 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 CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 48 ms

    48 ms

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

Core Web Vitals

12 to fix0
  • Fails Core Web Vitals for real visitors

    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-user CLS: 0.78

    0.78

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • First Contentful Paint: 9.0 s

    9.0 s

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

  • Largest Contentful Paint: 20.4 s

    20.4 s

    Your largest element takes 20.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Oferta en Ambiente Gourmet”.

  • Time to Interactive: 31.7 s

    31.7 s

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

  • Speed Index: 11.4 s

    11.4 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user LCP: 3.4 s

    3.4 s

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

  • Real-user INP: 317 ms

    317 ms

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • 9 images without width and height

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

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

    +14%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

1 checks passed
  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix70
  • Page weight: 5.9 MB in 209 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 209 requests on a phone: scripts 3.7 MB (83), images 1.0 MB (37) and other files 747 KiB (75). Under 2 MB keeps phones on slow connections fast.

  • About 1.7 g of CO₂ per visit

    1.69 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 8384
  • 1 button without a name

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

  • Hidden but focusable

    4 elements hidden from screen readers can still receive keyboard focus.

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (7 elements)

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

  • No main landmark

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

  • Page should contain a level-one heading (1 element)

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

  • 3 form fields without a label

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

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 13 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10086
  • Title is short (16 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

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

  • No X (Twitter) card tag

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

  • 10 internal links, 1 external

    The homepage links to 10 pages on ambientegourmet.com and 1 external page.

5 checks passed
  • Meta description: 124 characters

    Your meta description is 124 characters: “Encuentra todo para tu mesa, cocina, muebles y decoración. Compra online. Envíos a todo Colombia y múltiples medios de …”.

  • One H1 headline

    Your main headline reads: “Ambiente Gourmet”.

  • Canonical URL set

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

  • robots.txt in place

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

  • XML sitemap found

    Your XML sitemap is reachable at http://www.ambientegourmet.com/sitemap.xml.

AI search readiness

100
2 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: 6 of 6 facts

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

Other pages

3 to fix86
  • 1 linked page hidden from search

    https://www.ambientegourmet.com/5838 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a meta description

    https://www.ambientegourmet.com/ambiente-living and https://www.ambientegourmet.com/5838 use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://www.ambientegourmet.com/ambiente-living, https://www.ambientegourmet.com/ag and https://www.ambientegourmet.com/5838 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://www.ambientegourmet.com/bonos-de-regalo, https://www.ambientegourmet.com/ag, https://www.ambientegourmet.com/ag/mesa/vajillas-y-platos, https://www.ambientegourmet.com/ag/mesa/vasos-y-copas and https://www.ambientegourmet.com/lo-nuevo 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.

  • 1 page slow to respond

    https://www.ambientegourmet.com/lo-nuevo took over 3 s to send its HTML from our server.

  • 8 internal pages checked

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

5 checks passed
  • Linked pages load

    All 8 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 8 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://d2vjim51gqd2yo.cloudfront.net/images/product/ic_closed_dsk.png.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Unexpected token ')'”.

2 checks passed
  • Tap targets are thumb-sized

    32 of 34 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix43
  • No call to action on the first screen

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

  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 38 words

    The homepage has only about 38 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 mores (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.

  • 31 cookies set on arrival

    31

    Opening the homepage sets 31 cookies, 4 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 48 other companies contacted

    Loading the homepage contacts 48 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 ambientegourmet.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on ambientegourmet.com, including 25 speed issues, 3 SEO issues and 5 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