Este informe de auditoría web analiza https://TyeshaLevin.com en 12 dimensiones críticas con recomendaciones accionables.
https://TyeshaLevin.com
67Necesita Mejorasde 100
Informe de Auditoría Web
@tyeshalevin | Merchant services, EA Home - Think Energy
20 de mayo de 2026 333ms respuesta HTTPS Seguro
Resumen Ejecutivo
https://TyeshaLevin.com scores 67/100 (D+). Strong areas include Performance, Mobile. Priority improvements needed in Security, AI Readiness, AIO. The site has 1 words, 0 images, and 1 schema blocks. Focus on the top recommendations below to improve your score.
333ms
Tiempo de Respuesta
1
Conteo de Palabras
0
Imágenes
0
Enlaces
Desglose de Puntuación — 12 Dimensiones
Problemas Principales a Solucionar
1[SEO] Meta description is short (108 chars)
2[SEO] No H1 heading found
3[SEO] Thin content (1 words)
4[Performance] No font-display property found
5[Security] Missing Strict-Transport-Security header
6[Security] Missing X-Content-Type-Options header
7[Security] Missing Referrer-Policy header
8[Security] Missing Permissions-Policy header
9[Security] Server header exposes technology: Google Frontend
10[Accessibility] No skip navigation link
Recomendaciones Principales
1Expand your meta description to 120–160 characters for better SERP visibility
2Add exactly one H1 tag with your primary keyword to establish page topic
3Expand your content to at least 300+ words for better search rankings
4Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
5Add font-display: swap to web font declarations to show fallback text while fonts load
6Add Strict-Transport-Security header with max-age=63072000; includeSubDomains; preload
7Add X-Content-Type-Options: nosniff to prevent MIME type sniffing
8Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
9Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
10Add Cross-Origin-Opener-Policy: same-origin-allow-popups
11Add Cross-Origin-Resource-Policy: cross-origin
12Remove or obfuscate the Server header to avoid exposing your technology stack
Análisis Detallado por Categoría
Hallazgos Clave
1Title tag is 56 characters — within optimal 30–60 range
2Canonical URL is set and matches the page URL
3Complete Open Graph tags (title, description, image, url, type)
4Complete Twitter Card tags present
5HTML lang attribute set to "en"
6Favicon present
Problemas Encontrados
1Meta description is short (108 chars)
2No H1 heading found
3Thin content (1 words)
Recomendaciones para Alcanzar 100%
1Expand your meta description to 120–160 characters for better SERP visibility
2Add exactly one H1 tag with your primary keyword to establish page topic
3Expand your content to at least 300+ words for better search rankings
Hallazgos Clave
1Excellent server response time: 333ms
2Lean HTML document: 77KB
31 framework-managed script(s) — optimized by build pipeline
4Preloaded resources: script
514 async and 0 deferred scripts
6Cache-Control header with max-age is set
712 inline scripts (framework hydration/data — standard for SSR apps)
Problemas Encontrados
1No font-display property found
Recomendaciones para Alcanzar 100%
1Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
2Add font-display: swap to web font declarations to show fallback text while fonts load
Hallazgos Clave
1Viewport meta tag present: width=device-width, initial-scale=1, maximum-scale=1, viewport-fit=contain, user
2HTML5 doctype declared
3Character encoding declared
4Theme color meta tag set for mobile browsers
5Web app manifest detected — PWA-ready
6Apple touch icons present
Recomendaciones para Alcanzar 100%
1Consider implementing a service worker for offline support and faster repeat visits
Hallazgos Clave
1HTTPS enabled — encrypted connection
2Content Security Policy header present
3X-Frame-Options header prevents clickjacking
4X-Powered-By: Next.js — framework header, minimal risk
Problemas Encontrados
1Missing Strict-Transport-Security header
2Missing X-Content-Type-Options header
3Missing Referrer-Policy header
4Missing Permissions-Policy header
5Server header exposes technology: Google Frontend
Recomendaciones para Alcanzar 100%
1Add Strict-Transport-Security header with max-age=63072000; includeSubDomains; preload
2Add X-Content-Type-Options: nosniff to prevent MIME type sniffing
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
Hallazgos Clave
1Language declared: en
Problemas Encontrados
1No skip navigation link
2Missing landmarks: main, nav, footer
3No ARIA attributes detected
4No focus styles detected
Recomendaciones para Alcanzar 100%
1Add a "Skip to main content" link as the first focusable element for keyboard users
2Add semantic landmark elements: <main>, <nav>, <footer>
3Add ARIA attributes to interactive elements for better screen reader support
4Add :focus-visible styles to all interactive elements for keyboard navigation visibility
Hallazgos Clave
11 schema block(s): ProfilePage
2Complete social metadata (OG + Twitter Card)
Problemas Encontrados
1No semantic HTML elements detected
2No breadcrumb navigation
3No FAQ or Q&A content patterns found
4No sitemap reference found
5No social media links found
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
3Replace generic divs with semantic HTML5 elements to help AI models understand your content structure
4Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
5Add an FAQ section with FAQPage schema to increase chances of AI engine citations
6Create and reference an XML sitemap for AI crawler discoverability
7Use <strong> and <em> tags to highlight key entities, concepts, and terms
8Add links to your social media profiles to strengthen brand entity signals
Problemas Encontrados
1Very thin content (1 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Low semantic markup ratio — 3 divs vs 0 semantic elements
5Weak E-E-A-T schema signals
Recomendaciones para Alcanzar 100%
1AI models value comprehensive, authoritative content — aim for 1000–2000+ words covering the topic thoroughly
2Add FAQ or Q&A sections — AI models heavily rely on question-answer patterns for training data
3Use <strong>, <em>, and <mark> to highlight key entities, concepts, and brand terms for AI comprehension
4Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
5Add structured content (lists, comparison tables) that AI models can easily extract and reference
6Add Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
7Add Speakable schema markup to help voice assistants identify the most important content
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
6thin content — may not provide enough depth for AI engines
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
7Include unique statistics, expert quotes, and original insights that generative AI would want to cite
8Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
Problemas Encontrados
1No FAQ content or schema
2Content not optimized for featured snippets
3No Speakable schema for voice search
4No breadcrumb navigation
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 breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
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
Hallazgos Clave
1NAP information detected: phone: 17788012631, email: [email protected]
2Phone number(s) visible: 17788012631, 0108892
3Email address found: [email protected]
Problemas Encontrados
1No LocalBusiness structured data
2No Google Maps embed
3No address microdata
4No geo meta tags
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
Hallazgos Clave
11 JSON-LD block(s) with types: ProfilePage
2No schema validity issues detected
Problemas Encontrados
1Only basic schema implementation
Recomendaciones para Alcanzar 100%
1Expand structured data with more specific schema types relevant to your content
2Add BreadcrumbList schema for site hierarchy
3Add FAQPage schema to FAQ content
4Consider adding HowTo schema for instructional content
5Add more schema types — diverse structured data improves AI and search engine understanding
Hallazgos Clave
1prefers-reduced-motion support detected — respects user motion preferences
2High contrast / forced-colors mode supported
3Relative units (rem/em/clamp) detected — supports text resizing
4Page language declared — aids assistive technology
Problemas Encontrados
1Links may not be distinguishable from surrounding text
2No semantic HTML5 elements detected
3No focus styles detected
Recomendaciones para Alcanzar 100%
1Ensure links have visible underlines or other non-color visual indicators (WCAG 1.4.1)
2Use semantic elements (main, nav, article, section, aside, header, footer) for WCAG-compliant page structure
3Add :focus-visible CSS styles to all interactive elements (WCAG 2.4.7)
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.