baque.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

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

• Real-user LCP: 4.8 s

  4.8 s

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

• Real-user FCP: 4.6 s

  4.6 s

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

• Real-user TTFB: 3.8 s

  3.8 s

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

• Tap response (INP) held steady for real visitors

  0%

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

• Largest content (LCP) held steady for real visitors

  0%

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

• Page weight: 21.6 MB

  21.6 MB

  Your homepage downloads 21.6 MB on a phone, 19.2 MB of it images (89%). Under 2 MB keeps phones on slow connections fast.

• 2 images over 500 KB

  2 images weigh 18.2 MB together. On a phone connection a single image that size takes seconds.

  Elements (2)

• 8 images in older formats

  8 images (19.1 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.

  Elements (5)

• 1 image below the first screen load straight away

  1 image further down the page (43 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  Elements (1)

• About 6.1 g of CO₂ per visit

  6.13 g

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

• 11 text elements with low contrast

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

  Elements (3)

• 5 tap targets too small

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

  Elements (3)

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

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

  Elements (3)

• No main landmark

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

  Elements (1)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

  Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 7 links without text

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

  Elements (3)

• 4 form fields without a label

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

  View source

• Headings skip levels

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

  View sourceElements (1)

• Title is long (68 characters)

  Your title is 68 characters, so Google will cut it off around 60: “Cafés Baqué: especialistas en hacer buen café. Líderes en hostelería”.

  View source

• No canonical URL

  No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

• Meta description is long (287 characters)

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

  View source

• No social preview image

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

  View source

• 79 internal links, 10 external

  The homepage links to 79 pages on baque.com and 10 external pages.

• No Organization structured data

  There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  View source

• No llms.txt

  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.

• 15 internal pages checked

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

• 3 JavaScript errors while loading

  3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v5.4.1/css/all.css?ver=7.1.3' from origin 'https://ww…”.

• No HSTS header

  No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

• No Content-Security-Policy

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

• No clickjacking protection

  Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

• No X-Content-Type-Options

  X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

• No security.txt

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

• No CAA record

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

• DNSSEC is off

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

• 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 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 450 words of copy

  The homepage carries about 450 words of visible text.

• SPF does not block other senders (?all)

  Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 include:servers.mcsv.net include:sarenet.es include:spf.dominioabsoluto.net include:_spf.google.com ?all”.

• Email authentication score: 85/100

  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.

• 3 trackers load before any consent

  3

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

• 14 cookies set on arrival

  14

  Opening the homepage sets 14 cookies, 1 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.

• 13 other companies contacted

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