Este informe de auditoría web analiza https://www.CETEC.com en 12 dimensiones críticas con recomendaciones accionables.
https://www.CETEC.com
42Deficientede 100
Informe de Auditoría Web
CETEC Cereal Technologies
28 de junio de 2026 353ms respuesta HTTPS Seguro
Resumen Ejecutivo
https://www.CETEC.com scores 42/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 474 words, 56 images, and 1 schema blocks. Data confidence: 90%. Sustainability score: 75/100. Focus on the top recommendations below to improve your score.
353ms
Tiempo de Respuesta
474
Conteo de Palabras
56
Imágenes
190
Enlaces
Vista Previa del Sitio
Visitar SitioCargando vista previa…
Desglose de Puntuación — 12 Dimensiones
Problemas Principales a Solucionar
1[SEO] Title tag is very short (25 chars)
2[SEO] Missing meta description
3[SEO] Multiple H1 tags found (5)
4[SEO] Heading hierarchy gaps: h1 → h3 (skips h2)
5[SEO] Missing OG tags: og:description
6[SEO] Missing Twitter tags: twitter:description
7[SEO] 30 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
8[SEO] Title and H1 share no keywords — misaligned topic signals
9[SEO] High dofollow external link count (30) — excessive link equity leakage
10[SEO] Primary keyword "cetec cereal technologies" not found in H1
Recomendaciones Principales
1[Impact: High | Effort: Low] Expand your title to 50–60 characters for better click-through rates and SERP visibility
2[Impact: High | Effort: Low] Add a compelling meta description of 140–160 characters with target keywords (2025-2026 best practice)
3[Impact: High | Effort: Low] Consolidate to a single H1 tag — use H2–H6 for subtopics
4[Impact: High | Effort: Low] Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
5[Impact: Medium | Effort: Medium] Add missing Open Graph tags: og:description
6[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
7[Impact: High | Effort: Low] Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
8[Impact: Medium | Effort: Low] Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
9[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
10[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
11[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
12[Impact: Medium | Effort: Low] Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
Análisis Detallado por Categoría
Hallazgos Clave
1Canonical URL is set and matches the page URL
2HTML lang attribute set to "en-US"
3Favicon present
4159 internal links help establish site architecture
530 external links provide reference signals
6Content length of 474 words is adequate
7190 total links — within recommended range
8URL length (22 chars) is within optimal range
9No redirect chain — direct URL resolution
10Healthy internal link ratio: 84% of links are internal
11Primary keyword not in URL — acceptable for homepage/root URLs
12Moderate E-E-A-T signals (4 indicators)
13Low passive voice ratio (14%) — clear, active writing style
14Strong dwell/engagement signals: 3 indicators (ToC, related content, internal links)
15Social share buttons detected: ShareThis, Native Share
Problemas Encontrados
1Title tag is very short (25 chars)
2Missing meta description
3Multiple H1 tags found (5)
4Heading hierarchy gaps: h1 → h3 (skips h2)
5Missing OG tags: og:description
6Missing Twitter tags: twitter:description
730 external links missing rel="nofollow noopener noreferrer" — potential link equity leakage
8Title and H1 share no keywords — misaligned topic signals
9High dofollow external link count (30) — excessive link equity leakage
10Primary keyword "cetec cereal technologies" not found in H1
11Primary keyword missing from first paragraph
12Missing og:locale tag — social platforms may guess language/region
13OG image dimensions too small for social platforms
14Very high internal link density (335.4/1k words) — may appear spammy
15Primary keyword "cetec cereal technologies" not found in body content
Recomendaciones para Alcanzar 100%
1Expand your title to 50–60 characters for better click-through rates and SERP visibility
2Add a compelling meta description of 140–160 characters with target keywords (2025-2026 best practice)
3Consolidate to a single H1 tag — use H2–H6 for subtopics
4Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
5Add missing Open Graph tags: og:description
6Add rel="nofollow noopener noreferrer" and target="_blank" to all external links to prevent equity leakage and improve security
7Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
8Reduce dofollow external links to 2–5 per page. Add rel="nofollow" to low-value or affiliate links to preserve PageRank
9Include your primary keyword in the H1 heading for strongest on-page SEO signal
10Include your primary keyword naturally in the first paragraph to establish topical relevance early
11Include your primary keyword in the URL slug for improved crawlability and click-through rates
12Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
13Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
14Use a 1200×630px OG image and declare og:image:width / og:image:height for optimal previews
15Upgrade Twitter card to "summary_large_image" for larger, more engaging previews
16Reduce internal link density — excessive linking dilutes individual link value
17Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
18OG sharing completeness at 67% — add missing tags for better social previews
Hallazgos Clave
1Excellent server response time: 353ms
2HTML size is 294KB — acceptable
3No render-blocking scripts detected
425/56 images use lazy loading
5Responsive images with srcset detected
6Preconnect hints for: https://images.squarespace-cdn.com, https://use.typekit.net, https://p.typekit.net
71 async and 18 deferred scripts
8Lean CSS payload (~181KB)
9Gzip compression enabled
10Estimated LCP: ~1233ms — within Google's "good" threshold (<2.5s)
11Estimated INP: ~172ms — within Google's "good" threshold (<200ms)
Problemas Encontrados
1No WebP or AVIF image formats found
2Only 23/56 images have width/height attributes
3No font-display property found
4No effective Cache-Control header
510 inline <style> blocks
617 inline scripts
7Moderate JavaScript payload (~984KB)
8HTTP/1.1 detected — no multiplexing
9No CDN detected
1019 third-party scripts from 4 domains — significant performance impact
116 render-blocking CSS files — delays first paint
12Potentially unused CSS detected (large stylesheet count relative to page complexity)
13Potential long-task scripts: Inline script (~31KB)
14Moderate estimated CLS: 0.25 — above 0.1 "good" threshold
15Basic analytics only — missing event tracking or tag management
Recomendaciones para Alcanzar 100%
1Convert images to WebP or AVIF format for 30–50% file size reduction
2Add explicit width and height to all images to prevent Cumulative Layout Shift (CLS)
3Preload critical resources (fonts, hero images) with <link rel="preload">
4Add font-display: swap to web font declarations to show fallback text while fonts load
5Set Cache-Control headers with appropriate max-age to leverage browser caching
6Extract inline styles into external CSS files for better caching and maintainability
7Move inline scripts to external files with defer attributes
8Optimize JavaScript delivery with code splitting, deferred loading, and removing duplicate modules
9Upgrade to HTTP/2 or HTTP/3 for faster parallel resource loading and header compression
10Use a Content Delivery Network (CDN) like Cloudflare, CloudFront, or Fastly to reduce global latency
11Audit third-party scripts — defer non-critical ones and remove unused trackers/widgets to reduce main thread blocking
12Reduce render-blocking CSS by inlining critical CSS, using media queries on non-critical stylesheets, and loading non-critical CSS asynchronously
13Audit CSS with Chrome DevTools Coverage tab to identify and remove unused CSS rules
14Review large inline/external scripts that may block the main thread. Use web workers or break into smaller async chunks
15Reduce CLS: set image dimensions, preload web fonts, reserve space for ads and dynamic content
16Upgrade analytics: add Google Tag Manager for flexible tag deployment and configure custom events (form submissions, CTA clicks, scroll depth)
Hallazgos Clave
1Viewport meta tag present: initial-scale=1
2HTML5 doctype declared
3Character encoding declared
4Responsive images via srcset serve appropriate sizes per device
525 images with lazy loading benefit mobile data users
6Mobile-responsive hamburger menu detected
Problemas Encontrados
1Viewport does not include width=device-width
2No theme-color meta tag
3No web app manifest found
4Missing Apple touch icon
5Fixed-width elements detected (>800px) — may cause horizontal scrolling on mobile
6Popup/modal/interstitial detected — Google penalizes intrusive interstitials on mobile
7Only 1 manifest icon size(s) — recommend at least 4 (192, 384, 512, maskable)
8Estimated page weight ~4509KB — heavy for mobile data plans
Recomendaciones para Alcanzar 100%
1Set viewport to width=device-width, initial-scale=1 for proper mobile scaling
2Add <meta name="theme-color"> for browser chrome styling on mobile
3Create a manifest.json for PWA capabilities and add-to-homescreen support
4Add <link rel="apple-touch-icon"> for iOS homescreen icons
5Consider implementing a service worker for offline support and faster repeat visits
6Replace fixed pixel widths with relative units (%, vw, max-width) to prevent horizontal overflow on small screens
7Remove or minimize intrusive interstitials on mobile — Google's Page Experience update penalizes full-screen popups that block content
8Add multiple icon sizes (192x192, 384x384, 512x512, plus maskable) to your manifest for cross-device support
9Add env(safe-area-inset-*) CSS for proper display on notched/island devices
10Add :active / touch-action CSS for tactile feedback on mobile interactions
11Reduce page weight below 2MB: optimize images (WebP/AVIF), defer non-critical JS, remove unused CSS
Hallazgos Clave
1HTTPS enabled — encrypted connection
2HSTS header present — enforces HTTPS
3X-Content-Type-Options: nosniff is set
4Rate limiting recommended for form endpoints
Problemas Encontrados
1Missing Content-Security-Policy header
2Missing X-Frame-Options header
3Missing Referrer-Policy header
4Missing Permissions-Policy header
5Server header exposes technology: Squarespace
630 external links missing rel="noopener noreferrer" — security risk
7HSTS header present but missing preload directive
8Cookie security issues: missing HttpOnly flag; missing SameSite attribute
9No privacy policy detected
10No cookie consent banner detected
11No Subresource Integrity (SRI) on external scripts
Recomendaciones para Alcanzar 100%
1Implement a Content Security Policy to prevent XSS and injection attacks
2Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
3Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
4Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
5Add Cross-Origin-Opener-Policy: same-origin-allow-popups
6Add Cross-Origin-Resource-Policy: cross-origin
7Remove or obfuscate the Server header to avoid exposing your technology stack
8Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
9Add "preload" to your HSTS header and submit to hstspreload.org for maximum HTTPS enforcement
10Set Secure, HttpOnly, and SameSite=Strict (or Lax) attributes on all cookies to prevent session hijacking and CSRF
11Add a privacy policy link — required by GDPR, CCPA, and builds user trust
12Implement a cookie consent banner for GDPR/ePrivacy compliance
13Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
14Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
Hallazgos Clave
1Language declared: en-US
2All key landmarks present (main, nav, footer)
3All 34 buttons have accessible labels
4Rich ARIA implementation: 40 elements with ARIA attributes
Problemas Encontrados
1No skip navigation link
24 of 56 images (7%) missing alt text
31 form(s) missing proper labels
4Heading hierarchy has gaps — confusing for screen readers
5No focus styles detected
62 minor HTML validity issue(s)
733 images missing explicit dimensions — causes layout shifts for screen reader users
8CAPTCHA detected without accessible alternative
91 duplicate ID(s) — breaks ARIA references and label associations
Recomendaciones para Alcanzar 100%
1Add a "Skip to main content" link as the first focusable element for keyboard users
2Add descriptive alt text to all images — use empty alt="" only for decorative images
3Add <label> elements associated with every form input via for/id attributes
4Add :focus-visible styles to all interactive elements for keyboard navigation visibility
5Review and fix HTML structure issues for better accessibility and cross-browser compatibility
6Set explicit width and height (or CSS aspect-ratio) on all images to prevent layout shifts that disorient assistive technology users
7Provide an audio CAPTCHA alternative or use invisible/accessible CAPTCHA solutions (WCAG 1.1.1)
8Ensure all element IDs are unique — duplicate IDs break form labels, ARIA relationships, and fragment navigation
Hallazgos Clave
11 schema block(s): WebSite
2Strong semantic markup: nav, header, main, section, figure, figcaption, footer
3Complete social metadata (OG + Twitter Card)
4Breadcrumb navigation present — aids AI in understanding site hierarchy
517 strong entity mentions (bold/emphasized text)
6Social presence signals: instagram, facebook, youtube
76 call-to-action elements detected
8No AI crawlers blocked via meta tags — content accessible to AI search engines
9robots.txt file found
10robots.txt references 1 sitemap(s) — aids AI crawler discoverability
11High RAG-friendliness (100/100): 0 headings with IDs, 94 section anchors
12Content provenance signals detected (citations with sources, attributed claims)
Problemas Encontrados
1No FAQ or Q&A content patterns found
2No sitemap reference found
3robots.txt blocks CSS/JS/image assets — search engines and AI cannot render your page
4No llms.txt file found — AI models cannot find structured guidance for your site
5No content freshness signals (dateModified, datePublished, <time> elements)
Recomendaciones para Alcanzar 100%
1Add more structured data types (FAQ, HowTo, Breadcrumb) to improve AI comprehension
2Add hreflang tags if your site serves multiple languages or regions
3Add an FAQ section with FAQPage schema to increase chances of AI engine citations
4Create and reference an XML sitemap for AI crawler discoverability
5Remove Disallow rules for /css/, /js/, /images/ in robots.txt — Google and AI crawlers need these to render and understand your pages
6Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
7Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
8Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
9Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
Hallazgos Clave
1Strong entity emphasis: 17 key terms highlighted
2Good semantic-to-div ratio: 63 semantic elements
3Good paragraph length for readability and AI parsing
419 external citations — strong reference density for AI model training
51 call-to-action element(s) detected
6Good form usability score: 90/100
7Trust signals present: Trust Badges, HTTPS Security
8Clear value proposition detected in heading elements
Problemas Encontrados
1Content may be too thin for AI optimization (474 words)
2No structured Q&A content
3Weak E-E-A-T schema signals
4No author or expertise signals
5No CTA above the fold
6No social proof elements
Recomendaciones para Alcanzar 100%
1Expand content to 1000+ words with comprehensive topic coverage for better AI model training value
2Add FAQ or Q&A sections — AI models heavily rely on question-answer patterns for training data
3Add structured content (lists, comparison tables) that AI models can easily extract and reference
4Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
5Add Speakable schema markup to help voice assistants identify the most important content
6Include specific statistics, percentages, and data points that AI models can extract and cite in responses
7Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
8Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
9Add more clear CTAs ("Get Started", "Request Quote", "Contact Us") throughout the page for higher conversion rates
10Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
11Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
Hallazgos Clave
117 emphasized terms suggest unique, quotable insights
224 original data elements (charts, figures, data tables)
Problemas Encontrados
1No direct Q&A patterns for generative AI extraction
2No data tables for AI comparison extraction
3Few or no lists
4Content too thin for AI citation value
5Insufficient structured data for generative engine context
6No hreflang tags — generative engines cannot determine language/region targeting
Recomendaciones para Alcanzar 100%
1Structure content with clear questions as headings (H2/H3) followed by concise, definitive answers in the first paragraph
2Add comparison tables with structured data — generative AI engines frequently cite tabular content
3Use numbered and bulleted lists for step-by-step content — generative engines prefer structured, scannable formats
4Include how-to or step-by-step instructional content for generative AI answer inclusion
5Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
6Generative engines cite pages with substantial, authoritative content — aim for 1000+ words with unique insights
7Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
8Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
9Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
Hallazgos Clave
1Short paragraphs are well-suited for answer extraction
2Content length and paragraph structure are voice-search optimized
Problemas Encontrados
1No FAQ content or schema
2Content not optimized for featured snippets
3No Speakable schema for voice search
4Few concise answer paragraphs for snippet extraction
5No direct answer patterns ("X is defined as...", "X refers to...")
Recomendaciones para Alcanzar 100%
1Create an FAQ section with FAQPage structured data — essential for People Also Ask and featured snippet inclusion
2Consider adding how-to content with HowTo schema for step-by-step rich results
3Use question-based H2/H3 headings followed by a direct 40–60 word answer paragraph for featured snippet targeting
4Add Speakable schema to mark sections suitable for text-to-speech by voice assistants
5Add BreadcrumbList schema to your breadcrumb navigation
6Add more bullet/numbered lists — search engines frequently pull list content into People Also Ask results
7Consider adding video content with VideoObject schema for multimedia search results
8Write concise 40–60 word paragraphs that directly answer common questions — these are extracted as featured snippets and voice answers
9Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
Hallazgos Clave
1NAP information detected: phone: 15710597520, email: [email protected]
2Phone number(s) visible: 15710597520
3Email address found: [email protected]
Problemas Encontrados
1No LocalBusiness structured data
2No Google Maps embed
3No address microdata
4No geo meta tags
5No review/rating schema
Recomendaciones para Alcanzar 100%
1Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates
2Add an embedded Google Map to your contact or about page for local search signals
3Add PostalAddress schema or itemprop="address" microdata to your address elements
4Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
5Add AggregateRating schema to display star ratings in search results — reviews significantly impact local click-through rates
Hallazgos Clave
11 JSON-LD block(s) with types: WebSite
2All structured data uses JSON-LD format — Google's recommended format
3Some top-tier schemas: WebSite
4No schema validity issues detected
Problemas Encontrados
1Only basic schema implementation
2No sameAs properties in schema — missing entity disambiguation
3Schema property completeness averaging 50%
4No rich results eligibility detected
Recomendaciones para Alcanzar 100%
1Expand structured data with more specific schema types relevant to your content
2Add more top-tier schema types — consider: LocalBusiness, Organization, Product
3Consider adding secondary schema types: Person, HowTo, Service, Event for richer search features
4Add missing high-impact schemas: Organization, BreadcrumbList, Product
5Add BreadcrumbList schema — enables breadcrumb rich results in Google
6Add FAQPage schema to FAQ content — enables expandable rich results
7Consider adding HowTo schema for instructional content
8Add more schema types — diverse structured data improves AI and search engine understanding
9Add sameAs links to Organization/Person schema pointing to Wikipedia, Wikidata, social profiles
10Fill in missing recommended properties for each schema type
11Add FAQ, HowTo, or Breadcrumb schema to become eligible for enhanced search result features
12Add nested schemas (e.g., author within Article, offers within Product) to define entity relationships
13Add SearchAction schema to your WebSite type to enable the sitelinks search box in Google results
Hallazgos Clave
1Links are visually distinguishable (underline or decoration detected)
2Relative units (rem/em/clamp) detected — supports text resizing
3Good semantic element usage (63 semantic elements)
4Page language declared — aids assistive technology
5All ARIA roles are valid
6Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
7Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
Problemas Encontrados
1No prefers-reduced-motion support
2No high contrast mode support
3No error suggestion mechanisms detected in forms
4No focus styles detected
5No form error identification detected
Recomendaciones para Alcanzar 100%
1Add @media (prefers-reduced-motion: reduce) to disable animations for users who are sensitive to motion
2Add @media (prefers-contrast: high) or (forced-colors: active) styles for users with low vision
3Add aria-invalid, aria-errormessage, and visible error messages for form validation (WCAG 3.3.3)
4Add :focus-visible CSS styles to all interactive elements (WCAG 2.4.7)
5Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
6Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
Oferta por Tiempo Limitado
Las 12 Optimizaciones — Incluidas en Tu Sitio Web Personalizado
We're currently bundling cada optimización de esta auditoría — SEO, AIO, GEO, AEO, Schema.org, accesibilidad WCAG, rendimiento, seguridad y más — directamente en nuestro servicio de Desarrollo de Aplicaciones Web Personalizadas service.
En lugar de corregir problemas después del lanzamiento, los eliminamos desde el inicio. Cada sitio web que construimos se entrega listo para producción con una puntuación de 90+ en las 12 dimensiones de auditoría.