breteame.com
Breteame — Profesionales verificados en Costa Rica
0 failed · 4 warnings · 24 passed
Audited Thu, 06 Aug 2026 05:16:12 GMT · https://breteame.com/
Meta & Head
23.6/25
Title, description, canonical, social tags — what search engines read first.
Open Graph tagsmedium impactlow effort
Missing Open Graph tags: og:url
Your Open Graph markup is incomplete, so social platforms fall back to guessed text or drop the preview image entirely when this page is shared — a broken card gets far fewer clicks than a complete one. Add the missing og:url tag to <head>. For og:image, use an absolute https:// URL to an image around 1200x630 pixels; relative paths are the usual reason previews break. Re-check with a platform's sharing debugger afterwards, since preview cards are cached.
8 passing checks
- Title tag<title> is "Breteame — Profesionales verificados en Costa Rica" (50 characters)
- Meta descriptionMeta description is "Encontrá fontaneros, electricistas, cerrajeros, jardineros y escombreros verificados cerca tuyo. Contactalos directo por WhatsApp o llamada." (140 characters)
- Canonical URLCanonical href is "https://breteame.com"
- Viewport meta tagViewport is "width=device-width, initial-scale=1"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Twitter card tagtwitter:card is "summary_large_image"
- Page allows indexingrobots: index, follow
Content & Structure
24.1/25
Headings, copy depth, images, structured data, internal linking.
Heading hierarchylow impactlow effort
Heading level jumps from h1 ("Contratá profesionales verificados en Costa Rica") to h3 ("Fletes Económicos San Carlos//83082892")
Headings form the page's outline; when levels jump (h2 straight to h4), search engines and screen readers get a broken table of contents and the relationship between sections turns ambiguous. Fix the jump by stepping down one level at a time — promote the deeper heading, or add the missing intermediate level. The usual cause is choosing heading tags for their default font size; set sizes in CSS instead and let the tags reflect actual document structure.
6 passing checks
- Single H1 heading1 h1 found: "Contratá profesionales verificados en Costa Rica"
- Word count3352 words of visible text
- Structured data (JSON-LD)JSON-LD types found: WebSite, FAQPage
- HTML lang attribute<html lang="es">
- JavaScript-dependent contentvisible text ~4656 chars in the initial HTML
- Internal linking33 internal, 1 external links
Technical
22.7/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
Fast time to first bytehigh impactmedium effort
1200 ms
Time to first byte is the floor under every other speed metric — the browser can't parse, render, or fetch anything until the first byte arrives, so a slow TTFB drags down all Core Web Vitals and tests crawlers' patience. Add caching in front of the origin: full-page caching at a CDN (Cloudflare, Fastly) helps most, followed by server-side caches (Redis, object caching) and indexes on slow database queries. Measure from locations near your actual users — tuning only your fastest region leaves distant visitors just as slow.
Response compression enabledlow impactlow effort
no content-encoding header
This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.
10 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- No mixed content0 http:// subresource references
- Short redirect chainno redirects; URL resolves directly
- robots.txt present and permissiverobots.txt exists and allows crawling
- XML sitemap availablesitemap.xml exists and is valid XML
- Reasonable HTML size142.3 KB
- Missing pages return 404missing paths return HTTP 404/410
- www and non-www resolve consistentlywww and non-www converge on the same host
- HTML5 doctype<!DOCTYPE html> present
Performance
Core Web Vitals scoring via Google PageSpeed is coming soon.
Share your score
Embed this live badge on your site — it updates whenever the audit is re-run.