Ny.gov The Official Website of New York State
The official website of the State of New York. Find information about state government agencies and learn more about our programs and services.
ny.gov Desktop Performance
51/100
These metrics represent real-world Chrome users experience viewing ny.gov web page. 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 Paint16/100 4.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
First Contentful Paint35/100 1.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index48/100 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Time to Interactive49/100 4.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Cumulative Layout Shift58/100 0.216
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Total Blocking Time97/100 100 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Should Fix (16)
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Eliminate render-blocking resources
Potential savings of 1,080 ms
1,080 ms
Serve images in next-gen formats
Potential savings of 1,294 KiB
1,080 ms
Preload key requests
Potential savings of 1,050 ms
1,050 ms
Efficiently encode images
Potential savings of 554 KiB
480 ms
Remove unused CSS
Potential savings of 82 KiB
240 ms
Remove unused JavaScript
Potential savings of 219 KiB
160 ms
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Does not use passive listeners to improve scrolling performance
Ensure text remains visible during webfont load
Avoid enormous network payloads
Total size was 6,993 KiB
Serve static assets with an efficient cache policy
9 resources found
Avoid an excessive DOM size
1,397 elements
Avoid long main-thread tasks
4 long tasks found
Avoid chaining critical requests
29 chains found
Keep request counts low and transfer sizes small
87 requests • 6,993 KiB
Avoid large layout shifts
5 elements found
Largest Contentful Paint element
1 element found
Passed Audits (13)
Minimizes main-thread work
1.6 s
Preconnect to required origins
JavaScript execution time
0.7 s
Avoids `document.write()`
Defer offscreen images
Potential savings of 3 KiB
Avoid multiple page redirects
Potential savings of 190 ms
Properly size images
Potential savings of 2 KiB
Initial server response time was short
Root document took 150 ms
Minify JavaScript
Potential savings of 17 KiB
Enable text compression
Minify CSS
Minimize third-party usage
Third-party code blocked the main thread for 10 ms
Use video formats for animated content
ny.gov Desktop SEO
83/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
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
6 links found
Passed Audits (10)
Page isn’t blocked from indexing
Document avoids plugins
Page has successful HTTP status code
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
robots.txt is valid
Document has a `<title>` element
Document has a valid `rel=canonical`
Image elements have `[alt]` attributes
Document has a meta description
Document has a valid `hreflang`
ny.gov Desktop Best Practices
69/100
These checks highlight opportunities to improve the overall code health of ny.gov 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
Includes front-end JavaScript libraries with known security vulnerabilities
5 vulnerabilities detected
Does not use HTTPS
1 insecure request found
Requests the geolocation permission on page load
Links to cross-origin destinations are unsafe
Passed Audits (10)
Displays images with correct aspect ratio
No browser errors logged to the console
Avoids Application Cache
Allows users to paste into password fields
Avoids requesting the notification permission on page load
Properly defines charset
Avoids deprecated APIs
Detected JavaScript libraries
Page has the HTML doctype
Serves images with appropriate resolution
ny.gov Desktop Progressive Web App
22/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
Is not configured for a custom splash screen
Manifest doesn't have a maskable icon
Does not set a theme color for the address bar.
Fast and reliable
`start_url` does not respond with a 200 when offline
Current page does not respond with a 200 when offline
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 18.6 s
Installable
Does not register a service worker that controls page and `start_url`
Web app manifest does not meet the installability requirements
Does not use HTTPS
1 insecure request found
Passed Audits (4)
Redirects HTTP traffic to HTTPS
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
Contains some content when JavaScript is not available
Provides a valid `apple-touch-icon`
ny.gov Desktop Accessibility
90/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 (3)
Names and labels
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.
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Passed Audits (21)
`[role]` values are valid
Form elements have associated labels
`[aria-*]` attributes match their roles
The page contains a heading, skip link, or landmark region
`[id]` attributes on active, focusable elements are unique
Document has a `<title>` element
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
`[role]`s have all required `[aria-*]` attributes
Image elements have `[alt]` attributes
ARIA IDs are unique
`[role]`s are contained by their required parent element
`[aria-*]` attributes are valid and not misspelled
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
`<html>` element has a valid value for its `[lang]` attribute
`[aria-*]` attributes have valid values
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
`[aria-hidden="true"]` is not present on the document `<body>`
`<html>` element has a `[lang]` attribute
Heading elements appear in a sequentially-descending order
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Desktop Speed
70/100
These checks analyze the performance of ny.gov on desktop devices and return PageSpeed score and information on how to improve the load time. What makes a good Progressive Web App?
Should Fix (5)
Optimize images
Eliminate render-blocking JavaScript and CSS in above-the-fold content
Leverage browser caching
Minify CSS
Minify JavaScript
Passed Audits (5)
Avoid landing page redirects
Enable compression
Reduce server response time
Minify HTML
Prioritize visible content
www.ny.com
www.ny.net
www.ny.org
www.ny.info
www.ny.biz
www.ny.us
www.ny.mobi
www.y.gov
www.ny.gov
www.by.gov
www.nby.gov
www.bny.gov
www.hy.gov
www.nhy.gov
www.hny.gov
www.jy.gov
www.njy.gov
www.jny.gov
www.my.gov
www.nmy.gov
www.mny.gov
www.n.gov
www.nt.gov
www.nyt.gov
www.nty.gov
www.ng.gov
www.nyg.gov
www.ngy.gov
www.nh.gov
www.nyh.gov
www.nu.gov
www.nyu.gov
www.nuy.gov
www.ny.net
www.ny.org
www.ny.info
www.ny.biz
www.ny.us
www.ny.mobi
www.y.gov
www.ny.gov
www.by.gov
www.nby.gov
www.bny.gov
www.hy.gov
www.nhy.gov
www.hny.gov
www.jy.gov
www.njy.gov
www.jny.gov
www.my.gov
www.nmy.gov
www.mny.gov
www.n.gov
www.nt.gov
www.nyt.gov
www.nty.gov
www.ng.gov
www.nyg.gov
www.ngy.gov
www.nh.gov
www.nyh.gov
www.nu.gov
www.nyu.gov
www.nuy.gov