This website audit report analyzes http://Florida.gov across 12 critical dimensions with actionable recommendations.
http://Florida.gov
36Poorout of 100
Website Audit Report
- MyFlorida
September 7, 2026 at 1:52 PM EDT 991ms response HTTPS Secure302 Redirect
Executive Summary
http://Florida.gov scores 36/100 (F). Priority improvements needed in SEO, Performance, Security. The site has 36 words, 1 images, and 0 schema blocks. Data confidence: 70%. Sustainability score: 100/100. Focus on the top recommendations below to improve your score.
991ms
Response Time
36
Word Count
1
Images
10
Links
Website Preview
Visit SiteHTTP → HTTPS Redirect
302 Temporaryredirect detected — your site correctly forces secure connections.
Loading preview…
Score Breakdown — 12 Dimensions
Top Issues to Fix
1[SEO] Title tag is very short (11 chars)
2[SEO] Missing meta description
3[SEO] Missing canonical URL
4[SEO] Missing OG tags: og:url
5[SEO] Missing Twitter tags: twitter:card, twitter:title, twitter:description, twitter:image
6[SEO] Thin content (36 words)
7[SEO] 7 external links missing recommended rel attributes
8[SEO] SPA framework detected (nextjs) with thin initial HTML content — search engines may not index all content
9[SEO] Title and H1 share no keywords — misaligned topic signals
10[SEO] 7 dofollow external links — slightly above optimal range
Top Recommendations
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 a <link rel="canonical"> tag pointing to the preferred version of this page
4[Impact: Medium | Effort: Medium] Add missing Open Graph tags: og:url
5[Impact: Medium | Effort: Medium] Expand your content to at least 300+ words for better search rankings
6[Impact: Medium | Effort: Medium] Add rel="nofollow noopener noreferrer" to external links pointing to unaffiliated sites
7[Impact: Medium | Effort: Medium] Ensure your SPA uses server-side rendering (SSR) or static generation so crawlers see full content without JavaScript execution
8[Impact: High | Effort: Low] Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
9[Impact: Medium | Effort: Medium] Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
10[Impact: High | Effort: Low] Include your primary keyword in the H1 heading for strongest on-page SEO signal
11[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
12[Impact: High | Effort: Medium] Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
Detailed Category Analysis
Key Findings
1Single H1 tag present: "The Official Page for Sunshine State Government"
2HTML lang attribute set to "en"
3Favicon present
47 external links provide reference signals
510 total links — within recommended range
6URL length (26 chars) is within optimal range
7No redirect chain — direct URL resolution
8Primary keyword present in URL — good URL optimization
9OG image dimensions ≥1200×630px — optimal for all platforms
Issues Found
1Title tag is very short (11 chars)
2Missing meta description
3Missing canonical URL
4Missing OG tags: og:url
5Missing Twitter tags: twitter:card, twitter:title, twitter:description, twitter:image
6Thin content (36 words)
77 external links missing recommended rel attributes
8SPA framework detected (nextjs) with thin initial HTML content — search engines may not index all content
9Title and H1 share no keywords — misaligned topic signals
107 dofollow external links — slightly above optimal range
11Primary keyword "myflorida" not found in H1
12Weak E-E-A-T signals (2 indicators)
13Missing og:locale tag — social platforms may guess language/region
14Twitter card type not specified
15No social sharing buttons/widgets detected
Recommendations to Reach 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 a <link rel="canonical"> tag pointing to the preferred version of this page
4Add missing Open Graph tags: og:url
5Expand your content to at least 300+ words for better search rankings
6Add rel="nofollow noopener noreferrer" to external links pointing to unaffiliated sites
7Ensure your SPA uses server-side rendering (SSR) or static generation so crawlers see full content without JavaScript execution
8Align your title tag and H1 heading around the same primary keyword for clearer topical relevance
9Consider nofollowing 2–3 less authoritative outbound links to stay in the 2–5 optimal range
10Include your primary keyword in the H1 heading for strongest on-page SEO signal
11Strengthen E-E-A-T: add author bios, about page link, testimonials, trust badges, and credentials to demonstrate expertise and trustworthiness
12Link to an About page to establish authoritativeness and brand trust (E-E-A-T)
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)
15Set <meta name="twitter:card" content="summary_large_image"> for optimal Twitter/X previews
16Add social share buttons (Facebook, Twitter/X, LinkedIn, WhatsApp) to encourage content distribution and earn social signals
17OG sharing completeness at 67% — add missing tags for better social previews
18SEO (E-E-A-T): no author linkage or sameAs identity markup detected. Add a verifiable author byline with rel="author" and sameAs links to strengthen Experience/Expertise signals.
19SEO: no IndexNow signal detected. Adopt the IndexNow protocol (Bing/Yandex/Seznam) to push instant crawl notifications when content changes.
Key Findings
1Acceptable response time: 991ms
2Lean HTML document: 19KB
3No render-blocking scripts detected
41/1 images use lazy loading
5Most images have explicit width/height attributes (prevents layout shift)
6Preconnect hints for: https://fonts.googleapis.com, https://fonts.gstatic.com, https://fonts.gstatic.com
7Preloaded resources: style
8font-display property detected — reduces invisible text during font loading
90 async and 9 deferred scripts
10Cache-Control header with max-age is set
11Lean CSS payload (~34KB)
12JavaScript payload (~457KB) is acceptable for framework app
13HTTP/3 (QUIC) detected — fastest connection protocol
14CDN detected: CloudFront — reduces latency for global users
15Brotli compression enabled — best-in-class compression
16Estimated LCP: ~1271ms — within Google's "good" threshold (<2.5s)
17Estimated CLS: 0.05 — within Google's "good" threshold (<0.1)
18Estimated INP: ~105ms — within Google's "good" threshold (<200ms)
19Alternative analytics platform detected (Plausible/Umami/Matomo)
Issues Found
1No WebP or AVIF image formats found
25 font files loaded — excessive font weight
3Web fonts loaded without preload — causes FOIT/FOUT flash
Recommendations to Reach 100%
1Optimize server response time to under 500ms with caching or a CDN
2Convert images to WebP or AVIF format for 30–50% file size reduction
3Limit web fonts to 2–3 families with subset character ranges to reduce font loading impact
4Preload your primary font with <link rel="preload" as="font" crossorigin> for faster first contentful paint
5Add <link rel="preload" as="font" crossorigin> for your primary font files to eliminate flash of invisible/unstyled text
6Consider adding Google Search Console integration alongside your analytics for SEO-specific insights
7Performance: no Speculation Rules API detected. Add <script type="speculationrules"> to prerender/prefetch likely next navigations for near-instant page transitions.
8Performance (LCP): no image declares fetchpriority="high". Mark the LCP hero image with fetchpriority="high" so the browser prioritizes it during initial load.
Key Findings
1Viewport meta tag present: width=device-width, initial-scale=1.0
2HTML5 doctype declared
3Character encoding declared
4Theme color meta tag set for mobile browsers
5Web app manifest detected — PWA-ready
6Apple touch icons present
71 images with lazy loading benefit mobile data users
8Web app manifest includes 4 icon sizes — good coverage
9Lightweight page (~660KB) — fast on mobile networks
Issues Found
1Manifest present but no service worker — PWA install prompt will not fire
Recommendations to Reach 100%
1Consider implementing a service worker for offline support and faster repeat visits
2Add a service worker to complete PWA install requirements (manifest + SW + HTTPS)
3Add env(safe-area-inset-*) CSS for proper display on notched/island devices
4Add :active / touch-action CSS for tactile feedback on mobile interactions
5Mobile/PWA: incomplete Apple web-app meta tags (missing capable, status-bar-style, title). Add apple-mobile-web-app-capable, -status-bar-style and -title for a polished iOS home-screen install.
6Mobile/PWA: viewport meta lacks viewport-fit=cover. Add it (with safe-area-inset padding) so content renders edge-to-edge on notched/dynamic-island devices.
Key Findings
1HTTPS enabled — encrypted connection
2HTTP → HTTPS 302 redirect detected — properly forces secure connections
3No cookie security issues detected
4Privacy policy link detected
5Rate limiting recommended for form endpoints
6No server software/technology fingerprints exposed in headers or markup
7No stack traces or sensitive error details exposed in responses
8No raw email addresses exposed in page source
9No obvious secret/API-key patterns exposed in page source
10Client-side library inventory (SBOM): React
119 script resource(s) catalogued for software-composition review
12No common sensitive paths (.git, .env, server-status, …) were publicly accessible
Issues Found
1Missing Strict-Transport-Security header
2Missing Content-Security-Policy header
3Missing X-Content-Type-Options header
4Missing X-Frame-Options header
5Missing Referrer-Policy header
6Missing Permissions-Policy header
7Server header exposes technology: AmazonS3
87 external links missing rel="noopener noreferrer" — security risk
9No cookie consent banner detected
10security.txt file is missing — no standardized channel for reporting vulnerabilities
Recommendations to Reach 100%
1Add Strict-Transport-Security header with max-age=63072000; includeSubDomains; preload
2Implement a Content Security Policy to prevent XSS and injection attacks
3Add X-Content-Type-Options: nosniff to prevent MIME type sniffing
4Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking attacks
5Add Referrer-Policy: strict-origin-when-cross-origin to control referrer leakage
6Add Permissions-Policy to restrict access to camera, microphone, geolocation, etc.
7Add Cross-Origin-Opener-Policy: same-origin-allow-popups
8Add Cross-Origin-Resource-Policy: cross-origin
9Remove or obfuscate the Server header to avoid exposing your technology stack
10Add rel="noopener noreferrer" to all external links with target="_blank" to prevent tabnabbing attacks
11Implement a cookie consent banner for GDPR/ePrivacy compliance
12Implement rate limiting on form endpoints to prevent brute-force attacks and spam submissions
13Add 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]
14A09 Logging & Alerting Failures: no client-side error/security monitoring detected. Add centralized logging with tamper-evident storage and real-time alerting on auth failures and anomalies.
Key Findings
1Language declared: en
2Skip navigation link present
3All 1 images have alt attributes
4All 1 buttons have accessible labels
52 ARIA-attributed elements found
6Focus styles detected for keyboard navigation
71 minor HTML validity issue(s) — common in modern framework component patterns
Issues Found
1Missing landmarks: nav, footer
21 form(s) missing proper labels
31 duplicate ID(s) — breaks ARIA references and label associations
Recommendations to Reach 100%
1Add semantic landmark elements: <nav>, <footer>
2Add <label> elements associated with every form input via for/id attributes
3Review HTML structure for any non-framework-related nesting issues
4Ensure all element IDs are unique — duplicate IDs break form labels, ARIA relationships, and fragment navigation
5Accessibility: no forced-colors / prefers-contrast media handling detected. Test and support Windows High Contrast / forced-colors mode so essential UI remains visible.
Key Findings
1Complete social metadata (OG + Twitter Card)
22 call-to-action elements detected
3No AI crawlers blocked via meta tags — content accessible to AI search engines
4Moderate RAG-friendliness (46/100)
5Content provenance signals detected (citations with sources, attributed claims)
6Content freshness signals present (dateModified/datePublished/time elements)
7Good HTML-to-text ratio (56%) — AI crawlers can extract content efficiently
Issues Found
1No structured data (Schema.org) found
2No semantic HTML elements detected
3No breadcrumb navigation
4No FAQ or Q&A content patterns found
5No sitemap reference found
6No social media links found
7No robots.txt file found
8No llms.txt file found — AI models cannot find structured guidance for your site
Recommendations to Reach 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 a robots.txt file at your domain root — essential for crawler governance and AI SEO strategy
10Create /llms.txt following the llms.txt standard: # Title, > description, ## Overview, ## Core Services, ## Key Pages with full URLs
11Create /llms-full.txt with comprehensive documentation (services, pricing, team, case studies) for AI models that need depth
12Add <link rel="alternate" type="text/plain" href="/llms.txt"> in your HTML <head> for AI discoverability
13Add id attributes to headings and section elements for better RAG (Retrieval Augmented Generation) chunk targeting by AI systems
Key Findings
1Good paragraph length for readability and AI parsing
27 external citations — strong reference density for AI model training
32 call-to-action element(s) detected
4Trust signals present: HTTPS Security, Privacy Policy
5Clear value proposition detected in heading elements
Issues Found
1Very thin content (36 words)
2No structured Q&A content
3Weak entity markup — few terms emphasized
4Low semantic markup ratio — 21 divs vs 0 semantic elements
5Weak E-E-A-T schema signals
6No author or expertise signals
7No CTA above the fold
8No social proof elements
Recommendations to Reach 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
8Include specific statistics, percentages, and data points that AI models can extract and cite in responses
9Include expert quotes in <blockquote> elements to boost E-E-A-T and citation potential
10Add visible author bylines with bios and link to author pages — AI models evaluate content credibility through authorship signals
11Add more clear CTAs ("Get Started", "Request Quote", "Contact Us") throughout the page for higher conversion rates
12Place a clear CTA in your hero/header section so visitors see a conversion path immediately upon landing
13Add social proof: testimonials, client counts ("500+ businesses served"), case studies, or review snippets near CTAs
14AIO: no schema "name" property to anchor your primary entity. Declare a consistent Organization/Person/Product name in JSON-LD matching your title and H1.
Issues Found
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
Recommendations to Reach 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
12GEO: no comparison tables or step-by-step structured blocks found. Add comparison tables and ordered how-to steps — formats generative engines favor for structured, citable answers.
Key Findings
1Short paragraphs are well-suited for answer extraction
Issues Found
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...")
Recommendations to Reach 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
10AEO: no 40–60 word concise answer directly follows a question heading. Lead each question section with a self-contained ~40–60 word answer to win featured snippets and voice answers.
Key Findings
1NAP information detected: phone: 2776553
2Phone number(s) visible: 2776553, 1263593
Issues Found
1No LocalBusiness structured data
2No Google Maps embed
3No address microdata
4No geo meta tags
5No review/rating schema
Recommendations to Reach 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
Issues Found
1No Schema.org structured data found
2Missing high-impact schema types: Organization, WebSite
Recommendations to Reach 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
Key Findings
1prefers-reduced-motion support detected — respects user motion preferences
2High contrast / forced-colors mode supported
3Links are visually distinguishable (underline or decoration detected)
4Relative units (rem/em/clamp) detected — supports text resizing
5Focus styles detected for keyboard navigation visibility
6Page language declared — aids assistive technology
7All ARIA roles are valid
8Focus not obscured by sticky/fixed elements (WCAG 2.4.11)
9Accessible authentication detected (autocomplete, no CAPTCHA barriers) — WCAG 3.3.8
10prefers-reduced-motion detected but enforcement unclear
Issues Found
1No error suggestion mechanisms detected in forms
2No semantic HTML5 elements detected
3No form error identification detected
Recommendations to Reach 100%
1Add aria-invalid, aria-errormessage, and visible error messages for form validation (WCAG 3.3.3)
2Use semantic elements (main, nav, article, section, aside, header, footer) for WCAG-compliant page structure
3Add aria-invalid, aria-errormessage, and inline error messages to form fields (WCAG 3.3.1/3.3.3)
4Add aria-live regions (role="status" or role="alert") for form feedback, notifications, and dynamic content updates (WCAG 4.1.3)
5Ensure prefers-reduced-motion actually disables animations (set animation: none and transition: none in the media query)
Limited-Time Offer
All 12 Optimizations — Bundled Into Your Custom Website
We're currently bundling every optimization from this audit — SEO, AIO, GEO, AEO, Schema.org, WCAG accessibility, performance, security, and more — directly into our Custom Web Application Development service.
Instead of fixing issues after launch, we eliminate them from the start. Every website we build ships production-ready with a 90+ score across all 12 audit dimensions.