ambar.com website review

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

About 287 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

22 KiB could be saved by minifying CSS.

The page has 2,058 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

5 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and New Relic and others), adding 262 KiB and 290 ms of main-thread time.

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

17 KiB could be saved by minifying JavaScript.

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

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.

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

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

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

Your largest element takes 30.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Usamos cookies para mejorar su experiencia de navegación, m…”.

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

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

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

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

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

7 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-10, real Chrome visitors' largest content (lcp) went from 4.5 s to 4.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 22.6 MB in 116 requests on a phone: media 13.9 MB (2), images 7.2 MB (40) and scripts 619 KiB (33). Under 2 MB keeps phones on slow connections fast.

Ambar-IPA-bot-33cl.png weighs 16.8 MB. On a phone connection a single image that size takes seconds.

12 images (19.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.

2 images are downloaded at several times the size a phone draws them, for example Horizontal-Negro-scaled.png at 2,560 px wide, shown at 130 px. Resized copies would save about 130 KiB.

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

1 element has a tabindex above 0, which scrambles the keyboard order.

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

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

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

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

Your meta description is 220 characters; Google truncates after about 160, so the end of your pitch is cut.

2 links have no real href, so search engines can't follow them.

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

The homepage links to 121 pages on ambar.com and 11 external pages.

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.

/cervezas/especial, /cervezas/export, /cervezas/1900sinfiltrar, /cervezas/morena and /cervezas/radler took over 3 s to send their HTML from our server.

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

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

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

ambar.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

ambar.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 1,017 words of visible text.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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