Este informe de auditoría web analiza https://FBI.gov en 12 dimensiones críticas con recomendaciones accionables.
https://FBI.gov
46Deficientede 100
Informe de Auditoría Web
Just a moment...
22 de julio de 2026 28ms respuesta HTTPS Seguro
Resumen Ejecutivo
https://FBI.gov scores 46/100 (F). Strong areas include Security. Priority improvements needed in SEO, AI Readiness, AIO. The site has 0 words, 0 images, and 0 schema blocks. Data confidence: 65%. Sustainability score: 100/100. Focus on the top recommendations below to improve your score.
28ms
Tiempo de Respuesta
0
Conteo de Palabras
0
Imágenes
0
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 (16 chars)
2[SEO] Missing meta description
3[SEO] No H1 heading found
4[SEO] Missing canonical URL
5[SEO] No Open Graph tags found
6[SEO] No Twitter Card tags found
7[SEO] Missing favicon
8[SEO] Thin content (0 words)
9[SEO] Page is set to noindex — search engines will not index this page
10[SEO] Meta refresh redirect detected — harmful for SEO
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] Add exactly one H1 tag with your primary keyword to establish page topic
4[Impact: High | Effort: Low] Add a <link rel="canonical"> tag pointing to the preferred version of this page
5[Impact: High | Effort: Low] Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
6[Impact: Medium | Effort: Low] Add Twitter Card meta tags for better social media previews
7[Impact: Medium | Effort: Medium] Add a favicon for brand recognition in browser tabs and bookmarks
8[Impact: Medium | Effort: Medium] Expand your content to at least 300+ words for better search rankings
9[Impact: Medium | Effort: Medium] Remove noindex from robots meta if this page should appear in search results
10[Impact: Medium | Effort: Medium] Replace meta refresh redirects with proper 301 server-side redirects
11[Impact: High | Effort: Low] Include your primary keyword in the URL slug for improved crawlability and click-through rates
12[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
Análisis Detallado por Categoría
Hallazgos Clave
1HTML lang attribute set to "en-US"
2URL length (16 chars) is within optimal range
3No redirect chain — direct URL resolution
4Primary keyword not in URL — acceptable for homepage/root URLs
Problemas Encontrados
1Title tag is very short (16 chars)
2Missing meta description
3No H1 heading found
4Missing canonical URL
5No Open Graph tags found
6No Twitter Card tags found
7Missing favicon
8Thin content (0 words)
9Page is set to noindex — search engines will not index this page
10Meta refresh redirect detected — harmful for SEO
11Weak E-E-A-T signals (0 indicators)
12No social sharing buttons/widgets detected
13Low OG sharing completeness (0%) — social previews will be poor
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)
3Add exactly one H1 tag with your primary keyword to establish page topic
4Add a <link rel="canonical"> tag pointing to the preferred version of this page
5Add Open Graph tags (og:title, og:description, og:image, og:url, og:type) for social sharing
6Add Twitter Card meta tags for better social media previews
7Add a favicon for brand recognition in browser tabs and bookmarks
8Expand your content to at least 300+ words for better search rankings
9Remove noindex from robots meta if this page should appear in search results
10Replace meta refresh redirects with proper 301 server-side redirects
11Include your primary keyword in the URL slug for improved crawlability and click-through rates
12Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
13Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
14Link to a Contact page — essential trust signal for E-E-A-T and local SEO
15Add social share buttons (Facebook, Twitter/X, LinkedIn, WhatsApp) to encourage content distribution and earn social signals
16Complete your Open Graph tags (og:title, og:description, og:image, og:url, og:type, og:locale) for rich social media previews
Hallazgos Clave
1Excellent server response time: 28ms
2Lean HTML document: 6KB
3No render-blocking scripts detected
4Lean CSS payload (~1KB)
5JavaScript payload (~3KB) is acceptable
6HTTP/3 (QUIC) detected — fastest connection protocol
7CDN detected: Cloudflare — reduces latency for global users
8Brotli compression enabled — best-in-class compression
9Estimated LCP: ~228ms — within Google's "good" threshold (<2.5s)
10Estimated CLS: 0 — within Google's "good" threshold (<0.1)
11Estimated INP: ~50ms — within Google's "good" threshold (<200ms)
12Server-Timing header present — enables performance debugging
Problemas Encontrados
1No font-display property found
2No effective Cache-Control header
3No resource hints found
4No analytics tracking detected — flying blind on user behavior
Recomendaciones para Alcanzar 100%
1Add <link rel="preconnect"> for critical third-party domains to reduce DNS lookup time
2Preload critical resources (fonts, hero images) with <link rel="preload">
3Add font-display: swap to web font declarations to show fallback text while fonts load
4Set Cache-Control headers with appropriate max-age to leverage browser caching
5Add preconnect, prefetch, and preload hints for critical third-party resources and fonts
6Install 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
4Lightweight page (~10KB) — fast on mobile networks
Problemas Encontrados
1No theme-color meta tag
2No web app manifest found
3Missing Apple touch icon
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 <link rel="apple-touch-icon"> for iOS homescreen icons
4Consider implementing a service worker for offline support and faster repeat visits
5Add env(safe-area-inset-*) CSS for proper display on notched/island devices
6Add :active / touch-action CSS for tactile feedback on mobile interactions
Hallazgos Clave
1HTTPS enabled — encrypted connection
2HSTS header present — enforces HTTPS
3Content Security Policy header present
4X-Content-Type-Options: nosniff is set
5X-Frame-Options header prevents clickjacking
6Referrer-Policy set to: same-origin
7Permissions-Policy header restricts browser features
8Cross-Origin-Opener-Policy set
9Cross-Origin-Resource-Policy set
10Cross-Origin-Embedder-Policy set
11Server via CDN proxy (cloudflare) — header added by infrastructure, not application
12HSTS with preload and adequate max-age — eligible for browser preload list
13No cookie security issues detected
14CSP strictness score 55/100 — adequate for modern framework apps that require inline styles/scripts
15CSP uses nonce-based policy — strong inline script protection
16Permissions-Policy restricts 16 browser features (accelerometer, camera, clipboard-read, clipboard-write)
17No server software/technology fingerprints exposed in headers or markup
18No stack traces or sensitive error details exposed in responses
19No raw email addresses exposed in page source
Problemas Encontrados
1No privacy policy detected
2No cookie consent banner detected
3CSP contains 1 unsafe-inline directive(s) — weakens XSS protection
4security.txt file is missing — no standardized channel for reporting vulnerabilities
Recomendaciones para Alcanzar 100%
1Add a privacy policy link — required by GDPR, CCPA, and builds user trust
2Implement a cookie consent banner for GDPR/ePrivacy compliance
3Strengthen CSP: consider nonce-based policies when feasible
4Replace unsafe-inline with nonce-based CSP or hash-based allowlisting for inline scripts/styles
5Add 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]
Hallazgos Clave
1Language declared: en-US
21 ARIA-attributed elements found
3No major HTML nesting or validity issues detected
Problemas Encontrados
1No skip navigation link
2Missing landmarks: nav, footer
3No 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: <nav>, <footer>
3Add :focus-visible styles to all interactive elements for keyboard navigation visibility
Hallazgos Clave
1No AI crawlers blocked via meta tags — content accessible to AI search engines
2robots.txt file found
3robots.txt references 1 sitemap(s) — aids AI crawler discoverability
4Good HTML-to-text ratio (68%) — AI crawlers can extract content efficiently
Problemas Encontrados
1No structured data (Schema.org) found
2No semantic HTML elements detected
3Incomplete social metadata
4No breadcrumb navigation
5No FAQ or Q&A content patterns found
6No sitemap reference found
7No social media links found
8No llms.txt file found — AI models cannot find structured guidance for your site
9Low RAG-friendliness (0/100) — AI systems cannot anchor into specific sections
10No content freshness signals (dateModified, datePublished, <time> elements)
11High JS content ratio (60%) — most content may require JavaScript execution
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
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
9Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
10Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
11Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
12Add id attributes to all H2/H3 headings and wrap content sections in <section id="..."> for vector-embeddable, RAG-friendly content chunks
13Add dateModified and datePublished meta tags and use <time datetime="..."> elements — AI models prefer fresh, timestamped content
14Reduce JavaScript dependence for content rendering — AI crawlers may not execute JS and miss your content
Problemas Encontrados
1Very thin content (0 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Low semantic markup ratio — 2 divs vs 0 semantic elements
5Weak E-E-A-T schema signals
6No external citations/references — reduces credibility for AI models
7No author or expertise signals
8No clear call-to-action elements detected
9No CTA above the fold
10Insufficient trust signals for conversion optimization
11No social proof elements
12No clear value proposition in headings
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
8Add outbound citations to authoritative sources to demonstrate research depth and increase AI citation worthiness
9Include specific statistics, percentages, and data points that AI models can extract and cite in responses
10Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
11Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
12Add prominent CTAs with action-oriented text ("Get Started", "Book a Call", "Try Free") — every page should guide users toward conversion
13Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
14Add trust signals: testimonials, trust badges, guarantees, client logos, and privacy indicators to boost conversion confidence
15Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
16Your H1 or hero section should clearly state your unique value proposition — what you offer, for whom, and why it matters
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
7No 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
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
9Add bidirectional hreflang tags with x-default to help AI engines serve the correct language variant
10Add original data visualizations, charts, or data tables — generative engines cite pages with unique, first-party data
11Include first-hand insights using phrases like "our research found" or "based on our analysis" to demonstrate original expertise
Problemas Encontrados
1No FAQ content or schema
2Content not optimized for featured snippets
3No Speakable schema for voice search
4No breadcrumb navigation
5Few concise answer paragraphs for snippet extraction
6No 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
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: 17847400
2Phone number(s) visible: 17847400
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%
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
6Add 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
1Relative units (rem/em/clamp) detected — supports text resizing
2Page language declared — aids assistive technology
3All ARIA roles are valid
4Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
Problemas Encontrados
1No prefers-reduced-motion support
2No high contrast mode support
3Links may not be distinguishable from surrounding text
4No semantic HTML5 elements detected
5No focus styles 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
3Ensure links have visible underlines or other non-color visual indicators (WCAG 1.4.1)
4Use semantic elements (main, nav, article, section, aside, header, footer) for WCAG-compliant page structure
5Add :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.