Spain · Madrid Completed: Apr 22, 2026 23:39 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 73 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Well-optimized for search — your content is discoverable.
Good server performance with room for optimization.
Several regulatory requirements are not yet met.
Missing metadata means poor previews on social media and search.
Reasonable footprint with room for optimization.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
Cookie 'ASP.NET_SessionId' is missing the Secure flag
Security gaps expose your site and users to attacks, eroding trust.
Cookie '__RequestVerificationToken' is missing the Secure flag
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
High impact, low effort — start here.
High impact, requires investment.
Nothing in this quadrant — good news.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/63d013b3-7f6f-4d3c-8f75-2b8d2525c088)<a href="https://beavercheck.com/results/63d013b3-7f6f-4d3c-8f75-2b8d2525c088"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fflsenate.gov" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fflsenate.govThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. The 5 security gaps leave your users exposed — modern browsers increasingly warn visitors about insecure sites. Addressing the critical issues below would have the most immediate impact on your user trust.
8 barrier(s) likely increasing bounce by ~38%.
Page takes 5.5s to load
+12% bounceUsers abandon at ~3s — you're 3.0s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
5 form field(s) without a label
+6% bounceScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
Fix: Associate every input with a visible <label for="…">; add autocomplete attributes
No viewport meta tag
+15% bounceMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">
No Open Graph tags
+2% bounceLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
Fix: Add og:title, og:description, og:image, og:url to the page head
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
2 broken link(s) on the page
+3% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$250 investment → $4,158/month returns + USD 157,500 risk avoided
$250
2h · 5 findings
$4,158 /mo
~$49,901 / year
USD 157,500
if kept compliant
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
2.5 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,125 / month at risk
~$157,502 / year if left unfixed
$157,500
+6 more
$0.13 /mo
1630.5 MB/mo × 0.080 USD/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
5.47 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
5.52 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
21 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
9.46 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
6.02 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| m.flsenate.gov/Scripts/jquery.mobile-1.3.2.min.js | 142.3 KiB | 3.3 s |
| m.flsenate.gov/Scripts/jquery-1.9.1.min.js | 90.8 KiB | 2.8 s |
| m.flsenate.gov/Content/css/jquery.mobile-1.3.2.min.css | 92.8 KiB | 2.8 s |
| m.flsenate.gov/Scripts/GoogleAnalytics.js | 1.0 KiB | 580 ms |
| m.flsenate.gov/Scripts/jquery.validate.min.js | 20.9 KiB | 1.3 s |
| m.flsenate.gov/Scripts/jquery.unobtrusive.custom.mobile-only.js | 7.0 KiB | 880 ms |
| m.flsenate.gov/Scripts/jquery.validate.unobtrusive.min.js | 5.0 KiB | 730 ms |
| m.flsenate.gov/Content/css/styles.css | 12.9 KiB | 1.2 s |
| m.flsenate.gov/Scripts/initializerScripts.js | 3.1 KiB | 730 ms |
| m.flsenate.gov/Scripts/jquery-migrate-1.2.1.min.js | 8.4 KiB | 880 ms |
| m.flsenate.gov/Scripts/ListCollapser.js | 2.2 KiB | 580 ms |
| m.flsenate.gov/Content/css/common.css | 48.9 KiB | 1.3 s |
| m.flsenate.gov/Content/css/pending.css | 1.0 KiB | 280 ms |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| www.google-analytics.com/analytics.js | 7200.0 s | 20.9 KiB |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div.ui-panel-content-wrap > div.mHeader > div > a.logo div.ui-panel-content-wrap > div.mHeader > div > a.logo | m.flsenate.gov/Content/img/logo.png | 10.1 KiB | 8.8 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| flsenate.gov/ | 1.1 s |
| m.flsenate.gov/ | 0.0 ms |
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| m.flsenate.gov/ | 2.7 s |
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| m.flsenate.gov/Content/css/common.css | 48.9 KiB | 14.5 KiB |
| m.flsenate.gov/Content/css/print.css | 18.7 KiB | 6.5 KiB |
| m.flsenate.gov/Content/css/styles.css | 12.9 KiB | 4.4 KiB |
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| m.flsenate.gov/Content/css/jquery.mobile-1.3.2.min.css | 92.5 KiB | 81.7 KiB |
| m.flsenate.gov/Content/css/common.css | 48.6 KiB | 39.6 KiB |
| m.flsenate.gov/Content/css/print.css | 18.4 KiB | 18.4 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| m.flsenate.gov/Scripts/jquery.mobile-1.3.2.min.js | 142.0 KiB | 82.5 KiB |
| m.flsenate.gov/Scripts/jquery-1.9.1.min.js | 90.5 KiB | 35.2 KiB |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| m.flsenate.gov/Scripts/jquery.unobtrusive.custom.mobile-only.js | 6.7 KiB | 2.3 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.ui-mobile html.ui-mobile |
These are opportunities to improve the interpretation of your content by users in different locales.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta head > meta |
These items highlight common accessibility best practices.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Please Select a Senator
Albritton (27)
Arrington (25)
Avila (39)
Berman (26)
Be… div.main > div.ui-body > form#NameLeg > select#Senator |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.47 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.82 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
0 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.051
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.23 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
3.82 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
President Albritton enters the Senate Chamber div#spotlightSlider > div.spotlightItem > div.image > img.slide-photo | flsenate.gov/PublishedContent/images/Slides/2026OpeningDay.jpg | 155.4 KiB | 141.1 KiB |
President div#president > a > p.centertext > img | flsenate.gov/PublishedContent/Senators/2024-2026/Photos/s27_5342.jpg | 62.2 KiB | 54.8 KiB |
div.header-container > header.wrapper > div#logo > a.logo div.header-container > header.wrapper > div#logo > a.logo | flsenate.gov/Content/img/seals.png | 61.0 KiB | 52.7 KiB |
Senate Page Program div.bannerBtns > p > a#btnPageProgram > img | flsenate.gov/UserContent/img/buttons/btn-PageProgram.png | 52.4 KiB | 50.0 KiB |
Senate Kids Handbook div.bannerBtns > p > a#btnSenateKidsPDF > img | flsenate.gov/UserContent/img/buttons/btn-SenateKidsBook.png | 42.3 KiB | 40.0 KiB |
Next div.main > div.grid-autoLeft > div#calendar > a#homeNextButton | flsenate.gov/Content/img/common.png | 28.1 KiB | 21.4 KiB |
Appropriations div.bannerBtns > p > a#btnAppropriations > img | flsenate.gov/UserContent/img/buttons/btn-Appropriations.png | 20.4 KiB | 18.0 KiB |
Hold the Line on the Urban Development Boundary (PDF)
March 16, 2026 - Publicat… div.grid-autoLeft > div.gridHome-autoLeft > ul.recentNews > li.nophoto | flsenate.gov/PublishedContent/Senators/2024-2026/Photos/S38_5525_avatar.jpg | 13.0 KiB | 12.6 KiB |
Week in Review: Session Week 9 (PDF)
March 14, 2026 - Publication by Senator Ar… div.grid-autoLeft > div.gridHome-autoLeft > ul.recentNews > li.nophoto | flsenate.gov/PublishedContent/Senators/2024-2026/Photos/S25_5494_avatar.jpg | 12.5 KiB | 12.2 KiB |
2026 The First 60 Days (PDF)
March 23, 2026 - Publication by Senator Martin div.grid-autoLeft > div.gridHome-autoLeft > ul.recentNews > li.nophoto | flsenate.gov/PublishedContent/Senators/2024-2026/Photos/S33_5524_avatar.jpg | 12.3 KiB | 12.0 KiB |
"Delivering for District 35" March 2026 Edition (PDF)
March 17, 2026 - Publicat… div.grid-autoLeft > div.gridHome-autoLeft > ul.recentNews > li.nophoto | flsenate.gov/PublishedContent/Senators/2024-2026/Photos/S35_5572_avatar.jpg | 12.1 KiB | 11.8 KiB |
EMERGENCY STOPGAP FUNDING FOR FLORIDA HIV PATIENTS SIGNED INTO LAW (PDF)
March … div.grid-autoLeft > div.gridHome-autoLeft > ul.recentNews > li.nophoto | flsenate.gov/PublishedContent/Senators/2024-2026/Photos/S17_5256_avatar.jpg | 11.9 KiB | 11.6 KiB |
Accessibilty div.bannerBtns > p > a#btnAccessibility > img | flsenate.gov/UserContent/img/buttons/btn-accessibility.png | 8.4 KiB | 6.0 KiB |
Special Session Update and Planning (PDF)
April 15, 2026 - Publication by Presi… div.grid-autoLeft > div.gridHome-autoLeft > ul.recentNews > li.presOffice | flsenate.gov/UserContent/img/mediaIcons/seal-45x45.png | 6.2 KiB | 5.9 KiB |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img | flsenate.gov/PublishedContent/Offices/Senator/Week_in_Review__Session_Week_9.jpg | 6.5 KiB | 5.4 KiB |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img | flsenate.gov/PublishedContent/Offices/Senator/Week_in_Review__Post_Session.jpg | 6.5 KiB | 5.3 KiB |
Find Your State Legislators, U.S. Representatives & U.S. Senators div.bannerBtns > p > a#btnFYL > img | flsenate.gov/UserContent/img/buttons/btn-find-legislators.png | 7.6 KiB | 5.2 KiB |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| flsenate.gov/ | 1.2 s |
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| flsenate.gov/Content/css/common.css | 17.9 KiB | 6.3 KiB |
| flsenate.gov/Content/css/home.css | 13.3 KiB | 5.3 KiB |
| flsenate.gov/Content/css/styles.css | 5.7 KiB | 2.3 KiB |
| flsenate.gov/Content/css/print.css | 5.7 KiB | 2.3 KiB |
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| flsenate.gov/Scripts/jquery-ui-1.13.2.js | 709.6 KiB | 362.0 KiB |
| flsenate.gov/Scripts/jquery-3.7.1.js | 83.0 KiB | 41.4 KiB |
| flsenate.gov/Scripts/HomePage/FloorBills.js | 5.7 KiB | 2.6 KiB |
| flsenate.gov/Scripts/HomePage/BillActions.js | 3.8 KiB | 2.0 KiB |
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| flsenate.gov/PublishedContent/Senators/css/avatar.css | 24.4 KiB | 23.6 KiB |
| flsenate.gov/Content/css/common.css | 17.5 KiB | 14.5 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| flsenate.gov/Scripts/jquery-ui-1.13.2.js | 709.6 KiB | 567.8 KiB |
| www.googletagmanager.com/gtag/js?id=G-ZLT62P38CF&cx=c>m=4e64k1 | 151.8 KiB | 65.2 KiB |
| www.googletagmanager.com/gtag/js?id=G-8CSBCL4LLF&cx=c>m=4e64k1 | 151.8 KiB | 65.1 KiB |
| www.googletagmanager.com/gtag/js?id=?tag=G-ZLT62P38CF | 84.6 KiB | 55.9 KiB |
| www.googletagmanager.com/gtag/js?id=?tag=G-8CSBCL4LLF | 84.6 KiB | 53.4 KiB |
| flsenate.gov/Scripts/jquery-3.7.1.js | 83.0 KiB | 34.7 KiB |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
President Albritton enters the Senate Chamber div#spotlightSlider > div.spotlightItem > div.image > img.slide-photo | flsenate.gov/PublishedContent/images/Slides/2026OpeningDay.jpg |
ul.recentNews > li.presOffice > a > img ul.recentNews > li.presOffice > a > img | /PublishedContent/Offices/President/4_15_26_Special_Sessi... |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img | /PublishedContent/Offices/Senator/Delivering_for_District... |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img | flsenate.gov/PublishedContent/Offices/Senator/Week_in_Review__Post_Session.jpg |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img | /PublishedContent/Offices/Senator/EMERGENCY_STOPGAP_FUNDI... |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img | flsenate.gov/PublishedContent/Offices/Senator/2026_The_First_60_Days__2_.jpg |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img | /PublishedContent/Offices/Senator/Delivering_for_District... |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img | /PublishedContent/Offices/Senator/Protecting_Our_Water__P... |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img | flsenate.gov/PublishedContent/Offices/Senator/Week_in_Review__Session_Week_9.jpg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
District 27 div#president > ul > li > a |
Media & Press Releases div#president > ul > li > a#lnkPresidentMedia |
Legislative Appointments div#president > ul > li > a#lnkLegislativeAppointments |
These are opportunities to improve the legibility of your content.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.js html.js |
These are opportunities to improve the interpretation of your content by users in different locales.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
ul.recentNews > li.presOffice > a > img ul.recentNews > li.presOffice > a > img |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img |
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div#billYear_chzn > div.chzn-drop > div.chzn-search > input div#billYear_chzn > div.chzn-drop > div.chzn-search > input |
div#statuteYear_chzn > div.chzn-drop > div.chzn-search > input div#statuteYear_chzn > div.chzn-drop > div.chzn-search > input |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.header-container > header.wrapper > div#logo > a.logo div.header-container > header.wrapper > div#logo > a.logo |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Media & Press Releases div#president > ul > li > a#lnkPresidentMedia |
Legislative Appointments div#president > ul > li > a#lnkLegislativeAppointments |
Special Session Proclamation div#homeCalendarLinks > ul > li > a |
Calendars/Weekly Schedules div#homeCalendarLinks > ul > li > a |
Video Broadcast Schedule div#homeCalendarLinks > ul > li > a |
2 div.spotlightHeader > ul.controls > li > a |
3 div.spotlightHeader > ul.controls > li > a |
4 div.spotlightHeader > ul.controls > li > a |
5 div.spotlightHeader > ul.controls > li > a |
6 div.spotlightHeader > ul.controls > li > a |
7 div.spotlightHeader > ul.controls > li > a |
Play div.spotlightHeader > ul.controls > li > a.ctrlimg |
Pause div.spotlightHeader > ul.controls > li > a.ctrlimg |
Senators nav > div.grid-20 > p > a |
Senator List div.grid-20 > ul > li > a |
Find Your Legislators div.grid-20 > ul > li > a |
District Maps div.grid-20 > ul > li > a |
Vote Disclosures div.grid-20 > ul > li > a |
Committees nav > div.grid-20 > p > a |
Committee List div.grid-20 > ul > li > a |
Committee Publications div.grid-20 > ul > li > a |
Search nav > div.grid-20 > p > a |
Bill Search Tips div.grid-20 > ul > li > a |
Statute Search Tips div.grid-20 > ul > li > a |
Site Search Tips div.grid-20 > ul > li > a |
Session nav > div.grid-20 > p > a |
Bills div.grid-20 > ul > li > a |
Calendars div.grid-20 > ul > li > a |
Journals div.grid-20 > ul > li > a |
Appropriations div.grid-20 > ul > li > a |
Conferences div.grid-20 > ul > li > a |
Reports div.grid-20 > ul > li > a |
Executive Appointments div.grid-20 > ul > li > a |
Executive Suspensions div.grid-20 > ul > li > a |
Redistricting div.grid-20 > ul > li > a |
Statutes div.grid-20 > ul > li > a |
Constitution div.grid-20 > ul > li > a |
Media nav > div.grid-20 > p > a |
Publications div.grid-20 > ul > li > a |
Videos div.grid-20 > ul > li > a |
Topics div.grid-20 > ul > li > a |
About nav > div.grid-20 > p > a |
Employment div.grid-20 > ul > li > a |
Visit Us div.grid-20 > ul > li > a |
Contact Us div.grid-20 > ul > li > a |
Page Program div.grid-20 > ul > li > a |
Offices nav > div.grid-20 > p > a |
President's Office div.grid-20 > ul > li > a |
Majority Office div.grid-20 > ul > li > a |
Minority Office div.grid-20 > ul > li > a |
Secretary's Office div.grid-20 > ul > li > a |
Reference nav > div.grid-20 > p > a |
Glossary div.grid-20 > ul > li > a |
FAQ div.grid-20 > ul > li > a |
Help div.grid-20 > ul > li > a |
Links div.grid-20 > ul > li > a |
Search Tips div.grid-20 > ul > li > a |
Publications div.grid-20 > ul > li > a |
Rules div.grid-20 > ul > li > a |
Handbooks div.grid-20 > ul > li > a |
Advisory Opinions div.grid-20 > ul > li > a |
Public Records div.grid-20 > ul > li > a |
Twitter div.grid-20 > ul.inline > li > a.twitterIco16 |
RSS div.grid-20 > ul.inline > li > a.rssIco16 |
Senate Tracker nav > div.grid-20 > p > a |
Login div.grid-20 > ul > li > a |
Sign Up div.grid-20 > ul > li > a |
Tracker Help div.grid-20 > ul > li > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.js html.js |
These items highlight common accessibility best practices.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | flsenate.gov/Scripts/jquery-3.7.1.js line 4996, col 11 |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
ul.recentNews > li.presOffice > a > img ul.recentNews > li.presOffice > a > img |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img |
ul.recentNews > li.nophoto > a > img ul.recentNews > li.nophoto > a > img |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Performance issues directly impact user engagement and conversion rates.
| Uncrawlable Link |
|---|
2026D div#searchbox > form.form-inline > div#billYear_chzn > a.chzn-single |
2025 div#searchbox > form.form-inline > div#statuteYear_chzn > a.chzn-single |
Prev div#datepicker > div.ui-datepicker-inline > div.ui-datepicker-header > a.ui-datepicker-prev |
Next div#datepicker > div.ui-datepicker-inline > div.ui-datepicker-header > a.ui-datepicker-next |
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Performance issues directly impact user engagement and conversion rates.
To appear in search results, crawlers need access to your app.
Send Feedback