Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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.

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.

Request	Cache TTL	Transfer Size
seattle.gov/images/Departments/Court/Homepage/2021JudgesGroup_300x300.png	300.0 s	137.3 KiB
seattle.gov/cms_resources/js/Subsetter/solid.min.js	300.0 s	100.4 KiB
seattle.gov/cms_resources/pe/SeattleText-Bold-V3.woff	300.0 s	92.7 KiB
/libraries/Ctujouh4.js?exp=1776894828464&sig=4a311810a7c0...	180.0 s	66.2 KiB
seattle.gov/cms_resources/pe/sea-global.js	300.0 s	61.5 KiB
seattle.gov/images/Global/Home_Parks_Spring_Programs_Promo.jpg	300.0 s	53.7 KiB
seattle.gov/cms_resources/pe/sea-global.css	300.0 s	20.4 KiB
seattle.gov/cms_resources/js/Subsetter/light.min.js	300.0 s	18.6 KiB
seattle.gov/cms_resources/js/Subsetter/fontawesome.min.js	300.0 s	15.7 KiB
siteimproveanalytics.com/js/siteanalyze_15203573.js	86400.0 s	31.5 KiB
www.trumba.com/scripts/spuds.js	0.0 ms	12.5 KiB
seattle.gov/cms_resources/js/Subsetter/regular.min.js	300.0 s	10.2 KiB
/images/Council/Citywide Circle Headshots/Council Image T...	300.0 s	6.9 KiB
seattle.gov/cms_resources/js/Subsetter/brands.min.js	300.0 s	6.8 KiB
/images/Departments/CityAttorney/SeattleHome/evans_citywi...	300.0 s	6.7 KiB
/images/MayorWilson/CitywideHomePage/mayor_wilson_citywid...	300.0 s	6.3 KiB
seattle.gov/cms_resources/js/siteimprove_analytics.js	300.0 s	829 B

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.

URL	Est Savings
seattle.gov/cms_resources/pe/SeattleText-Bold-V3.woff	300 ms
/s/opensans/v44/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...	45 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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:11.236 source:map[column:8891 line:1 type:source-location url:https://siteimproveanalytics.com/js/siteanalyze_15203573.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:39.014 source:map[column:33931 line:5 type:source-location url:https://seattle.gov/cms_resources/js/Subsetter/fontawesome.min.js urlProvider:network]] map[reflowTime:11.236 source:map[column:54694 line:0 type:source-location url:https://siteimproveanalytics.com/js/siteanalyze_15203573.js urlProvider:network]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG

nodeLabel: Children in colorful clothing climb steps on a forest trail in Seattle

path: 1,HTML,1,BODY,5,MAIN,0,DIV,0,DIV,3,UL,0,LI,0,ARTICLE,3,PICTURE,0,IMG

selector: li > article.card > picture > img.thumbnail

snippet: <img class="thumbnail" loading="lazy" src="/images/Global/Home_Parks_Spring_Programs_Promo.jpg" alt="Children in colorful clothing climb steps on a forest trail in Seattle">

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

value: no origins were preconnected

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

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.

URL	Transfer Size	Duration
seattle.gov/cms_resources/pe/sea-global.css	20.4 KiB	333 ms
www.trumba.com/scripts/spuds.js	12.5 KiB	1.3 s
/libraries/Ctujouh4.js?exp=1776894828464&sig=4a311810a7c0...	66.2 KiB	2.1 s
fonts.googleapis.com/css?family=Open+Sans:400,700,800,600,300	2.3 KiB	832 ms
seattle.gov/cms_resources/js/siteimprove_analytics.js	829 B

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.

	URL	Resource Size	Est Savings
li > article.card > div.avatar > img `li > article.card > div.avatar > img`	seattle.gov/images/Departments/Court/Homepage/2021JudgesGroup_300x300.png	136.5 KiB	133.9 KiB
Children in colorful clothing climb steps on a forest trail in Seattle `li > article.card > picture > img.thumbnail`	seattle.gov/images/Global/Home_Parks_Spring_Programs_Promo.jpg	53.1 KiB	34.2 KiB

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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: 2.3 s 311.0 KiB

URL	Transfer Size	Est Savings
/_/translate_http/_/js/k=translate_http.tr.es.eNjH1Jo6ldQ...	118.2 KiB	93.6 KiB
www.googletagmanager.com/gtag/js?id=G-CGFRM1LP6G&cx=c&gtm=4e64k0	160.0 KiB	64.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-PXQBQ2	159.5 KiB	63.6 KiB
/libraries/Ctujouh4.js?exp=1776894828464&sig=4a311810a7c0...	65.9 KiB	43.6 KiB
siteimproveanalytics.com/js/siteanalyze_15203573.js	30.8 KiB	23.2 KiB
seattle.gov/cms_resources/pe/sea-global.js	61.0 KiB	22.2 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Total CPU Time	Script Evaluation	Script Parse
seattle.gov/	772 ms	9.8 ms	2.5 ms
seattle.gov/cms_resources/js/Subsetter/fontawesome.min.js	491 ms	367 ms	4.4 ms
Unattributable	380 ms	15 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-CGFRM1LP6G&cx=c&gtm=4e64k0	371 ms	304 ms	39 ms
www.googletagmanager.com/gtm.js?id=GTM-PXQBQ2	336 ms	287 ms	45 ms
seattle.gov/cms_resources/js/Subsetter/solid.min.js	259 ms	74 ms	27 ms
seattle.gov/cms_resources/pe/sea-global.js	247 ms	230 ms	1.0 ms
/_/translate_http/_/js/k=translate_http.tr.es.eNjH1Jo6ldQ...	164 ms	120 ms	36 ms
siteimproveanalytics.com/js/siteanalyze_15203573.js	91 ms	31 ms	14 ms
/libraries/Ctujouh4.js?exp=1776894828464&sig=4a311810a7c0...	69 ms	52 ms	15 ms
seattle.gov/cms_resources/js/Subsetter/light.min.js	51 ms	40 ms	4.8 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Category	Time Spent
Script Evaluation	1.6 s
Other	748 ms
Style & Layout	505 ms
Script Parsing & Compilation	206 ms
Rendering	154 ms
Garbage Collection	60 ms
Parse HTML & CSS	58 ms

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 16.7 KiB

URL	Transfer Size	Est Savings
seattle.gov/cms_resources/pe/sea-global.css	19.9 KiB	16.7 KiB

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

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,251 KiB

●User Timing marks and measures 9 user timings

●Avoid long main-thread tasks 10 long tasks found

●Avoid non-composited animations 1 animated element found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 110 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 20 ms

○INP breakdown

○Avoid large layout shifts

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header.bg_blue > div.contained > div.header_subLayout > button#search-btn `header.bg_blue > div.contained > div.header_subLayout > button#search-btn`

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.

○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

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●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

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○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

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○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.

○Skip links are focusable.

○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.

○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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

100

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.

○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 have descriptive text

●Links are crawlable

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

○robots.txt is valid