Este informe de auditoría web analiza https://www.paez.law/lgbtq en 12 dimensiones críticas con recomendaciones accionables.
https://www.paez.law/lgbtq
45Deficientede 100
Informe de Auditoría Web
Abogado de Inmigracion LGBTQIA+ | Paez Law | United States
1 de agosto de 2026 349ms respuesta HTTPS Seguro
Resumen Ejecutivo
https://www.paez.law/lgbtq scores 45/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 810 words, 34 images, and 0 schema blocks. Data confidence: 85%. Sustainability score: 75/100. Focus on the top recommendations below to improve your score.
349ms
Tiempo de Respuesta
810
Conteo de Palabras
34
Imágenes
27
Enlaces
Vista Previa del Sitio
Visitar SitioCargando vista previa…
Desglose de Puntuación — 12 Dimensiones
Problemas Principales a Solucionar
1[SEO] Meta description is short (73 chars)
2[SEO] Multiple H1 tags found (4)
3[SEO] Heading hierarchy gaps: h2 → h6 (skips h3), h2 → h6 (skips h3), h1 → h5 (skips h2)
4[SEO] 6 external links missing recommended rel attributes
5[SEO] 9 dofollow external links — slightly above optimal range
6[SEO] Primary keyword "abogado inmigracion lgbtqia" not found in H1
7[SEO] Primary keyword missing from first paragraph
8[SEO] Weak E-E-A-T signals (2 indicators)
9[SEO] Low readability score (15 Flesch) — content is hard to read
10[SEO] Missing og:locale tag — social platforms may guess language/region
Recomendaciones Principales
1[Impact: High | Effort: Low] Expand your meta description to 140–160 characters for better SERP visibility
2[Impact: High | Effort: Low] Consolidate to a single H1 tag — use H2–H6 for subtopics
3[Impact: High | Effort: Low] Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
4[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" to external links pointing to unaffiliated sites
5[Impact: Medium | Effort: Medium] Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
6[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
7[Impact: High | Effort: Low] Include your primary keyword naturally in the first paragraph to establish topical relevance early
8[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
9[Impact: High | Effort: Medium] Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
10[Impact: High | Effort: Medium] Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
11[Impact: High | Effort: Medium] Link to a Contact page — essential trust signal for E-E-A-T and local SEO
12[Impact: Medium | Effort: Medium] Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
Análisis Detallado por Categoría
Hallazgos Clave
1Title tag is 58 characters — within optimal 50–60 range (Google 2025-2026)
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
716 internal links help establish site architecture
89 external links provide reference signals
9Content length of 810 words is adequate
1027 total links — within recommended range
11URL length (26 chars) is within optimal range
12No redirect chain — direct URL resolution
13Healthy internal link ratio: 59% of links are internal
14Good anchor text diversity: 100% unique anchor texts
15Primary keyword not in URL — acceptable for homepage/root URLs
16OG image dimensions ≥1200×630px — optimal for all platforms
17Twitter card uses summary_large_image — maximum visual impact
18Internal link density (19.8/1k words) — above average but acceptable for navigation-heavy pages
19Strong entity salience: Estados Unidos, Luis Enrique, New York City (score: 56)
Problemas Encontrados
1Meta description is short (73 chars)
2Multiple H1 tags found (4)
3Heading hierarchy gaps: h2 → h6 (skips h3), h2 → h6 (skips h3), h1 → h5 (skips h2)
46 external links missing recommended rel attributes
59 dofollow external links — slightly above optimal range
6Primary keyword "abogado inmigracion lgbtqia" not found in H1
7Primary keyword missing from first paragraph
8Weak E-E-A-T signals (2 indicators)
9Low readability score (15 Flesch) — content is hard to read
10Missing og:locale tag — social platforms may guess language/region
11Primary keyword "abogado inmigracion lgbtqia" not found in body content
12No social sharing buttons/widgets detected
Recomendaciones para Alcanzar 100%
1Expand your meta description to 140–160 characters for better SERP visibility
2Consolidate to a single H1 tag — use H2–H6 for subtopics
3Fix heading hierarchy to use sequential levels (H1 → H2 → H3) without skipping
4Add rel="nofollow noopener noreferrer" to external links pointing to unaffiliated sites
5Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
6Include your primary keyword in the H1 heading for strongest on-page SEO signal
7Include your primary keyword naturally in the first paragraph to establish topical relevance early
8Include your primary keyword in the URL slug for improved crawlability and click-through rates
9Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
10Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
11Link to a Contact page — essential trust signal for E-E-A-T and local SEO
12Significantly simplify your content — aim for 60+ Flesch Reading Ease with shorter sentences and simpler vocabulary
13Add <meta property="og:locale" content="en_US"> (or your locale) for precise language targeting in social shares
14Convert your OG image to WebP format for faster social media loading (1200×630px recommended)
15Add <meta property="article:published_time"> for content freshness signals in social shares
16Add <meta property="article:modified_time"> to signal content freshness
17Include your primary keyword naturally throughout the content body — aim for 0.5–2.5% density
18Add TL;DR summaries or definition-style opening paragraphs ("X is...") for zero-click/featured snippet capture
19Add engagement signals: related posts section, "Read next" links, and table of contents to increase dwell time
20Add social share buttons (Facebook, Twitter/X, LinkedIn, WhatsApp) to encourage content distribution and earn social signals
21OG sharing completeness at 83% — add missing tags for better social previews
Hallazgos Clave
1Excellent server response time: 349ms
25/34 images use lazy loading
3Responsive images with srcset detected
4font-display property detected — reduces invisible text during font loading
56 async and 2 deferred scripts
6Cache-Control header with max-age is set
7HTTP/3 (QUIC) detected — fastest connection protocol
8CDN detected: CDN (unidentified) — reduces latency for global users
9Brotli compression enabled — best-in-class compression
10Estimated LCP: ~1049ms — within Google's "good" threshold (<2.5s)
11Server-Timing header present — enables performance debugging
Problemas Encontrados
1Very large HTML: 881KB
23 render-blocking scripts slow down initial paint
3No WebP or AVIF image formats found
4Only 14/34 images have width/height attributes
529 inline <style> blocks
648 inline scripts
7Moderate CSS payload (~296KB)
8Heavy JavaScript payload (~1017KB across 11 files)
911 third-party scripts from 2 domains — significant performance impact
1078 font files loaded — excessive font weight
11Potential long-task scripts: Inline script (~16KB), Inline script (~54KB), Inline script (~10KB)
12High estimated CLS: 0.3 — exceeds Google's 0.25 threshold
13Estimated INP: ~223ms — needs improvement (goal: <200ms)
14Web fonts loaded without preload — causes FOIT/FOUT flash
15No analytics tracking detected — flying blind on user behavior
Recomendaciones para Alcanzar 100%
1Critical: HTML is over 500KB — implement code splitting, lazy loading, and remove unnecessary markup
2Convert all non-critical scripts to async/defer to eliminate render-blocking resources
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
8Move inline scripts to external files with defer attributes
9Consider purging unused CSS and using critical CSS extraction to reduce render-blocking stylesheets
10Reduce JavaScript with code splitting, tree shaking, and lazy loading. Target <500KB total JS for optimal performance
11Audit third-party scripts — defer non-critical ones and remove unused trackers/widgets to reduce main thread blocking
12Limit web fonts to 2–3 families with subset character ranges to reduce font loading impact
13Preload your primary font with <link rel="preload" as="font" crossorigin> for faster first contentful paint
14Review large inline/external scripts that may block the main thread. Use web workers or break into smaller async chunks
15Fix CLS: add explicit width/height to all images and iframes, preload fonts, avoid injecting content above existing content
16Improve INP: break up long JavaScript tasks, use web workers for heavy computation, debounce input handlers
17Add <link rel="preload" as="font" crossorigin> for your primary font files to eliminate flash of invisible/unstyled text
18Install Google Analytics 4 (GA4) with Google Tag Manager immediately — analytics is essential for measuring SEO and marketing ROI
Hallazgos Clave
1Viewport meta tag present: width=device-width, initial-scale=1
2HTML5 doctype declared
3Character encoding declared
4Apple touch icons present
5Service worker detected — offline capability possible
6Responsive images via srcset serve appropriate sizes per device
75 images with lazy loading benefit mobile data users
8Touch feedback CSS detected (active states or touch-action)
94 internationalization signals detected (hreflang, lang, dir, locale meta)
Problemas Encontrados
1No theme-color meta tag
2No web app manifest found
3Only 2 manifest icon size(s) — recommend at least 4 (192, 384, 512, maskable)
4Estimated page weight ~4004KB — heavy for mobile data plans
Recomendaciones para Alcanzar 100%
1Add <meta name="theme-color"> for browser chrome styling on mobile
2Create a manifest.json for PWA capabilities and add-to-homescreen support
3Add multiple icon sizes (192x192, 384x384, 512x512, plus maskable) to your manifest for cross-device support
4Add env(safe-area-inset-*) CSS for proper display on notched/island devices
5Reduce 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
4Privacy policy link detected
5Rate limiting recommended for form endpoints
6No stack traces or sensitive error details exposed in responses
7No obvious secret/API-key patterns exposed in page source
8Client-side library inventory (SBOM): React 18.3.1
911 script resource(s) catalogued for software-composition review
10No common sensitive paths (.git, .env, server-status, …) were publicly accessible
Problemas Encontrados
1Missing Content-Security-Policy header
2Missing X-Frame-Options header
3Missing Referrer-Policy header
4Missing Permissions-Policy header
5Server header exposes technology: Pepyaka
66 external links missing rel="noopener noreferrer" — security risk
7HSTS header present but missing preload directive
8Cookie security issues: missing Secure flag; missing HttpOnly flag; missing SameSite attribute
9No cookie consent banner detected
10No Subresource Integrity (SRI) on external scripts
11Server technology disclosed via response headers/markup: Server: Pepyaka; Generator meta tag: Wix.com Website Builder
12security.txt file is missing — no standardized channel for reporting vulnerabilities
132 email address(es) exposed in page source (e.g. [email protected], [email protected]) — can be harvested for spam/phishing
14HTML comments leak potentially sensitive hints: credential reference
15A private/internal IP address (RFC 1918) is disclosed in the page source — reveals internal network topology
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
11Implement a cookie consent banner for GDPR/ePrivacy compliance
12Add integrity attributes to external scripts/stylesheets to prevent supply-chain attacks
13Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
14Remove or obfuscate technology-revealing headers (Server, X-Powered-By, X-AspNet-Version) and the generator meta tag to reduce your attack surface
15Add an RFC 9116 security.txt at /.well-known/security.txt with Contact and Expires fields so researchers can responsibly report security issues [Impact: Low | Effort: Low]
16If these emails are not meant to be public, obfuscate them or replace with a contact form; for intentional contact addresses this is informational only [Impact: Info | Effort: Low]
17Strip developer comments (TODOs, credentials, internal URLs, debug notes) from production HTML during your build [Impact: Low | Effort: Low]
18Remove references to internal hostnames/IP addresses from public responses [Impact: Medium | Effort: Low]
Hallazgos Clave
1Language declared: en
2All 34 images have alt attributes
3All 23 buttons have accessible labels
4Rich ARIA implementation: 54 elements with ARIA attributes
5Focus styles detected for keyboard navigation
6No major HTML nesting or validity issues detected
Problemas Encontrados
1No skip navigation link
2Missing landmarks: nav
31 form(s) missing proper labels
4Heading hierarchy has gaps — confusing for screen readers
520 images missing explicit dimensions — causes layout shifts for screen reader users
61 video(s) missing captions/subtitles
79 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 semantic landmark elements: <nav>
3Add <label> elements associated with every form input via for/id attributes
4Set explicit width and height (or CSS aspect-ratio) on all images to prevent layout shifts that disorient assistive technology users
5Add <track kind="captions"> or <track kind="subtitles"> to all video elements (WCAG 1.2.2)
6Ensure all element IDs are unique — duplicate IDs break form labels, ARIA relationships, and fragment navigation
Hallazgos Clave
1Hreflang tags: x-default, en-us
2Strong semantic markup: header, main, section, footer
3Complete social metadata (OG + Twitter Card)
4Sitemap reference detected
5Social presence signals: facebook, twitter, instagram
61 call-to-action elements detected
7No AI crawlers blocked via meta tags — content accessible to AI search engines
8robots.txt file found
9robots.txt references 1 sitemap(s) — aids AI crawler discoverability
10llms.txt detected (score: 73/100, quality: comprehensive)
11llms.txt has proper title and description block
12llms.txt has 13 well-organized sections
13llms.txt references 4 URLs for AI navigation
14llms.txt includes service/product catalog
15llms.txt uses proper Markdown formatting for machine readability
16llms.txt uses canonical domain in URLs
17llms.txt includes citation/attribution guidance
18llms.txt includes version/date for freshness tracking
19High RAG-friendliness (100/100): 0 headings with IDs, 129 section anchors
20Content provenance signals detected (citations with sources, attributed claims)
Problemas Encontrados
1No structured data (Schema.org) found
2No breadcrumb navigation
3No FAQ or Q&A content patterns found
4No llms-full.txt companion file found
5llms.txt is not referenced in HTML
6No content freshness signals (dateModified, datePublished, <time> elements)
7High JS content ratio (53%) — most content may require JavaScript execution
Recomendaciones para Alcanzar 100%
1Implement JSON-LD structured data — start with Organization, BreadcrumbList, and page-specific types
2Add breadcrumb navigation with BreadcrumbList schema for better site hierarchy signals
3Add an FAQ section with FAQPage schema to increase chances of AI engine citations
4Use <strong> and <em> tags to highlight key entities, concepts, and terms
5Create /llms-full.txt with detailed documentation — services, pricing, case studies, technical specs — for AI models that want depth
6Add more key page URLs to llms.txt — aim for 8-15 covering all major sections of your site
7Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your <head> for discoverability
8Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
9Reduce JavaScript dependence for content rendering — AI crawlers may not execute JS and miss your content
Hallazgos Clave
1Moderate content depth (810 words)
2Structured content: 12 lists, 0 tables — easily parsed by AI
3Good paragraph length for readability and AI parsing
43 external citation(s)
51 call-to-action element(s) detected
6Good form usability score: 85/100
7Trust signals present: Guarantee, HTTPS Security
8Clear value proposition detected in heading elements
Problemas Encontrados
1No structured Q&A content
2Weak entity markup — few terms emphasized
3Low semantic markup ratio — 357 divs vs 10 semantic elements
4Weak E-E-A-T schema signals
5No author or expertise signals
6No CTA above the fold
7No social proof elements
Recomendaciones para Alcanzar 100%
1Add FAQ or Q&A sections — AI models heavily rely on question-answer patterns for training data
2Use <strong>, <em>, and <mark> to highlight key entities, concepts, and brand terms for AI comprehension
3Replace generic <div> wrappers with semantic elements (article, section, aside, figure) for AI clarity
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
112 lists provide scannable, AI-friendly content
2Hreflang includes self-referencing tag
3x-default hreflang fallback present
Problemas Encontrados
1No direct Q&A patterns for generative AI extraction
2No data tables for AI comparison extraction
3Insufficient structured data for generative engine context
4No statistics or data points in substantial content
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
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
5Include unique statistics, expert quotes, and original insights that generative AI would want to cite
6Add multiple schema types (Article, FAQ, HowTo) to help generative engines contextualize your content
7Include specific statistics, percentages, and numerical data — generative engines prefer content with verifiable data points
8Add original data visualizations, charts, or data tables — generative engines cite pages with unique, first-party data
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
212 lists provide scannable answers for People Also Ask
3Video content detected — supports multimedia answer results
421 concise answer-length paragraphs (10–50 words) — ideal for snippet extraction
5Content 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
4No breadcrumb navigation
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 breadcrumb navigation with BreadcrumbList schema for better content hierarchy signals
6Include direct definitional statements like "X is..." or "X refers to..." — answer engines extract these as zero-click results
Hallazgos Clave
1NAP information detected: phone: 17853539525, email: [email protected]
2Phone number(s) visible: 17853539525, 7007184
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
Problemas Encontrados
1No Schema.org structured data found
2Missing high-impact schema types: Organization, WebSite
Recomendaciones para Alcanzar 100%
1Implement JSON-LD structured data immediately — start with Organization, WebSite, and BreadcrumbList
2Priority schema types to add: Organization, WebSite — these have the highest SEO impact for your page type
Hallazgos Clave
1prefers-reduced-motion support detected — respects user motion preferences
2High contrast / forced-colors mode supported
3Links are visually distinguishable (underline or decoration detected)
4Form error/validation feedback detected
51 media element(s) without autoplay
6Relative units (rem/em/clamp) detected — supports text resizing
7Focus styles detected for keyboard navigation visibility
8Page language declared — aids assistive technology
9All ARIA roles are valid
10Form error identification mechanisms present (WCAG 3.3.1)
11Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
122 ARIA live regions for dynamic content announcements
13prefers-reduced-motion detected but enforcement unclear
Problemas Encontrados
1Low semantic-to-div ratio — 357 divs vs 10 semantic elements
211 elements with tabindex="-1" — may hide content from keyboard users
33 heading level skip(s) — confuses screen reader navigation
4Multiple fixed/sticky elements may obscure focused content (WCAG 2.4.11)
Recomendaciones para Alcanzar 100%
1Replace more generic <div> elements with semantic HTML5 tags for better screen reader navigation
2Review elements with tabindex="-1" — ensure important interactive elements remain keyboard-accessible
3Use sequential heading levels (H1→H2→H3) without skipping — screen reader users navigate by heading hierarchy (WCAG 1.3.1)
4Ensure sticky headers/footers do not fully obscure the keyboard focus indicator. Use scroll-padding-top or ensure focus remains visible under overlapping elements (WCAG 2.4.11 AA)
5Ensure prefers-reduced-motion actually disables animations (set animation: none and transition: none in the media query)
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.