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.

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.

URL	Est Savings
www.roku.com/intl/s/1741383521562/fonts/glyphicons-roku.woff	140 ms

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-DIV

nodeLabel: Roku Happy Streaming logo

path: 1,HTML,1,BODY,2,DIV,1,DIV,0,SECTION,0,DIV

selector: div#kitchensink-root > div#ks-page-content-container > section.ks-wrapper > div.intl-imagewrapper

snippet: <div class="intl-imagewrapper">

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

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
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
/beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312...	86400.0 s	10.7 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.

	URL	Resource Size	Est Savings
Australia Flag Icon `div.intl-countrylist > div.intl-item > a.ks-mt-20 > img`	image.roku.com/w/images/hero/flags/AU.jpg	22.9 KiB	22.7 KiB
United Kingdom Flag Icon `div.intl-countrylist > div.intl-item > a.ks-mt-20 > img`	image.roku.com/w/images/hero/flags/UK.jpg	17.8 KiB	17.5 KiB
Roku Happy Streaming logo `div#ks-page-content-container > section.ks-wrapper > div.intl-imagewrapper > img`	image.roku.com/w/images/hero/roku-logo.png	23.7 KiB	16.8 KiB
United States Flag Icon `div.intl-countrylist > div.intl-item > a.ks-mt-20 > img`	image.roku.com/w/images/hero/flags/US.jpg	14.3 KiB	14.1 KiB
Brazil Flag Icon `div.intl-countries > div.col1 > a.ks-mt-20 > img`	image.roku.com/w/images/hero/flags/BR.jpg	11.3 KiB	11.0 KiB
Peru Flag Icon `div.intl-countries > div.col2 > a.ks-mt-20 > img`	image.roku.com/w/images/hero/flags/PE.jpg	7.5 KiB	7.2 KiB
Canada Flag Icon `div.intl-countrylist > div.intl-item > a.ks-mt-20 > img`	image.roku.com/w/images/hero/flags/CA.jpg	6.9 KiB	6.7 KiB
Mexico Flag Icon `div.intl-countries > div.col2 > a.ks-mt-20 > img`	image.roku.com/w/images/hero/flags/MX.jpg	6.9 KiB	6.6 KiB
Guatemala Flag Icon `div.intl-countries > div.col2 > a.ks-mt-20 > img`	image.roku.com/w/images/hero/flags/GT.jpg	6.1 KiB	5.9 KiB
Costa Rica Flag Icon `div.intl-countries > div.col1 > a.ks-mt-20 > img`	image.roku.com/w/images/hero/flags/CR.jpg	5.8 KiB	5.6 KiB
Honduras Flag Icon `div.intl-countries > div.col2 > a.ks-mt-20 > img`	image.roku.com/w/images/hero/flags/HN.jpg	5.5 KiB	5.3 KiB
Panama Flag Icon `div.intl-countries > div.col2 > a.ks-mt-20 > img`	image.roku.com/w/images/hero/flags/PA.jpg	5.5 KiB	5.2 KiB
El Salvador Flag Icon `div.intl-countries > div.col1 > a.ks-mt-20 > img`	image.roku.com/w/images/hero/flags/SV.jpg	4.5 KiB	4.3 KiB
Argentina Flag Icon `div.intl-countries > div.col1 > a.ks-mt-20 > img`	image.roku.com/w/images/hero/flags/AR.jpg	4.5 KiB	4.2 KiB
Nicaragua Flag Icon `div.intl-countries > div.col2 > a.ks-mt-20 > img`	image.roku.com/w/images/hero/flags/NI.jpg	4.3 KiB	4.1 KiB

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

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: 1.7 s

URL	Time Spent
roku.com/	805 ms
www.roku.com/	855 ms
www.roku.com/intl?next=/&source=www.roku.com	0.0 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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: 790 ms 127.5 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-TKFC7L4	123.9 KiB	66.4 KiB
www.roku.com/intl/s/1741383521562/runtime/page.js	192.8 KiB	61.1 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.	Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.	Not actionable

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

URL	Transfer Size	Est Savings
/*! normalize.css v3.0.1 \| MIT License \| git.io/normalize...	81.1 KiB	80.1 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
roku `div.mobile-nav-bar > div.mobile-nav-brand > a > img.mobile-nav-brand-logo`	www.roku.com/intl/s/1741383521562/fonts/roku-logo.svg
California Consumer Privacy Act (CCPA) Opt-Out Icon `section.legal-links > a > span.legal-icon > img.ccpa-icon`	image.roku.com/w/assets/privacy-options.png

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 692 KiB

●JavaScript execution time 0.7 s

●Minimizes main-thread work 1.4 s

●Avoid long main-thread tasks 4 long tasks found

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 60 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

100

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Roku, Inc. `div.row > div.col-sm-8 > section.copyright > a`

○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

●`[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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[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 are distinguishable without relying on color.

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

○Buttons have an accessible name

○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

○Heading elements appear in a sequentially-descending order

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

○Form elements have associated labels

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

○Identical links have the same purpose.

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

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
Roku Happy Streaming logo `div#ks-page-content-container > section.ks-wrapper > div.intl-imagewrapper > img`	image.roku.com/w/images/hero/roku-logo.png	210 x 100 (2.10)	665 x 330 (2.02)

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
www.roku.com/intl/s/1741383521562/fonts/Gotham-Book.woff	`Failed to load resource: the server responded with a status of 403 ()`
www.roku.com/intl/s/1741383521562/fonts/Gotham-Medium.woff	`Failed to load resource: the server responded with a status of 403 ()`
www.roku.com/intl/s/1741383521562/fonts/Gotham-Bold.woff	`Failed to load resource: the server responded with a status of 403 ()`
www.roku.com/intl/s/1741383521562/fonts/Gotham-Book.ttf	`Failed to load resource: the server responded with a status of 403 ()`
www.roku.com/intl/s/1741383521562/fonts/Gotham-Bold.ttf	`Failed to load resource: the server responded with a status of 403 ()`
www.roku.com/intl/s/1741383521562/fonts/Gotham-Medium.ttf	`Failed to load resource: the server responded with a status of 403 ()`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.roku.com/intl/s/1741383521562/runtime/page.js

●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

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●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

○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

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`