Skip to content
https://arkansas.gov

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

79

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff250 ms

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:56.593 source:map[type:text value:[unattributed]]] map[reflowTime:3.79 source:map[column:380 line:580 type:source-location url:https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js urlProvider:network]] map[reflowTime:0.561 source:map[column:47 line:303 type:source-location url:https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js urlProvider:network]] map[reflowTime:0.822 source:map[column:332 line:412 type:source-location url:https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js urlProvider:network]]]

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
/wp-content/cache/min/1/wp-content/plugins/elementor/asse...4.5 KiB
/wp-content/cache/min/1/wp-content/plugins/search-filter-...1.6 KiB91 ms
/wp-content/cache/min/1/wp-content/plugins/search-filter/...3.5 KiB
/wp-content/cache/min/1/wp-content/uploads/search-filter/...2.1 KiB91 ms
/wp-content/cache/min/1/wp-content/plugins/elementor/asse...4.5 KiB211 ms
/wp-content/cache/min/1/wp-content/plugins/elementor/asse...574 B171 ms
/wp-content/cache/min/1/wp-content/plugins/search-filter-...3.7 KiB91 ms
/wp-content/cache/min/1/wp-content/plugins/search-filter/...2.4 KiB
/wp-content/cache/min/1/wp-content/plugins/search-filter/...410 B91 ms
/wp-content/plugins/dynamic-content-for-elementor/assets/...1.9 KiB
/wp-content/themes/hello-theme-child-master/style.css?ver...582 B91 ms
/wp-content/uploads/elementor/css/post-18456.css?ver=1775...813 B
/wp-content/uploads/elementor/css/post-27877.css?ver=1775...12.4 KiB80 ms
portal.arkansas.gov/wp-content/uploads/elementor/css/post-13.css?ver=17757491157.9 KiB
/wp-content/plugins/elementor-pro/assets/css/conditionals...611 B
/wp-content/plugins/dynamic-content-for-elementor/assets/...3.2 KiB
/wp-content/plugins/dynamic-content-for-elementor/assets/...2.5 KiB
/wp-content/plugins/essential-addons-for-elementor-lite/a...1.6 KiB171 ms
/wp-content/cache/min/1/wp-content/themes/hello-elementor...1.3 KiB171 ms
/wp-content/plugins/elementor/assets/lib/animations/style...475 B171 ms
/wp-content/plugins/dynamic-content-for-elementor/assets/...431 B171 ms
/wp-content/plugins/dynamic-content-for-elementor/assets/...1.7 KiB171 ms
/wp-content/plugins/elementor/assets/css/widget-heading.m...203 B171 ms
/wp-content/uploads/elementor/css/custom-frontend.min.css...7.4 KiB211 ms
portal.arkansas.gov/wp-content/uploads/elementor/css/post-127.css?ver=17757491163.6 KiB
portal.arkansas.gov/wp-content/uploads/elementor/css/post-6.css?ver=17757490802.4 KiB
/wp-content/plugins/elementor/assets/lib/animations/style...320 B
/wp-content/plugins/elementor-pro/assets/css/modules/moti...510 B
/wp-content/uploads/elementor/css/custom-widget-nested-ta...2.1 KiB
/wp-content/plugins/elementor-pro/assets/css/widget-carou...895 B
/wp-content/uploads/elementor/css/custom-pro-widget-testi...1.9 KiB171 ms
/wp-content/plugins/elementor/assets/css/conditionals/e-s...998 B171 ms
/wp-content/plugins/elementor/assets/css/conditionals/sha...494 B171 ms
/wp-content/plugins/elementor/assets/css/widget-divider.m...981 B171 ms
/wp-content/plugins/elementor/assets/lib/animations/style...473 B171 ms
/wp-content/plugins/elementor/assets/lib/font-awesome/css...12.6 KiB251 ms
/wp-content/plugins/elementor-pro/assets/css/widget-searc...1.2 KiB171 ms
/wp-content/uploads/elementor/css/custom-pro-widget-mega-...3.1 KiB171 ms
/wp-content/cache/min/1/wp-content/plugins/dynamic-conten...1.4 KiB
/wp-content/plugins/elementor/assets/lib/animations/style...285 B171 ms
/wp-content/plugins/elementor/assets/lib/animations/style...337 B171 ms
/wp-content/cache/min/1/wp-content/plugins/dynamic-conten...5.5 KiB211 ms
/wp-content/plugins/elementor/assets/css/widget-image.min...200 B171 ms
/wp-content/plugins/dynamic-content-for-elementor/assets/...206 B171 ms
/wp-content/cache/min/1/wp-content/uploads/essential-addo...1.7 KiB171 ms
/wp-content/plugins/dynamic-content-for-elementor/assets/...162 B171 ms
/wp-content/plugins/dynamic-content-for-elementor/assets/...182 B171 ms
/wp-content/plugins/dynamic-content-for-elementor/assets/...2.5 KiB171 ms
/wp-content/plugins/elementor/assets/css/widget-menu-anch...141 B171 ms
/wp-content/cache/min/1/wp-content/themes/hello-elementor...1.8 KiB171 ms
/wp-content/uploads/elementor/css/custom-pro-widget-loop-...1.3 KiB171 ms
/wp-content/cache/min/1/wp-content/themes/hello-elementor...1.4 KiB171 ms
/wp-content/uploads/elementor/css/custom-widget-icon-list...1.1 KiB171 ms
portal.arkansas.gov/wp-includes/css/dist/block-library/style.min.css?ver=6.9.415.9 KiB291 ms
/wp-content/plugins/elementor-pro/assets/css/widget-loop-...229 B171 ms
/wp-content/uploads/elementor/css/custom-widget-icon-box....565 B171 ms
/wp-content/uploads/elementor/css/custom-pro-widget-slide...810 B171 ms
portal.arkansas.gov/wp-content/uploads/elementor/css/post-209.css?ver=17757491081.5 KiB91 ms

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.3 KiB

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Real ID Mobile ID Car Tag Renewal Property Taxes Franchise Tax AR Taxpayer Acce… div.elementor-widget-container > div.elementor-shortcode > div.elementor > div.elementor-element
portal.arkansas.gov/wp-content/uploads/dogs-at-the-caddo-river-jpg.webp194.1 KiB35.5 KiB
body.home > footer.elementor > div.elementor-element > ::before body.home > footer.elementor > div.elementor-element > ::before
portal.arkansas.gov/wp-content/uploads/2023/03/fish-seamless-pattern-768x768.png111.9 KiB15.9 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 28.0 KiB
URLTransfer SizeEst Savings
portal.arkansas.gov/wp-includes/css/dist/block-library/style.min.css?ver=6.9.415.8 KiB15.7 KiB
/wp-content/plugins/elementor/assets/lib/font-awesome/css...12.4 KiB12.3 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 177.2 KiB
URLTransfer SizeEst Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js361.8 KiB177.2 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 595 ms
URLTime Spent
arkansas.gov/595 ms
portal.arkansas.gov/0.0 ms
●Time to Interactive 2.3 s
●Layout shift culprits
●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 40 ms
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,665 KiB
●JavaScript execution time 0.2 s
●Minimizes main-thread work 1.4 s
●Avoid long main-thread tasks 1 long task found
●Avoid non-composited animations 49 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 130 ms
●Server Backend Latencies 50 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 190 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
99

Accessibility

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
92

SEO

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
www.dfa.arkansas.gov/mydmv-service/real-id/LEARN MORE
/news/arkansas-century-farm-program-now-accepting-2026-ap...read more
/news/asp-traffic-stop-on-i-57-leads-to-seizure-of-6-kilo...read more
/news/asp-cid-investigating-officer-involved-shooting-dea...read more
/news/annual-asp-memorial-service-honoring-fallen-trooper...read more
/news/asp-west-memphis-pd-stop-suspect-fleeing-in-stolen-...read more
ardot.gov/news/26-050/read more

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid
●Page isn’t blocked from indexing
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback