Website review, no card needed

myfloridacfo.com logo

myfloridacfo.com website review

Visit site (opens in a new tab)Reviewed 29 October 202638 issues · 83 checks

This review found 38 issues worth fixing on myfloridacfo.com, 15 of them high impact, across 83 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.0 s1.7 sMay 9Oct 241.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.7 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.8 s
Oct 3, 20261.9 s
Oct 10, 20262.0 s
Oct 17, 20262.0 s
Oct 24, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
97 ms79 msMay 9Oct 2481 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202686 ms
May 16, 202686 ms
May 23, 202688 ms
May 30, 202689 ms
Jun 6, 202688 ms
Jun 13, 202693 ms
Jun 20, 202688 ms
Jun 27, 202691 ms
Jul 4, 202695 ms
Jul 11, 202691 ms
Jul 18, 202690 ms
Jul 25, 202689 ms
Aug 1, 202687 ms
Aug 8, 202686 ms
Aug 15, 202686 ms
Aug 22, 202684 ms
Aug 29, 202685 ms
Sep 5, 202686 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202686 ms
Oct 3, 202686 ms
Oct 10, 202683 ms
Oct 17, 202682 ms
Oct 24, 202681 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of myfloridacfo.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. myfloridacfo.com at 0.5 s0.5 s
  2. myfloridacfo.com at 1.0 s1.0 s
  3. myfloridacfo.com at 1.4 s1.4 s
  4. myfloridacfo.com at 1.9 s1.9 s
  5. myfloridacfo.com at 2.4 s2.4 s
  6. myfloridacfo.com at 2.9 s2.9 s
  7. myfloridacfo.com at 3.4 s3.4 s
  8. myfloridacfo.com at 3.9 s3.9 s

Speed

5 to fix37
  • Improve image delivery

    2.8 s · 648 KiB

    5 images could be 648 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.

  • Render-blocking requests

    2.1 s

    17 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.

  • Reduce unused JavaScript

    1.4 s · 223 KiB

    About 223 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 37

    37/100

    Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused CSS

    300 ms · 51 KiB

    About 51 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and jQuery CDN and others), adding 545 KiB and 319 ms of main-thread time.

  • Font display

    250 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

  • 4 long tasks on the main thread

    4 long tasks block the main thread while loading, the longest for 148 ms. During a long task the page ignores taps.

  • Document request latency

    25 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Use efficient cache lifetimes

    20 KiB

    3 files are served with short cache lifetimes, so returning visitors download them again (20 KiB).

  • Minify CSS

    8 KiB

    8 KiB could be saved by minifying CSS.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 275 ms of it running JavaScript. That is comfortably low.

  • Server response: 30 ms

    30 ms

    Your server sent the HTML in 30 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 17.6 s

    17.6 s

    Your largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Florida Department of Financial Services - How Can We Help …”.

  • Time to Interactive: 17.6 s

    17.6 s

    The page becomes fully interactive after 17.6 s. Good is under 3.8 s.

  • First Contentful Paint: 5.7 s

    5.7 s

    The first text or image appears after 5.7 s on a phone. Good is under 1.8 s.

  • Cumulative Layout Shift: 0.418

    0.418

    The layout shifts by 0.418 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 7.5 s

    7.5 s

    Visually, the page fills in at 7.5 s (Speed Index). Good is under 3.4 s.

  • Real-user LCP: 2.5 s

    2.5 s

    Real visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 2.2 s

    2.2 s

    Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

  • 16 images without width and height

    16 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -5%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 86 ms to 81 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user INP: 72 ms

    72 ms

    Real visitors wait 72 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.07

    0.07

    For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.

  • Total Blocking Time: 142 ms

    142 ms

    Scripts block the page for only 142 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix60
  • 1 image over 500 KB

    myfloridacfo-background.webp weighs 938 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 2.7 MB in 61 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 61 requests on a phone: images 1.4 MB (23), fonts 571 KiB (9) and scripts 534 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    61 KiB

    1 image is downloaded at several times the size a phone draws it, for example meeth-cfo-ingoglia-banner.jpg at 1,485 px wide, shown at 366 px. Resized copies would save about 61 KiB.

  • 3 images in older formats

    3 images (261 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 4 images below the first screen load straight away

    4 images further down the page (85 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.78 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.78 g of CO₂e: 93.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

4 to fixGoogle 9293
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8379
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 52 internal links, 17 external

    The homepage links to 52 pages on myfloridacfo.com and 17 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “Florida Department of Financial Services Homepage”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “The Florida Department of Financial Services | MyFloridaCFO.com”.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://myfloridacfo.com/sitemap/sitemap-index.xml.

AI search readiness

2 to fix75
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • Some text only appears after JavaScript runs

    45%

    The HTML your server sends has 195 of the 432 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

    There is no https://myfloridacfo.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

1 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

3 to fix83
  • 2 pages share a title

    / and https://myfloridacfo.com/home all use the title “The Florida Department of Financial Services | MyFloridaCFO.com”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://myfloridacfo.com/about/meet-the-cfo, https://myfloridacfo.com/news/pressreleases, https://myfloridacfo.com/home, https://myfloridacfo.com/division/consumers/home, https://myfloridacfo.com/division/risk/home and https://myfloridacfo.com/division/treasury/home and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://myfloridacfo.com/division/funeralcemetery/home, https://myfloridacfo.com/division/risk/home and https://myfloridacfo.com/division/wc/home have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 40 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Connecting to 'https://use.typekit.net/qzk1ppy.css' violates the following Content Security Policy directive: "connect-…”.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    29 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix57
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 432 words of copy

    The homepage carries about 432 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact” and “Public Records Request”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 13 other companies contacted

    Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at myfloridacfo.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Sitefinity 15.4.8622.0 DX
Framework
jQuery
Analytics
Google Tag Manager
Hosting
State Of Fla

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on myfloridacfo.com, including 15 speed issues, 4 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25