# BeaverCheck Audit Report — https://www.amadohastaelextremo.es

**Date:** November 1, 2026  
**URL:** https://www.amadohastaelextremo.es  
**Overall Grade:** B (83/100)  
**Report:** https://beavercheck.com/results/93e5394c-ce60-4f21-bdb2-8baf801614f2

## Top Findings

1. **[CRITICAL]** HSTS header is missing — Security > Security Headers
2. **[CRITICAL]** 1 image(s) missing alt attribute — Accessibility > Alt Text Quality
3. **[CRITICAL]** 2 control(s) without accessible label — Accessibility > Form Accessibility
4. **[WARNING]** 18 inline style attribute(s) detected — Security > CSP Inline-Style Readiness
5. **[WARNING]** 2 link(s) open in a new tab without rel=noopener — Security > Cross-Origin Tab Safety

---

## Lighthouse Scores

| Category | Score |
|----------|-------|
| Performance | 74 |
| Accessibility | 94 |
| Best Practices | 100 |
| SEO | 100 |

---

## Security

### Security Headers (F — 35/100)

*4 of 10 headers properly configured*

- **[CRITICAL]** HSTS header is missing — Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.
- **[WARNING]** X-Content-Type-Options header is missing — This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'.
- **[PASS]** X-Frame-Options is properly configured
- **[WARNING]** Referrer-Policy header is missing — Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
- **[WARNING]** Permissions-Policy header is missing — Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
- **[PASS]** Content-Security-Policy is present
- **[WARNING]** Cross-Origin-Opener-Policy header is missing — COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
- **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
- **[PASS]** X-Powered-By header is not present
- **[PASS]** Server header is present without version info
- **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload).

### Content Security Policy (B — 70/100)

*2 of 10 CSP checks passed*

- **[INFO]** Raw CSP policy
- **[WARNING]** default-src directive is missing — default-src provides a fallback for other directives. Set it to restrict default resource loading.
- **[INFO]** No script-src or default-src to check for 'unsafe-inline'
- **[INFO]** No script-src or default-src to check for 'unsafe-eval'
- **[INFO]** No script-src or default-src to check for wildcard
- **[PASS]** object-src falls back to default-src
- **[WARNING]** base-uri directive is missing — Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
- **[PASS]** frame-ancestors directive is set
- **[WARNING]** form-action directive is missing — form-action restricts where forms can submit data, preventing form hijacking.
- **[INFO]** upgrade-insecure-requests is not set — This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

### TLS & Certificates (A+ — 100/100)

*TLS 1.3, 8 checks passed*

- **[PASS]** TLS 1.3 is used
- **[PASS]** Strong cipher suite is used
- **[PASS]** HTTP/2 is negotiated
- **[INFO]** OCSP stapling not enabled — Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server.
- **[PASS]** Certificate is valid (expires in 49 days)
- **[PASS]** Certificate chain has 3 certificates
- **[PASS]** Certificate uses modern signature algorithm
- **[PASS]** Certificate covers 1 domain(s)
- **[PASS]** Certificate is issued by a trusted CA

### Cookie Security (A+ — 100/100)

*1 cookies analyzed, 3 checks passed*

- **[PASS]** Cookie '__cf_bm' has the Secure flag
- **[PASS]** Cookie '__cf_bm' has the HttpOnly flag
- **[PASS]** Cookie '__cf_bm' has SameSite=None

### Cookie Hygiene (A+ — 100/100)

*All 1 cookie(s) pass hygiene checks*

- **[PASS]** All 1 cookie(s) pass hygiene checks

### WAF / Bot Protection (A — 90/100)

*Cloudflare*

- **[PASS]** Cloudflare detected — Detected via: cf-ray: a539d6273f66d618-CDG

### security.txt (C — 60/100)

*No security.txt file found*

- **[INFO]** No security.txt file found — security.txt (RFC 9116) provides a standardized way for security researchers to report vulnerabilities. Create one at /.well-known/security.txt with at least a Contact field.

### Cross-Origin Tab Safety (C — 75/100)

*2 of 11 new-tab link(s) missing rel=noopener*

- **[WARNING]** 2 link(s) open in a new tab without rel=noopener — Without rel="noopener", the destination tab can navigate the original tab via window.opener -- a reverse-tabnabbing phishing primitive. Modern browsers default to noopener since Chrome 88 / Firefox 79 / Safari 12.1, but explicit rel="noopener noreferrer" remains the documented best practice for older browsers, in-app webviews, and security scanners.

### CSP Inline-Style Readiness (C — 75/100)

*18 inline style attribute(s) detected*

- **[WARNING]** 18 inline style attribute(s) detected — Each `style=""` attribute forces `style-src 'unsafe-inline'` in any Content-Security-Policy, which negates most of CSP's XSS-mitigation value. 18 inline style(s) is moderate. Affected element types include: h1, div, h2, form, label. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win.

### Trusted Types (XSS Sink Hardening) (B — 95/100)

*Trusted Types not enabled*

- **[INFO]** Trusted Types not enabled — Trusted Types (CSP3) is a Chrome 83+ defense that requires DOM-XSS sinks (innerHTML, document.write, eval, ...) to receive a typed-and-sanitized value rather than a raw string. Adding `Content-Security-Policy: require-trusted-types-for 'script'; trusted-types default` neutralizes most DOM-XSS even when a payload reaches a sink. Adoption is currently ~0.1% of pages so this is informational; a roll-out usually starts in report-only mode.

### Bot Challenge Detection (A+ — 100/100)

*Scan reached real page content (no bot-protection interstitial)*

- **[PASS]** No bot-protection interstitial detected -- the rest of the report reflects the real page

### Soft-404 Detection (A+ — 100/100)

*No soft-404 patterns detected in page title or headings*

- **[PASS]** No soft-404 patterns detected in page title or headings

### Empty Page Detection (A+ — 100/100)

*Page has substantive body text and no placeholder / template-leak signals*

- **[PASS]** Page has substantive body text and no placeholder / template-leak signals

### Geo-Restriction Detection (A+ — 100/100)

*No geo-restriction signals detected -- scan reached the page from an allowed region*

- **[PASS]** No geo-restriction detected

### Maintenance Mode Detection (A+ — 100/100)

*No maintenance-mode signals detected -- scan reached a normal page*

- **[PASS]** No maintenance-mode signals detected

### Subresource Integrity Adoption (F — 30/100)

*0% SRI adoption (0/1 third-party resources)*

- **[WARNING]** SRI adoption: 0/1 third-party resources protected (0%) — Of 1 third-party `<script>` / `<link rel=stylesheet>` resources, 0 (0%) declare a Subresource Integrity hash via the `integrity=` attribute. SRI binds the page to the exact bytes of the third-party resource: if the CDN is compromised, attacker-modified bytes won't match the declared hash and the browser refuses to execute the resource.

Missing SRI on (first 1 examples):
  - https://fonts.googleapis.com/css2?display=swap&family=Poppins:ital,wght@0,200;0,300;0,400;0,500;0,700;1,200;1,300;1,400;1,500;1,700

Fix: add `integrity="sha384-..."` and `crossorigin="anonymous"` attributes. Generators: srihash.org, or in-browser via `await crypto.subtle.digest('SHA-384', bytes)`. Cache-bust the resource URL when you change versions, since the integrity hash will mismatch with old cached bytes.

### CORS Depth (A+ — 100/100)

*No CORS response headers -- the resource is same-origin-only by browser default*

- **[PASS]** No CORS response headers -- the resource is same-origin-only by browser default

### Permissions-Policy Granularity (C — 60/100)

*No Permissions-Policy header set -- powerful features (camera / microphone / geolocation / payment / USB) default to allow-on-same-origin*

- **[WARNING]** Permissions-Policy header not set -- features default to allow-on-same-origin — Without a `Permissions-Policy` (or legacy `Feature-Policy`) header, every powerful browser feature defaults to its spec default policy (typically `self`). A third-party iframe injected via XSS or a misconfigured embed can still request access to the user's camera, microphone, geolocation, payment APIs, USB devices, etc. Explicitly deny features the page doesn't need:

```
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=()
```

Features the page legitimately uses can stay enabled with `feature=(self)`.

### Referrer-Policy Strictness (B — 75/100)

*Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)*

- **[INFO]** Referrer-Policy header not set -- browser default applies — Without an explicit `Referrer-Policy` header, the browser falls back to its default policy. Modern browsers (Chrome 85+, Firefox 87+, Safari 15+) default to `strict-origin-when-cross-origin`, which is privacy-safe. Legacy browsers default to the leaky `no-referrer-when-downgrade`, which sends the full URL (including path + query) on cross-origin HTTPS-to-HTTPS requests. Set an explicit header to ensure consistent behavior:

```
Referrer-Policy: strict-origin-when-cross-origin
```

This matches the modern browser default and is privacy-safe without breaking referrer-based same-origin analytics.

### Source Map Exposure (A+ — 100/100)

*Source-map probe didn't run on this scan*

- **[PASS]** Source-map probe didn't run on this scan

### HTML Version Disclosure (A+ — 100/100)

*No software-version disclosures in HTML*

- **[PASS]** No software-version disclosures in HTML

### Open Redirect Surface (A+ — 100/100)

*No redirect-shaped query parameters in DOM links*

- **[PASS]** No redirect-shaped query parameters in DOM links

### Auth Security (A+ — 100/100)

*Page is not a login form -- auth-security checks are N/A*

- **[PASS]** Page does not appear to be a login form

### Subdomain Inventory Exposure (A+ — 100/100)

*No risky subdomain names in certificate SANs*

- **[PASS]** No risky subdomain names in certificate SANs

---

## Advanced Security

### Subresource Integrity (F — 20/100)

*0 of 1 external resources have SRI*

- **[WARNING]** External link from fonts.googleapis.com lacks integrity attribute — Without SRI, if this CDN is compromised, attackers could inject malicious code.

### JS Library Vulnerabilities (A+ — 100/100)

*No known vulnerabilities*

- **[PASS]** No known JavaScript library vulnerabilities detected

### Information Leakage (A+ — 100/100)

*No exposures*

- **[INFO]** No security.txt found — Consider adding a security.txt at /.well-known/security.txt.
- **[PASS]** No sensitive files exposed

### Email Security (F — 0/100)

*no DMARC*

- **[WARNING]** No DMARC record found — Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc.<domain> starting with v=DMARC1.
- **[WARNING]** SPF record has no `all` mechanism — Without a trailing `all` mechanism, receivers fall back to neutral for any sender not explicitly listed -- effectively no enforcement. Append -all (or ~all during rollout).
- **[INFO]** No DKIM detected via common selectors — DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative.
- **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts.<domain> and a policy file at https://mta-sts.<domain>/.well-known/mta-sts.txt.
- **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.<domain>.
- **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored.

### API Surface (A+ — 100/100)

*No API specs or GraphQL introspection found (probed 11 candidate path(s))*

- **[PASS]** No API specs or GraphQL introspection found (probed 11 path(s))

### Permissions-Policy (D — 40/100)

*No header set*

- **[WARNING]** No Permissions-Policy header — Consider adding a Permissions-Policy header to restrict browser feature access from embedded content.

### CORS Configuration (B — 80/100)

*No CORS headers*

- **[PASS]** No CORS headers present — secure default

---

## Performance

### Page Weight Budget (B — 72/100)

*1.5 MB transferred, 53 requests*

- **[PASS]** Page weighs 1.7 MB (1.5 MB transferred)
- **[WARNING]** Images are 1.4 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size.
- **[INFO]** 53 HTTP requests
- **[INFO]** Estimated 0.31 g CO2 per page load

### Third-Party Impact (A — 85/100)

*22% third-party, 0 ms blocking*

- **[INFO]** Third-party code accounts for 22% of page weight (329.8 KiB of 1.5 MiB)
- **[PASS]** Third-party blocking time is low (0 ms)

### Text Compression (A+ — 100/100)

*All text resources are compressed*

- **[PASS]** All text resources are compressed

### Image Optimization (C — 60/100)

*22 images, 0 KB saveable*

- **[WARNING]** https://www.amadohastaelextremo.es/assets/images/i... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.amadohastaelextremo.es/assets/images/i... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.amadohastaelextremo.es/assets/images/i... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.amadohastaelextremo.es/assets/images/i... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.amadohastaelextremo.es/assets/images/i... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.
- **[WARNING]** https://www.amadohastaelextremo.es/assets/images/i... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS.

### JS Execution Cost (C — 60/100)

*1112ms total JS execution*

- **[WARNING]** https://www.amadohastaelextremo.es/: 885ms CPU time
- **[INFO]** Unattributable: 226ms CPU time

### Font Loading (A+ — 100/100)

*6 fonts (47 KB)*

- **[INFO]** 6 font(s) use font-display: swap (FOUT risk but functional)

### JS Bundles (A+ — 100/100)

*1 scripts, 0 KB unused*


### Resource Caching (A+ — 100/100)

*All resources properly cached*

- **[PASS]** No caching issues found

### Critical Rendering Path (A+ — 100/100)

*No render-blocking resources*

- **[PASS]** No render-blocking resources detected

### Resource Hints (A+ — 100/100)

*No optimization needed*

- **[PASS]** No resource hint issues

### HTTP/3 (QUIC) (B — 75/100)

*HTTP/3 not advertised*

- **[INFO]** HTTP/3 (QUIC) is not advertised — HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads.

### Document Compression (B — 80/100)

*Document response uses gzip; brotli would be ~20% smaller*

- **[INFO]** Main HTML response uses gzip (brotli would be ~20% smaller) — All current browsers support brotli. Most CDNs (Cloudflare, Fastly, AWS CloudFront, Vercel, Netlify) can switch from gzip to brotli with a single config flag. Origin servers (nginx, Apache) need a brotli module compiled in -- nginx-brotli or Apache mod_brotli.

### Asset Compression

*No text asset hosts to measure*

- **[INFO]** No third-party or subdomain host served enough text assets to measure — Asset compression is measured per host, from one HEAD request against a sampled resource. Pages that serve all their JS and CSS from the document's own origin are covered by the document compression check instead.

### LCP Image Preload (A+ — 100/100)

*LCP preload audit not available*

- **[PASS]** LCP image preload audit not available for this scan

### Main HTML Cache-Control (A+ — 100/100)

*Main HTML max-age=0 (≤ 5min) is appropriate*

- **[PASS]** Main HTML max-age=0 (≤ 5min) is appropriate

### Server-Timing Observability (B — 85/100)

*No Server-Timing header found*

- **[INFO]** No Server-Timing header found — Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge.

### Server Response Intelligence (A+ — 100/100)

*2 server-response signal(s) detected*

- **[PASS]** `Vary` header declared: Accept-Encoding — The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class).
- **[PASS]** `Last-Modified` present -- timestamp-based conditional GET supported — Consider also setting `ETag` for stronger revalidation -- ETags are content hashes that don't suffer from clock-skew or DST issues. Last-Modified alone is functional for conditional GETs and not a bug.

### Page Weight Inventory (C — 60/100)

*53 resources · 1.5 MB · 0 KB savings available*

- **[WARNING]** Page weight 1.5 MB exceeds 1 MB target by 473 KB
- **[INFO]** 34 third-party resources (22% of weight)
- **[INFO]** 1 resources over 200KB

### Render-Blocking Resources (A+ — 100/100)

*No render-blocking resources detected*

- **[PASS]** No render-blocking resources detected in <head>

### Third-Party Resources (A+ — 100/100)

*No third-party resources detected*


### JavaScript Blocking (A+ — 100/100)

*No render-blocking JS or document.write usage detected*

- **[PASS]** No JavaScript blocking issues detected

### CSS Performance Depth (A+ — 100/100)

*No CSS performance depth issues detected*

- **[PASS]** No CSS performance depth issues detected

---

## Content Quality

### Links (F — 40/100)

*46 links checked, 25 healthy, 21 broken*

- **[CRITICAL]** 25 of 46 links are healthy
- **[WARNING]** Broken link: https://www.amadohastaelextremo.es/assets/images/favicon.... — Found in <link href>. Returns HTTP 429.
- **[WARNING]** Broken link: https://www.amadohastaelextremo.es/assets/images/apple-to... — Found in <link href>. Returns HTTP 429.
- **[WARNING]** Broken link: https://fonts.googleapis.com/css2?... — Found in <link href>. Returns HTTP 400.
- **[WARNING]** Broken link: https://www.amadohastaelextremo.es/assets/images/image01.... — Found in <img src>. Returns HTTP 429.
- **[WARNING]** Broken link: https://www.amadohastaelextremo.es/assets/images/image14.... — Found in <img src>. Returns HTTP 429.
- **[WARNING]** Broken link: https://www.amadohastaelextremo.es/assets/images/image09.... — Found in <img src>. Returns HTTP 429.
- **[WARNING]** Broken link: https://www.amadohastaelextremo.es/assets/images/image13.... — Found in <img src>. Returns HTTP 429.
- **[WARNING]** Broken link: https://www.amadohastaelextremo.es/assets/images/image02.... — Found in <img src>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://www.levante-emv.com/ribera/2026/06/06/disenos-val... — Found in <a href>. Returns HTTP 406.
- **[CRITICAL]** Broken link: https://www.amadohastaelextremo.es/assets/images/gallery0... — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://www.amadohastaelextremo.es/assets/images/gallery0... — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://www.amadohastaelextremo.es/assets/images/gallery0... — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://www.amadohastaelextremo.es/assets/images/gallery0... — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://www.amadohastaelextremo.es/assets/images/gallery0... — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://www.amadohastaelextremo.es/assets/images/gallery0... — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://www.amadohastaelextremo.es/assets/images/gallery0... — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://www.amadohastaelextremo.es/assets/images/gallery1... — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://www.amadohastaelextremo.es/assets/images/gallery0... — Found in <a href>. Returns HTTP 429.
- **[WARNING]** Broken link: https://www.amadohastaelextremo.es/assets/images/gallery0... — Found in <img src>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://www.amadohastaelextremo.es/assets/images/gallery0... — Found in <a href>. Returns HTTP 429.
- **[CRITICAL]** Broken link: https://www.amadohastaelextremo.es/assets/images/gallery0... — Found in <a href>. Returns HTTP 429.

### Mixed Content (A+ — 100/100)

*No mixed content detected — all resources use HTTPS.*

- **[PASS]** No mixed content detected — all resources use HTTPS

### Open Graph (A+ — 100/100)

*Open Graph tags are well configured for social sharing.*

- **[INFO]** og:description is short (46 characters) — Ideal length is 55–200 characters for social sharing previews.

### Open Graph / Twitter Card Depth (A+ — 100/100)

*OG image dimensions and Twitter card configuration look healthy*

- **[PASS]** OG/Twitter Card depth is clean -- dimensions, card type, and inheritance all valid

### Structured Data (A+ — 100/100)

*2 JSON-LD block(s) found — structured data is well configured.*

- **[PASS]** 2 blocks of custom type "OnlineStore" — unable to validate specific properties
- **[PASS]** 2 JSON-LD blocks found

### Rich Results Eligibility (A+ — 100/100)

*2 JSON-LD block(s) declaring 2 schema type(s)*

- **[PASS]** 2 rich-result schema type(s) declared — Inventory of structured-data types on the page (each may unlock a different SERP feature):

Product (×3), OnlineStore (×2)

Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient.

### Image Optimization (F — 35/100)

*5 issues found across 43 images*

- **[WARNING]** 5 images significantly larger than display size — Resizing to display dimensions could save approximately 290 KB.
- **[WARNING]** 43 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes.
- **[INFO]** 37 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight.
- **[WARNING]** All 10 images use legacy formats (JPEG/PNG/GIF) — WebP offers 25-35% smaller files than JPEG. Use <picture> with <source type="image/webp"> for modern format support.
- **[WARNING]** 1 images missing alt text — Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text.

### Autoplay Media (A+ — 100/100)

*No autoplay media on the page*

- **[PASS]** No autoplay media on the page

---

## Infrastructure

### DNS Records (A — 85/100)

*1 A records, 53 ms lookup*

- **[PASS]** Resolves to 1 IPv4 address(es)
- **[INFO]** Single A record — no DNS redundancy — Multiple A records provide failover if one server goes down.
- **[INFO]** No IPv6 (AAAA) records
- **[WARNING]** CNAME record at zone apex — A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
- **[PASS]** 2 nameserver(s) configured
- **[INFO]** No MX records — email not configured via DNS
- **[PASS]** SPF record present in TXT
- **[PASS]** DNS resolution time: 53 ms

### Subdomain Takeover (A+ — 100/100)

*No subdomain takeover risk detected*

- **[PASS]** CNAME does not point at a known takeover-able service

### DNSSEC (B — 80/100)

*Unsigned (DNSSEC not deployed)*

- **[INFO]** DNSSEC is not deployed — The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

### CAA Records (B — 80/100)

*No CAA records (any CA may issue certificates)*

- **[INFO]** No CAA records published — Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

### Reverse DNS (C — 60/100)

*0/1 IPs match cert SAN*

- **[INFO]** PTR lookup failed for 172.66.0.70: lookup 172.66.0.70: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

### Multi-Resolver DNS Speed (A+ — 100/100)

*Mean 24ms across 3 resolvers (spread 36ms)*

- **[PASS]** Quad9: 5ms
- **[PASS]** Cloudflare: 26ms
- **[PASS]** Google: 41ms

### Redirect Chain (A+ — 100/100)

*No redirects — direct access*

- **[PASS]** No redirects — direct access

### IPv6 Readiness (C — 60/100)

*No IPv6 support*

- **[INFO]** No IPv6 (AAAA) records found — IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

### Crawlability (A+ — 100/100)

*robots.txt present, sitemap with 1 URLs*

- **[PASS]** robots.txt is present
- **[PASS]** sitemap.xml is present
- **[PASS]** sitemap.xml is valid XML
- **[PASS]** sitemap.xml contains 1 entries
- **[PASS]** robots.txt references sitemap

### URL Variants (A+ — 100/100)

*www/non-www, trailing slash, HTTP→HTTPS*

- **[PASS]** www/non-www redirect configured correctly (preferred: www)
- **[PASS]** HTTP correctly redirects to HTTPS permanently

### Domain Intelligence

*Domain intelligence data not available*


---

## Compliance

### WCAG Compliance (A+ — 100/100)

*No testable criteria*


### Cookie Consent & Privacy (B — 80/100)

*No consent signals detected*

- **[WARNING]** No privacy policy link detected in the page — No link matching the privacy-policy vocabulary was found in the rendered page. The common privacy-policy paths were not probed for this scan, so this is an unconfirmed absence and is excluded from the regulatory-risk estimate.
- **[INFO]** No terms of service link detected
- **[INFO]** No cookie consent banner detected
- **[PASS]** 1 essential cookie(s) on initial load — no consent required
- **[INFO]** This is an automated check, not legal advice — BeaverCheck detects technical indicators of consent management. This does not constitute a legal compliance assessment. Consult a privacy professional for GDPR/CCPA compliance.

### Consent UX Depth (A+ — 100/100)

*No consent-UX depth issues detected*

- **[PASS]** No consent-UX depth issues detected

### Tracker Inventory (A+ — 100/100)

*No known trackers detected on this page*

- **[PASS]** No known trackers detected on this page

### Language & i18n (A — 90/100)

*Lang attribute present*

- **[PASS]** <html lang> attribute is present
- **[PASS]** <html lang> value is valid
- **[INFO]** No Content-Language HTTP header
- **[INFO]** Language signals are inconsistent — The <html lang> attribute and Content-Language header should agree.

### Hreflang Configuration (A+ — 100/100)

*No hreflang tags on this page*

- **[PASS]** No hreflang tags found (single-language site)

### Internationalization Extras (A+ — 100/100)

*No additional i18n signals detected*

- **[PASS]** No additional i18n signals detected

### Readability & Typography (A+ — 100/100)

*Font sizes and tap targets checked*


### Viewport Configuration (A+ — 100/100)

*Viewport properly configured*

- **[PASS]** Viewport meta tag is present
- **[PASS]** width=device-width is set
- **[PASS]** User zooming is allowed

### Accessibility Statement (B — 70/100)

*No accessibility statement detected*

- **[WARNING]** No accessibility statement detected — Sites are increasingly expected to publish an accessibility statement. Required by EU Web Accessibility Directive 2016/2102 for public-sector bodies; recommended best practice elsewhere. Common URLs: /accessibility, /accessibility-statement, /a11y. Detection is by link URL and anchor text, in a limited set of languages, so this is an unconfirmed absence.

### GDPR Article 13 Disclosures (F — 25/100)

*0 / 8 Art. 13 categories matched in homepage body*

- **[WARNING]** GDPR Article 13 disclosure coverage: 0 / 8 categories — Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 0 of 8 categories: . Missing: Data Protection Officer contact (where applicable), Data retention period, Data subject rights (access, erasure, rectification, etc.), Identity / contact details of the data controller, International data transfers, Legal basis for processing, Recipients of personal data, Right to lodge a complaint with a supervisory authority. Note: only the FIRST same-origin privacy-policy link is followed; deeper sub-pages (e.g. /legal/data-subject-rights) are not fetched.

### Third-Party Trackers (C — 55/100)

*1 trackers detected*

- **[INFO]** 1 third-party trackers detected — Found 1 analytics, 0 advertising, 0 marketing, 0 tag manager, 0 session-replay, 0 heatmap trackers.
- **[WARNING]** Trackers detected but no cookie policy found — This page loads 1 trackers but no cookie policy was detected. GDPR requires disclosure when using tracking cookies.
- **[WARNING]** Trackers detected but no privacy policy found — Most data protection regulations require a privacy policy when collecting user data via trackers.

### Cookie & Tracker Inventory (A+ — 100/100)

*1 cookies · 1 trackers · 0 pre-consent*

- **[INFO]** 1 third-party tracker(s) detected on page

### Tracking Pixel Inventory (A+ — 100/100)

*No tracking pixels detected*

- **[PASS]** No tracking pixels detected

### Browser Fingerprinting (A+ — 100/100)

*No browser-fingerprinting libraries detected*

- **[PASS]** No browser-fingerprinting libraries detected

### Cross-Site Cookies (SameSite=None) (B — 85/100)

*1 cross-site cookie(s) (1 tracking-shaped, 0 essential)*

- **[INFO]** 1 tracking-shaped cross-site cookie(s): __cf_bm — Cookies with SameSite=None travel in cross-site contexts (third-party iframes, cross-origin POSTs, embedded widgets). With third-party cookies dying in Chrome/Firefox, the legitimate use cases narrowed to SSO + payment widgets + federated auth. Each tracking-shaped cookie surfaced here is a cross-site analytics or ad-tech surface that needs explicit privacy-policy disclosure beyond basic cookie banner consent. Audit each: is it conditional on consent? Does the privacy policy name the recipient + purpose? Switching to SameSite=Lax disables the cross-site travel without breaking same-site analytics.

### Beacon Tracking (sendBeacon) (A+ — 100/100)

*No navigator.sendBeacon usage detected in inline scripts*

- **[PASS]** No navigator.sendBeacon usage detected in inline scripts

---

## Legal

### Legal Page Ecosystem (F — 35/100)

*1 of 7 expected legal pages detected*

- **[PASS]** Privacy Policy detected — Found at https://legal.amadohastaelextremo.es/, linked from footer.
- **[WARNING]** Terms of Service not detected — No link matching common Terms of Service URL patterns or link text was found. Most websites are expected to have a Terms of Service, especially those collecting user data.
- **[INFO]** Cookie Policy not detected — No link matching common Cookie Policy URL patterns or link text was found. Most websites are expected to have a Cookie Policy, especially those collecting user data.
- **[INFO]** Accessibility Statement not detected — No link matching common Accessibility Statement URL patterns or link text was found. Most websites are expected to have a Accessibility Statement, especially those collecting user data.
- **[INFO]** DMCA / Copyright Notice not detected — No link matching common DMCA / Copyright Notice URL patterns or link text was found. Most websites are expected to have a DMCA / Copyright Notice, especially those collecting user data.
- **[INFO]** Refund / Returns Policy not detected — No link matching common Refund / Returns Policy URL patterns or link text was found. Most websites are expected to have a Refund / Returns Policy, especially those collecting user data.
- **[INFO]** Acceptable Use Policy not detected — No link matching common Acceptable Use Policy URL patterns or link text was found. Most websites are expected to have a Acceptable Use Policy, especially those collecting user data.

### Copyright Notice (C — 55/100)

*No copyright notice detected*

- **[INFO]** No copyright notice detected — No copyright notice detected in the page content. While not legally required in most jurisdictions (copyright exists automatically), a notice is standard practice and signals site ownership.

### Regulatory Indicators

*1 regulatory indicator(s) detected*

- **[INFO]** This is a technical scan, not a legal assessment — BeaverCheck detects technical indicators that may suggest regulatory relevance. This is not a compliance audit and should not be relied upon for legal decisions. Consult qualified legal counsel for compliance assessments.
- **[INFO]** GDPR indicators detected (moderate confidence) — Indicators suggesting GDPR may be relevant: European TLD detected: .es. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents.

### Third-Party Data Sharing

*1 third-party service(s) detected*

- **[INFO]** Data inventory for transparency purposes — This inventory identifies third-party services that receive data from your site visitors. Under regulations like GDPR (Article 30), maintaining records of data processing activities is commonly considered a best practice. This automated scan provides a starting point — it may not capture all data flows.
- **[INFO]** 1 third-party services across 1 categories — 1 third-party services detected across 1 categories: CDN (1). Each of these services receives some user data from your site visitors.
- **[INFO]** Cloudflare (CDN) — Detected via cookie name. Typically collects: IP address (transient), Request metadata. Privacy policy: https://www.cloudflare.com/privacypolicy/. Data Processing Agreement available.

### Compliance Badges (C — 55/100)

*0 compliance badge(s) detected*

- **[INFO]** No compliance badges detected — No recognized compliance certification badges or seals were found. This is common — many sites do not display compliance badges.

---

## Availability

### CDN & Delivery (A — 85/100)

*Document and assets on Cloudflare*

- **[PASS]** Document is served via Cloudflare CDN (edge: CDG)
- **[INFO]** CDN cache status: DYNAMIC
- **[PASS]** Assets on Cloudflare: res.cloudinary.com (assets: 4)

### HTTP Caching (B — 75/100)

*max-age=0*

- **[PASS]** Cache-Control header is set
- **[PASS]** Last-Modified header present

### Operational Status Page (B — 80/100)

*No status page link detected*

- **[INFO]** No operational status page link detected — Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

### Transport Security (B — 75/100)

*HTTP/3, HSTS, and TLS version analysis*

- **[INFO]** HTTP/3 (QUIC) not advertised — HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
- **[WARNING]** Missing Strict-Transport-Security header — HSTS tells browsers to only use HTTPS, preventing SSL stripping attacks.
- **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT)

### Health Check Endpoint (B — 80/100)

*No conventional health endpoint found*

- **[INFO]** No conventional health endpoint found — Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.

### CDN Cache Observability (A+ — 100/100)

*Cache state: DYNAMIC*

- **[PASS]** CDN cache state observable via 1 header(s)

---

## Accessibility

### Landmark Structure (B — 75/100)

*4 landmarks*

- **[PASS]** <main> landmark present
- **[WARNING]** No <nav> landmark found
- **[WARNING]** Skip navigation link is missing (WCAG 2.4.1) — Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

### Heading Hierarchy (A — 90/100)

*13 headings*

- **[WARNING]** Multiple H1 headings (5 found) — A page should have only one H1. Multiple H1s dilute the document outline.

### Heading Text Quality (A+ — 100/100)

*All 13 heading(s) have substantive, well-formed text*

- **[PASS]** Heading text quality is clean -- no placeholder, length, or styling issues

### Alt Text Quality (A — 88/100)

*1 of 43 images have issues*

- **[CRITICAL]** 1 image(s) missing alt attribute — Images without alt text are invisible to screen readers.
- **[INFO]** 1 image(s) with alt text over 125 characters
- **[PASS]** 1 decorative image(s) correctly marked
- **[PASS]** 40 image(s) with good alt text

### Form Accessibility (D — 46/100)

*5 of 9 controls have issues*

- **[CRITICAL]** 2 control(s) without accessible label — Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
- **[WARNING]** 3 control(s) rely on placeholder only — Placeholder text disappears on focus and is not a reliable label.
- **[PASS]** 4 control(s) properly labeled

### Link & Button Quality (A — 88/100)

*57 links, 86 buttons — all OK*

- **[WARNING]** 11 link(s) open in new tab without warning — Add '(opens in new tab)' to link text or aria-label.
- **[PASS]** 46 link(s) with descriptive text

### Form Input Types (A+ — 100/100)

*9 form control(s) checked, no type mismatches*

- **[PASS]** No input-type mismatches detected

### Form Input Quality (A+ — 100/100)

*9 form control(s) checked, no input-semantic issues*

- **[PASS]** All form input semantics look correct

### Mobile Keyboard & Autofill (D — 60/100)

*3/3 eligible field(s) missing autocomplete or inputmode*

- **[WARNING]** 1 field(s) missing recommended autocomplete attribute — WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
- **[WARNING]** 2 field(s) would benefit from inputmode attribute — Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: tel, email.

### Document Language (A+ — 100/100)

*Lang attribute set to "es"*

- **[PASS]** <html lang="es"> is set and valid

### Tabindex Anti-Patterns (A+ — 100/100)

*5 explicit tabindex attribute(s) checked, no anti-patterns*

- **[PASS]** No tabindex anti-patterns detected

### Iframe Accessibility (A+ — 100/100)

*No iframes on this page*

- **[PASS]** No iframes on this page

### Tap Target Adequacy (A+ — 100/100)

*All tap targets meet WCAG 2.5.5/2.5.8 sizing*

- **[PASS]** All tap targets meet WCAG 2.5.5 (44x44px) sizing

### Mobile-Readable Font Sizes (D — 60/100)

*60% of visible text renders at >= 12 CSS px (6 below threshold)*

- **[WARNING]** 6 text node(s) render below 12 CSS pixels on mobile — Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <a> 11.0px ("TIENDA"); <a> 11.0px ("EDICIONES ESPECIALES"); <a> 11.0px ("HISTORIA"); <a> 11.0px ("CONTACTO"); <p> 9.2px ("© Amado hasta el extremo 2026. Para mayo...").

---

## UX

### 404 Error Page (C — 55/100)

*HTTP 404, custom page*

- **[PASS]** Correct 404 status code returned
- **[PASS]** Custom styled 404 page

### Favicon & Branding (F — 30/100)

*2 icon(s) detected*

- **[WARNING]** No favicon.ico at site root — Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
- **[PASS]** HTML icon links detected
- **[PASS]** Apple touch icon present

### Web Manifest (D — 40/100)

*Not found*

- **[INFO]** No web manifest found — No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

### PWA Depth (A+ — 100/100)

*No PWA depth issues detected*

- **[PASS]** No PWA depth issues detected

### Dark Mode Support (B — 80/100)

*Dark mode detected*

- **[PASS]** color-scheme meta tag present — The site declares support for light and dark color schemes via <meta name='color-scheme'>.
- **[INFO]** Detection limited to meta tags and inline styles — External CSS files may contain prefers-color-scheme rules not visible to this scan.

### Print Stylesheet (D — 40/100)

*No print styles*

- **[INFO]** No print-specific styles detected — When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

### Navigation UX (F — 0/100)

*No navigation patterns*

- **[INFO]** No breadcrumbs, search, or skip link detected — These navigation aids help users orient themselves and find content efficiently, especially on large sites.

### Mobile UX Depth (A+ — 97/100)

*1 mobile-depth signal(s) detected*

- **[INFO]** No `<meta name="theme-color">` -- browser chrome falls back to default — Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

---

## SEO

### Canonical URL (A+ — 100/100)

*Properly configured*

- **[PASS]** Canonical tag present
- **[PASS]** Canonical is self-referencing
- **[PASS]** Canonical matches final URL after redirects
- **[PASS]** Canonical target returns 200

### Meta Tags (A — 85/100)

*Title: 8 chars*

- **[PASS]** Page title is set
- **[WARNING]** Title is only 8 characters — consider expanding
- **[PASS]** Meta description length (144 chars) is optimal
- **[INFO]** Title and H1 have very different wording — Alignment helps users confirm they've reached the right page.

### Title Style Depth (A+ — 100/100)

*Title style is clean -- consistent separator, no stale year, no keyword stuffing*

- **[PASS]** Title style is clean

### Content Depth (A — 85/100)

*1988 words, Very Difficult*

- **[PASS]** Page has 1988 words — good depth for search engines
- **[INFO]** Text-to-HTML ratio is 4% — Very low ratio suggests heavy framework overhead or boilerplate.
- **[INFO]** Reading level: Very Difficult (grade 13)

### Internal Links (A+ — 100/100)

*39 internal, 18 external*

- **[PASS]** 39 internal links (68%)
- **[PASS]** 100% of links use descriptive anchor text
- **[INFO]** 39 internal / 18 external links

### Image SEO (A+ — 100/100)

*41 images, 31 descriptive filenames*

- **[INFO]** 10 image(s) have hash/generic filenames

### Hreflang

*0 hreflang tags*


### Hreflang URL Quality (A+ — 100/100)

*No hreflang tags on the page*

- **[PASS]** No hreflang tags on the page

### Hreflang Completeness (A+ — 100/100)

*No hreflang tags on this page -- check is N/A (single-language site or unannotated)*

- **[PASS]** No hreflang tags found -- completeness check is N/A

### Sitemap Freshness (A+ — 100/100)

*Sitemap updated within 90 days (1/1 URLs have lastmod)*

- **[PASS]** Sitemap actively maintained — newest lastmod: today

### Sitemap × Robots Consistency (A+ — 100/100)

*No sitemap-vs-robots conflicts detected*

- **[PASS]** Sitemap URLs are not blocked by robots.txt

### Sitemap Hygiene (A+ — 100/100)

*Sitemap structure / size look healthy (1 URLs, 8 KB)*

- **[PASS]** Sitemap structure / size look healthy (1 URLs)

### Markup Quality (A+ — 100/100)

*No markup-quality issues detected*

- **[PASS]** No markup-quality issues detected

---

## Sustainability

### CO2 Per Page Load (A — 85/100)

*0.35g CO2 per view*

- **[PASS]** 0.35g CO2 per page view — This page transfers 1.5 MB, producing an estimated 0.35g of CO2 per visit using the Sustainable Web Design model (v4). Breakdown: data center 0.01g, network 0.07g, end-user device 0.27g.
- **[INFO]** At 10,000 monthly views: 41.5 kg CO2/year — With 10,000 page views per month, this page would generate approximately 41.5 kg of CO2 annually — equivalent to charging 5189 smartphones.
- **[PASS]** Green hosting reduces data center emissions

### Green Hosting (A+ — 100/100)

*Green (both)*

- **[PASS]** Both hosting and CDN use renewable energy
- **[INFO]** Cloudflare: Verified by the Green Web Foundation
- **[INFO]** Cloudflare: 100% renewable energy for global network since 2019
- **[INFO]** Green hosting status based on known provider commitments — Green hosting detection uses a curated database of provider renewable energy commitments. This is not a real-time verification. For authoritative checks, visit thegreenwebfoundation.org.

### Repeat Visit Weight (A+ — 100/100)

*97% cached*

- **[PASS]** 97% reduction on repeat visits — Returning visitors download only 46 KB (vs 1496 KB first visit). 52 of 53 resources are served from browser cache, saving 0.34g CO2 per repeat visit.
- **[INFO]** Repeat visit: 0.01g CO2 (first visit: 0.35g)

### Carbon Budget (A — 85/100)

*24th percentile*

- **[PASS]** 0.35g CO2 — below the sustainability target of 0.50g — Cleaner than an estimated 76% of websites analyzed. This page meets the Web Sustainability Guidelines target.
- **[INFO]** Estimated 24th percentile — Compared to: top 10% = 0.20g, target = 0.50g, median = 0.60g per page view.

### Transfer Efficiency (A+ — 100/100)

*100% efficient*

- **[PASS]** Transfer efficiency: 100% — Only 0 KB of potential savings identified. Your page is well-optimized for size.

### Web Font Weight Variants (B — 85/100)

*5 font weights loaded across 1 famil(y/ies)*

- **[INFO]** 5 font weights loaded -- review whether all are used — 5+ weights for a single page is often more than needed. Compare against the actual font-weight CSS rules in your stylesheets; trim weights that aren't applied to any element. Affected families: Poppins.

---

---

*Generated by [BeaverCheck](https://beavercheck.com) — https://beavercheck.com/results/93e5394c-ce60-4f21-bdb2-8baf801614f2*