Lynnma.gov Site Title

Default Home Redirect Page

Lynnma.gov Test Results

Lynnma.gov Mobile Performance: 26/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce the impact of third-party code
Third-party code blocked the main thread for 3,720 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
Eliminate render-blocking resources
Potential savings of 4,400 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Defer offscreen images
Potential savings of 116 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Reduce JavaScript execution time
7.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 72 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Serve images in next-gen formats
Potential savings of 1,390 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Avoid an excessive DOM size
2,842 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Reduce unused CSS
Potential savings of 64 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.
Reduce initial server response time
Root document took 1,820 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.
Properly size images
Potential savings of 13 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Largest Contentful Paint element
26,090 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Minimize main-thread work
16.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Minify JavaScript
Potential savings of 25 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Avoid multiple page redirects
Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused JavaScript
Potential savings of 1,481 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.
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
Avoid enormous network payloads
Total size was 6,953 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Serve static assets with an efficient cache policy
113 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Minify CSS
Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Max Potential First Input Delay
870 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Time to Interactive
29.6 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.
First Meaningful Paint
7.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

Lynnma.gov Mobile SEO: 77/100
Quick overview:
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
2 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
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

Lynnma.gov Mobile Best Practices: 41/100
Quick overview:
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
General
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Uses third-party cookies
1 cookie found
Support for third-party cookies will be removed in a future version of Chrome. Learn more about phasing out third-party cookies.
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Uses deprecated APIs
2 warnings found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Lynnma.gov Mobile Accessibility: 77/100
Quick overview:
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
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
`[role]` values are not valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.
Elements use prohibited ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
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.
Image elements have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the `alt` attribute.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
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.
Similar tests
www.lynnma.com
www.lynnma.net
www.lynnma.org
www.lynnma.info
www.lynnma.biz
www.lynnma.us
www.lynnma.mobi
www.ynnma.gov
www.lynnma.gov
www.pynnma.gov
www.lpynnma.gov
www.plynnma.gov
www.oynnma.gov
www.loynnma.gov
www.olynnma.gov
www.kynnma.gov
www.lkynnma.gov
www.klynnma.gov
www.lnnma.gov
www.ltnnma.gov
www.lytnnma.gov
www.ltynnma.gov
www.lgnnma.gov
www.lygnnma.gov
www.lgynnma.gov
www.lhnnma.gov
www.lyhnnma.gov
www.lhynnma.gov
www.lunnma.gov
www.lyunnma.gov
www.luynnma.gov
www.lynma.gov
www.lybnma.gov
www.lynbnma.gov
www.lybnnma.gov
www.lyhnma.gov
www.lynhnma.gov
www.lyjnma.gov
www.lynjnma.gov
www.lyjnnma.gov
www.lymnma.gov
www.lynmnma.gov
www.lymnnma.gov
www.lynbma.gov
www.lynnbma.gov
www.lynhma.gov
www.lynnhma.gov
www.lynjma.gov
www.lynnjma.gov
www.lynmma.gov
www.lynnmma.gov
www.lynna.gov
www.lynnna.gov
www.lynnmna.gov
www.lynnnma.gov
www.lynnja.gov
www.lynnmja.gov
www.lynnka.gov
www.lynnmka.gov
www.lynnkma.gov
www.lynnm.gov
www.lynnmq.gov
www.lynnmaq.gov
www.lynnmqa.gov
www.lynnmw.gov
www.lynnmaw.gov
www.lynnmwa.gov
www.lynnms.gov
www.lynnmas.gov
www.lynnmsa.gov
www.lynnmz.gov
www.lynnmaz.gov
www.lynnmza.gov
Last Tested: