Este informe de auditoría web analiza https://myrtlejscott.com/ en 12 dimensiones críticas con recomendaciones accionables.
https://myrtlejscott.com/
67Necesita Mejorasde 100
Informe de Auditoría Web
Mental Health Therapy - Myrtle J Scott-Franklin Network LLC
21 de mayo de 2026 151ms respuesta HTTPS Seguro
Resumen Ejecutivo
https://myrtlejscott.com/ scores 67/100 (D+). Strong areas include Mobile. Priority improvements needed in Performance, AI Readiness, AIO. The site has 453 words, 6 images, and 0 schema blocks. Focus on the top recommendations below to improve your score.
151ms
Tiempo de Respuesta
453
Conteo de Palabras
6
Imágenes
10
Enlaces
Historial de Puntuación
Escaneo actual2 escaneos registrados↑ 14 pts desde el primer escaneo
Desglose de Puntuación — 12 Dimensiones
Problemas Principales a Solucionar
1[SEO] Heading hierarchy gaps: h2 → h4 (skips h3), h2 → h4 (skips h3), h2 → h4 (skips h3)
2[SEO] Missing canonical URL
3[SEO] Missing favicon
4[Performance] 3 render-blocking scripts slow down initial paint
5[Performance] No lazy loading on images
6[Performance] No WebP or AVIF image formats found
7[Performance] Only 0/6 images have width/height attributes
8[Performance] 14 inline <style> blocks
9[Security] Missing X-Content-Type-Options header
10[Security] Missing X-Frame-Options header
Recomendaciones Principales
1Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
2Add a <link rel="canonical"> tag pointing to the preferred version of this page
3Add a favicon for brand recognition in browser tabs and bookmarks
4Convert all non-critical scripts to async/defer to eliminate render-blocking resources
5Add loading="lazy" to below-the-fold images to improve initial page load
6Convert images to WebP or AVIF format for 30–50% file size reduction
7Add explicit width and height to all images to prevent Cumulative Layout Shift (CLS)
8Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
9Preload critical resources (fonts, hero images) with <link rel="preload">
10Extract inline styles into external CSS files for better caching and maintainability
11Add X-Content-Type-Options: nosniff to prevent MIME type sniffing
12Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
Análisis Detallado por Categoría
Hallazgos Clave
1Title tag is 59 characters — within optimal 30–60 range
2Meta description is 157 characters — within optimal 120–160 range
3Single H1 tag present: "Welcome to Myrtle J Scott-Franklin Network LLC"
4Complete Open Graph tags (title, description, image, url, type)
5Complete Twitter Card tags present
6HTML lang attribute set to "en-US"
77 internal links help establish site architecture
83 external links provide reference signals
9Content length of 453 words is adequate
Problemas Encontrados
1Heading hierarchy gaps: h2 → h4 (skips h3), h2 → h4 (skips h3), h2 → h4 (skips h3)
2Missing canonical URL
3Missing favicon
Recomendaciones para Alcanzar 100%
1Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
2Add a <link rel="canonical"> tag pointing to the preferred version of this page
3Add a favicon for brand recognition in browser tabs and bookmarks
Hallazgos Clave
1Excellent server response time: 151ms
2HTML size is 121KB — acceptable
3Responsive images with srcset detected
4font-display property detected — reduces invisible text during font loading
50 async and 1 deferred scripts
6Cache-Control header with max-age is set
Problemas Encontrados
13 render-blocking scripts slow down initial paint
2No lazy loading on images
3No WebP or AVIF image formats found
4Only 0/6 images have width/height attributes
514 inline <style> blocks
Recomendaciones para Alcanzar 100%
1Convert all non-critical scripts to async/defer to eliminate render-blocking resources
2Add loading="lazy" to below-the-fold images to improve initial page load
3Convert images to WebP or AVIF format for 30–50% file size reduction
4Add explicit width and height to all images to prevent Cumulative Layout Shift (CLS)
5Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
6Preload critical resources (fonts, hero images) with <link rel="preload">
7Extract inline styles into external CSS files for better caching and maintainability
Hallazgos Clave
1Viewport meta tag present: width=device-width, initial-scale=1
2HTML5 doctype declared
3Character encoding declared
4Theme color meta tag set for mobile browsers
5Web app manifest detected — PWA-ready
6Apple touch icons present
7Service worker detected — offline capability possible
8Responsive images via srcset serve appropriate sizes per device
Hallazgos Clave
1HTTPS enabled — encrypted connection
2HSTS header present — enforces HTTPS
3Content Security Policy header present
Problemas Encontrados
1Missing X-Content-Type-Options header
2Missing X-Frame-Options header
3Missing Referrer-Policy header
4Missing Permissions-Policy header
5Server header exposes technology: DPS/2.0.0+sha-d87240b
Recomendaciones para Alcanzar 100%
1Add X-Content-Type-Options: nosniff to prevent MIME type sniffing
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
Hallazgos Clave
1Language declared: en-US
2All key landmarks present (main, nav, footer)
3All 6 buttons have accessible labels
4Rich ARIA implementation: 70 elements with ARIA attributes
5Focus styles detected for keyboard navigation
Problemas Encontrados
1No skip navigation link
26 of 6 images (100%) missing alt text
31 form(s) missing proper labels
4Heading hierarchy has gaps — confusing for screen readers
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
Hallazgos Clave
1Some semantic elements: section, nav
2Complete social metadata (OG + Twitter Card)
32 call-to-action elements detected
Problemas Encontrados
1No structured data (Schema.org) found
2No breadcrumb navigation
3No FAQ or Q&A content patterns found
4No sitemap reference found
5No social media links found
Recomendaciones para Alcanzar 100%
1Implement JSON-LD structured data — start with Organization, BreadcrumbList, and page-specific types
2Add hreflang tags if your site serves multiple languages or regions
3Increase use of semantic HTML5 elements (article, section, aside, figure) for better AI understanding
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
Hallazgos Clave
1Structured content: 1 lists, 1 tables — easily parsed by AI
2Good paragraph length for readability and AI parsing
Problemas Encontrados
1Content may be too thin for AI optimization (453 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Low semantic markup ratio — 144 divs vs 9 semantic elements
5Weak E-E-A-T schema signals
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
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 Person, Article, and Review schemas to demonstrate expertise, experience, authoritativeness, and trustworthiness
6Add Speakable schema markup to help voice assistants identify the most important content
Hallazgos Clave
11 comparison/data table(s) — highly extractable by AI
Problemas Encontrados
1No direct Q&A patterns for generative AI extraction
2Few or no lists
3Content too thin for AI citation value
4Insufficient structured data for generative engine context
Recomendaciones para Alcanzar 100%
1Structure content with clear questions as headings (H2/H3) followed by concise, definitive answers in the first paragraph
2Use numbered and bulleted lists for step-by-step content — generative engines prefer structured, scannable formats
3Include how-to or step-by-step instructional content for generative AI answer inclusion
4Consider using <dl>/<dt>/<dd> definition lists for key terms and concepts
5Generative engines cite pages with substantial, authoritative content — aim for 1000+ words with unique insights
6Include unique statistics, expert quotes, and original insights that generative AI would want to cite
7Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
Hallazgos Clave
1Short paragraphs are well-suited for answer extraction
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: 9199999999
2Phone number(s) visible: 9199999999, 630-4776
Problemas Encontrados
1No LocalBusiness structured data
2No Google Maps embed
3No address microdata
4No geo meta tags
Recomendaciones para Alcanzar 100%
1Consider displaying a business email for direct contact signals
2Add LocalBusiness (or specific subtype like ProfessionalService) JSON-LD schema with name, address, phone, hours, and geo coordinates
3Add an embedded Google Map to your contact or about page for local search signals
4Add PostalAddress schema or itemprop="address" microdata to your address elements
5Add geo.region, geo.placename, and geo.position meta tags for geographic targeting
Problemas Encontrados
1No Schema.org structured data found
Recomendaciones para Alcanzar 100%
1Implement JSON-LD structured data immediately — start with Organization, WebSite, and BreadcrumbList
Hallazgos Clave
1Links are visually distinguishable (underline or decoration detected)
2Focus styles detected for keyboard navigation visibility
3Page language declared — aids assistive technology
Problemas Encontrados
1No prefers-reduced-motion support
2No high contrast mode support
3No error suggestion mechanisms detected in forms
4No relative units for text sizing detected
5Low semantic-to-div ratio — 144 divs vs 9 semantic elements
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)
4Use rem, em, or clamp() for font sizes to allow users to resize text up to 200% without loss of content (WCAG 1.4.4)
5Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
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.