Ca.gov www.ca.gov | California State Portal
State of California
ca.gov Mobile Performance
31/100
These metrics represent real-world Chrome users experience viewing ca.gov on mobile devices. Reports are focused on loading performance and other critical factors that most affect user experience. Follow our guide to track, optimize, and improve the quality of your web pages.
User Loading Experience
Largest Contentful Paint
Cumulative Layout Shift
First Contentful Paint
First Input Delay
Metrics
Largest Contentful Paint0/100 18.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Cumulative Layout Shift12/100 0.588
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Time to Interactive25/100 10.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Speed Index34/100 6.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Total Blocking Time48/100 610 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
First Contentful Paint65/100 3.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Should Fix (20)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats
Potential savings of 2,547 KiB
15,120 ms
Efficiently encode images
Potential savings of 279 KiB
1,830 ms
Properly size images
Potential savings of 278 KiB
1,350 ms
Remove unused JavaScript
Potential savings of 224 KiB
1,170 ms
Eliminate render-blocking resources
Potential savings of 900 ms
900 ms
Remove unused CSS
Potential savings of 64 KiB
360 ms
Minify JavaScript
Potential savings of 61 KiB
330 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Does not use passive listeners to improve scrolling performance
Avoid `document.write()`
Reduce the impact of third-party code
Third-party code blocked the main thread for 390 ms
Serve static assets with an efficient cache policy
35 resources found
Minimize main-thread work
6.9 s
Avoid enormous network payloads
Total size was 4,962 KiB
Reduce JavaScript execution time
2.3 s
Largest Contentful Paint element
1 element found
Keep request counts low and transfer sizes small
116 requests • 4,962 KiB
Avoid long main-thread tasks
20 long tasks found
Avoid large layout shifts
5 elements found
Avoid chaining critical requests
13 chains found
Passed Audits (9)
Avoids an excessive DOM size
550 elements
Minify CSS
Potential savings of 14 KiB
Use video formats for animated content
Preload key requests
Enable text compression
Defer offscreen images
Potential savings of 570 KiB
Avoid multiple page redirects
Potential savings of 630 ms
Initial server response time was short
Root document took 370 ms
Preconnect to required origins
ca.gov Mobile SEO
90/100
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more. Run these additional validators on your site to check additional SEO best practices.
Should Fix (2)
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately
84% appropriately sized tap targets
Passed Audits (10)
Document avoids plugins
Document has a valid `hreflang`
Document has a `<title>` element
Document has a meta description
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Links have descriptive text
Document uses legible font sizes
100% legible text
Image elements have `[alt]` attributes
Page has successful HTTP status code
Page isn’t blocked from indexing
ca.gov Mobile Best Practices
69/100
These checks highlight opportunities to improve the overall code health of ca.gov mobile page. Current recommendations will help to make your page fast and secure, to create a good user experience and to avoid deprecated technologies.
Should Fix (4)
Trust and Safety
Links to cross-origin destinations are unsafe
Does not use HTTPS
1 insecure request found
Includes front-end JavaScript libraries with known security vulnerabilities
2 vulnerabilities detected
General
Browser errors were logged to the console
Passed Audits (10)
Page has the HTML doctype
Avoids requesting the geolocation permission on page load
Serves images with appropriate resolution
Detected JavaScript libraries
Displays images with correct aspect ratio
Allows users to paste into password fields
Avoids Application Cache
Avoids requesting the notification permission on page load
Avoids deprecated APIs
Properly defines charset
ca.gov Mobile Progressive Web App
25/100
These checks validate the aspects of a Progressive Web App. Learn more. These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Should Fix (9)
PWA Optimized
Manifest doesn't have a maskable icon
Is not configured for a custom splash screen
Does not set a theme color for the address bar.
Fast and reliable
Page load is not fast enough on mobile networks
Interactive at 10.4 s
`start_url` does not respond with a 200 when offline
Current page does not respond with a 200 when offline
Installable
Does not use HTTPS
1 insecure request found
Web app manifest does not meet the installability requirements
Does not register a service worker that controls page and `start_url`
Passed Audits (5)
Redirects HTTP traffic to HTTPS
Contains some content when JavaScript is not available
Content is sized correctly for the viewport
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Provides a valid `apple-touch-icon`
ca.gov Mobile Accessibility
92/100
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Should Fix (2)
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[role]`s are not contained by their required parent element
Passed Audits (23)
Buttons have an accessible name
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
`[aria-*]` attributes match their roles
`<html>` element has a valid value for its `[lang]` attribute
The page contains a heading, skip link, or landmark region
No element has a `[tabindex]` value greater than 0
Document has a `<title>` element
`[id]` attributes on active, focusable elements are unique
`<frame>` or `<iframe>` elements have a title
ARIA IDs are unique
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[aria-hidden="true"]` elements do not contain focusable descendents
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Background and foreground colors have a sufficient contrast ratio
Image elements have `[alt]` attributes
`[role]` values are valid
`<html>` element has a `[lang]` attribute
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
Mobile Usability
99/100
These checks validate how easily a visitor can use ca.gov on a mobile device. Test results include a list of any mobile usability problems. Mobile usability problems are issues that can affect a user that visits the page on a mobile (small screen) device, including small font sizes (which are hard to read on a small screen).
Should Fix (1)
Size tap targets appropriately
Passed Audits (5)
Avoid app install interstitials that hide content
Avoid plugins
Configure the viewport
Size content to viewport
Use legible font sizes
Mobile Speed
53/100
These checks analyze the performance of ca.gov on mobile devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (6)
Optimize images
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Leverage browser caching
Reduce server response time
Minify JavaScript
Minify HTML
Passed Audits (4)
Avoid landing page redirects
Enable compression
Minify CSS
Prioritize visible content
www.ca.com
www.ca.net
www.ca.org
www.ca.info
www.ca.biz
www.ca.us
www.ca.mobi
www.a.gov
www.ca.gov
www.xa.gov
www.cxa.gov
www.xca.gov
www.da.gov
www.cda.gov
www.dca.gov
www.fa.gov
www.cfa.gov
www.fca.gov
www.va.gov
www.cva.gov
www.vca.gov
www.c.gov
www.cq.gov
www.caq.gov
www.cqa.gov
www.cw.gov
www.caw.gov
www.cwa.gov
www.cs.gov
www.cas.gov
www.csa.gov
www.cz.gov
www.caz.gov
www.cza.gov
www.ca.net
www.ca.org
www.ca.info
www.ca.biz
www.ca.us
www.ca.mobi
www.a.gov
www.ca.gov
www.xa.gov
www.cxa.gov
www.xca.gov
www.da.gov
www.cda.gov
www.dca.gov
www.fa.gov
www.cfa.gov
www.fca.gov
www.va.gov
www.cva.gov
www.vca.gov
www.c.gov
www.cq.gov
www.caq.gov
www.cqa.gov
www.cw.gov
www.caw.gov
www.cwa.gov
www.cs.gov
www.cas.gov
www.csa.gov
www.cz.gov
www.caz.gov
www.cza.gov