jom.com.mx
JÖM - Muebles – JÖM Muebles
1 failed · 5 warnings · 23 passed
Audited Sun, 19 Jul 2026 01:45:23 GMT · https://jom.com.mx/
Meta & Head
20.8/25
Title, description, canonical, social tags — what search engines read first.
Meta descriptionhigh impactlow effort
No meta description found
The meta description is your ad copy in search results; without one, engines pull an arbitrary snippet from the page, which usually reads poorly and costs you clicks. Add <meta name="description" content="..."> with 70–160 characters that summarize the page and give a concrete reason to click — what the visitor gets plus a differentiator (free, instant, no signup). Write a unique description per page: one duplicated across the site is treated much like a missing one.
8 passing checks
- Title tag<title> is "JÖM - Muebles – JÖM Muebles" (34 characters)
- Canonical URLCanonical href is "https://jom.com.mx/"
- Viewport meta tagViewport is "width=device-width,initial-scale=1"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Open Graph tagsAll core Open Graph tags present (og:title, og:description, og:image, og:url)
- Twitter card tagtwitter:card is "summary_large_image"
- Page allows indexingNo restrictive robots meta tag
Content & Structure
22.7/25
Headings, copy depth, images, structured data, internal linking.
Image alt textmedium impactlow effort
42 of 64 images have alt text
Alt text is how search engines understand what an image shows — it feeds image-search rankings and is what screen readers announce to blind visitors. Add a short, specific alt attribute to every meaningful image, describing the content rather than listing keywords: alt="Golden retriever puppy playing in snow" beats alt="dog puppy pet animal". Give purely decorative images an empty alt="" instead of omitting the attribute, so assistive technology knows to skip them rather than reading out the filename.
Heading hierarchylow impactlow effort
Heading level jumps from h2 ("Buscar") to h4 ("Productos")
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: "JÖM Muebles"
- Word count6113 words of visible text
- Structured data (JSON-LD)JSON-LD types found: Organization
- HTML lang attribute<html lang="es">
- JavaScript-dependent contentvisible text ~24671 chars in the initial HTML
- Internal linking65 internal, 15 external links
Technical
22.2/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
Fast time to first bytehigh impactmedium effort
1310 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.
HTML5 doctypelow impactlow effort
No doctype declaration found at the start of the document
Without a doctype, browsers render in quirks mode — inconsistent layout, and validators flag the page. Add <!DOCTYPE html> as the very first line of the document, before the <html> tag. Watch out for whitespace, comments, or BOM characters sneaking in before it.
9 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 size335.5 KB
- Missing pages return 404missing paths return HTTP 404/410
- www and non-www resolve consistentlywww and non-www converge on the same host
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.