Skip to content
https://itv.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

29

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.

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.

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:63.563 source:map[column:4826 line:1 type:source-location url:https://www.itv.com/hades-assets/_next/static/chunks/framework-a7264b46c4efe961.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:56.289 source:map[column:870562 line:0 type:source-location url:https://www.itv.com/hades-assets/_next/static/chunks/pages/_app-3a42f66cfa72259a.js urlProvider:network]] map[reflowTime:7.274 source:map[column:629711 line:0 type:source-location url:https://www.itv.com/hades-assets/_next/static/chunks/pages/_app-3a42f66cfa72259a.js urlProvider:network]]]

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.

URLResource SizeEst Savings
The Murder Line div.cp_pill-hero > div.cp_pill-hero__background > picture.cp_picture > img.cp_picture__img
/v2/images/programme/r7z21bl/itv_hub/03_Hero_Mobile/3x4?d...124.0 KiB97.0 KiB
The Real Housewives of Cheshire div.cp_pill-hero > div.cp_pill-hero__background > picture.cp_picture > img.cp_picture__img
/v2/images/series/rg5hrcb/itv_hub/03_Hero_Mobile/3x4?dist...75.6 KiB59.1 KiB
The Assembly div.cp_pill-hero > div.cp_pill-hero__background > picture.cp_picture > img.cp_picture__img
/v2/images/episode/2hwncfc/itv_hub/03_Hero_Mobile/3x4?dis...40.5 KiB31.7 KiB
article.cp_portrait-tile > div.cp_portrait-tile__body > picture.cp_picture > img.cp_picture__img article.cp_portrait-tile > div.cp_portrait-tile__body > picture.cp_picture > img.cp_picture__img
/v2/images/film/7lcxgpf/itv_hub/07_RailTilePortrait/2x3?d...27.7 KiB24.4 KiB
article.cp_portrait-tile > div.cp_portrait-tile__body > picture.cp_picture > img.cp_picture__img article.cp_portrait-tile > div.cp_portrait-tile__body > picture.cp_picture > img.cp_picture__img
/v2/images/series/ssqqvtg/itv_hub/07_RailTilePortrait/2x3...24.9 KiB21.8 KiB
article.cp_portrait-tile > div.cp_portrait-tile__body > picture.cp_picture > img.cp_picture__img article.cp_portrait-tile > div.cp_portrait-tile__body > picture.cp_picture > img.cp_picture__img
/v2/images/programme/r7z21bl/itv_hub/07_RailTilePortrait/...17.8 KiB15.6 KiB
article.cp_portrait-tile > div.cp_portrait-tile__body > picture.cp_picture > img.cp_picture__img article.cp_portrait-tile > div.cp_portrait-tile__body > picture.cp_picture > img.cp_picture__img
/v2/images/programme/1k6vbqv/itv_hub/07_RailTilePortrait/...17.6 KiB15.4 KiB
article.cp_portrait-tile > div.cp_portrait-tile__body > picture.cp_picture > img.cp_picture__img article.cp_portrait-tile > div.cp_portrait-tile__body > picture.cp_picture > img.cp_picture__img
/v2/images/programme/0z1hnkw/itv_hub/07_RailTilePortrait/...15.5 KiB13.6 KiB
article.cp_portrait-tile > div.cp_portrait-tile__body > picture.cp_picture > img.cp_picture__img article.cp_portrait-tile > div.cp_portrait-tile__body > picture.cp_picture > img.cp_picture__img
/v2/images/series/rg5hrcb/itv_hub/07_RailTilePortrait/2x3...14.2 KiB12.4 KiB
The Murder Line div.cp_pill-hero > div.cp_pill-hero__logo_container > picture.cp_picture > img.cp_picture__img
/v2/images/programme/r7z21bl/itv_hub/09_TitleLogo/default...12.7 KiB12.1 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:395.097 label:Time to first byte subpart:timeToFirstByte] map[duration:828.059 label:Resource load delay subpart:resourceLoadDelay] map[duration:74.113 label:Resource load duration subpart:resourceLoadDuration] map[duration:1280.703 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: The Murder Line
path: 1,HTML,1,BODY,1,DIV,0,DIV,0,DIV,2,MAIN,0,DIV,0,DIV,0,DIV,2,DIV,1,DIV,1,A,0,DIV,0,DIV,0,PICTURE,4,IMG
selector: div.cp_pill-hero > div.cp_pill-hero__background > picture.cp_picture > img.cp_picture__img
snippet: <img alt="The Murder Line" class="cp_picture__img cp_pill-hero__background__image" srcset="https://ovp.itv.com/v2/images/programme/r7z21bl/itv_hub/03_Hero_Mobile/3x4…" src="https://ovp.itv.com/v2/images/programme/r7z21bl/itv_hub/03_Hero_Mobile/3x4…">

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: The Murder Line
path: 1,HTML,1,BODY,1,DIV,0,DIV,0,DIV,2,MAIN,0,DIV,0,DIV,0,DIV,2,DIV,1,DIV,1,A,0,DIV,0,DIV,0,PICTURE,4,IMG
selector: div.cp_pill-hero > div.cp_pill-hero__background > picture.cp_picture > img.cp_picture__img
snippet: <img alt="The Murder Line" class="cp_picture__img cp_pill-hero__background__image" srcset="https://ovp.itv.com/v2/images/programme/r7z21bl/itv_hub/03_Hero_Mobile/3x4…" src="https://ovp.itv.com/v2/images/programme/r7z21bl/itv_hub/03_Hero_Mobile/3x4…">

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.

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.

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: 878 ms
URLTime Spent
itv.com/878 ms
www.itv.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 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: 690 ms 68.9 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

CategoryTime Spent
Script Evaluation4.1 s
Other818 ms
Style & Layout501 ms
Script Parsing & Compilation343 ms
Garbage Collection220 ms
Parse HTML & CSS138 ms
Rendering75 ms

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

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 4.3 KiB
URLTransfer SizeEst Savings
assets.fe.itv.com/cookies-prompt/cassie-v2.css24.2 KiB4.3 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 15.3 KiB
URLTransfer SizeEst Savings
app.10ft.itv.com/itvstatic/assets/cookies-prompt/cassie-init-v2.js37.7 KiB15.3 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
The Real Housewives of Cheshire div.cp_pill-hero > div.cp_pill-hero__logo_container > picture.cp_picture > img.cp_picture__img
/v2/images/programme/2psb31k/itv_hub/09_TitleLogo/default...
The Real Housewives of Cheshire div.cp_pill-hero > div.cp_pill-hero__logo_container > picture.cp_picture > img.cp_picture__img
/v2/images/programme/2psb31k/itv_hub/09_TitleLogo/default...
The Assembly div.cp_pill-hero > div.cp_pill-hero__logo_container > picture.cp_picture > img.cp_picture__img
/v2/images/programme/zz38m74/itv_hub/09_TitleLogo/default...
The Murder Line div.cp_pill-hero > div.cp_pill-hero__logo_container > picture.cp_picture > img.cp_picture__img
/v2/images/programme/r7z21bl/itv_hub/09_TitleLogo/default...
The Murder Line div.cp_pill-hero > div.cp_pill-hero__logo_container > picture.cp_picture > img.cp_picture__img
/v2/images/programme/r7z21bl/itv_hub/09_TitleLogo/default...

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

●Layout shift culprits
●Optimize DOM size
●Optimize viewport for mobile
●Avoids enormous network payloads Total size was 2,293 KiB
●User Timing marks and measures 21 user timings
●Avoid long main-thread tasks 20 long tasks found
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 130 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 240 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○Avoid non-composited animations
86

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Cookie choices We use cookies and similar technologies to provide our services… body.app_body > div#cassie-widget
Cookie choices We use cookies and similar technologies to provide our services… body.app_body > div#cassie-widget > div.cassie-cookie-module > div.cassie-pre-banner

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy & Cookie Information div.cassie-pre-banner > p#cassie_pre_banner_text > p > a#cookie-policy-link

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookie choices We use cookies and similar technologies to provide our services… body.app_body > div#cassie-widget > div.cassie-cookie-module > div.cassie-pre-banner

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Navigate to item 2 div > div.cp_pill-hero-slider-browser > div.cp_pill-hero-slider-browser__navigation > span.cp_pill-hero-slider-browser__navigation__dot
Navigate to item 3 div > div.cp_pill-hero-slider-browser > div.cp_pill-hero-slider-browser__navigation > span.cp_pill-hero-slider-browser__navigation__dot

These items highlight common accessibility best practices.

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
New series - stream every episode DRAMA CRIME & THRILLER SERIES 1 div.cp_pill-hero-slider-browser > div.cp_pill-hero-slider-browser__container > div.cp_pill-hero-slider-browser__container__wrapper-item > a#pill-hero-slide-1
○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
●Buttons have an accessible name
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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
○`<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
○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.
92

Best Practices

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.

SourceDescription
Error: Minified React error #418; visit https://react.dev/errors/418?args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at rv (https://www.itv.com/hades-assets/_next/static/chunks/framework-a7264b46c4efe961.js:1:37618) at rb (https://www.itv.com/hades-assets/_next/static/chunks/framework-a7264b46c4efe961.js:1:38579) at https://www.itv.com/hades-assets/_next/static/chunks/framework-a7264b46c4efe961.js:1:122280 at uu (https://www.itv.com/hades-assets/_next/static/chunks/framework-a7264b46c4efe961.js:1:126529) at ua (https://www.itv.com/hades-assets/_next/static/chunks/framework-a7264b46c4efe961.js:1:118931) at https://www.itv.com/hades-assets/_next/static/chunks/framework-a7264b46c4efe961.js:1:118715 at ul (https://www.itv.com/hades-assets/_next/static/chunks/framework-a7264b46c4efe961.js:1:118723) at i3 (https://www.itv.com/hades-assets/_next/static/chunks/framework-a7264b46c4efe961.js:1:115084) at uT (https://www.itv.com/hades-assets/_next/static/chunks/framework-a7264b46c4efe961.js:1:135686) at MessagePort.z (https://www.itv.com/hades-assets/_next/static/chunks/framework-a7264b46c4efe961.js:1:5060)
Framing 'https://gtm.bde.itv.com/' violates the following report-only Content Security Policy directive: "frame-src 'self' *.facebook.net *.facebook.com *.flashtalking.com *.stripe.com bugcrowd.com". The violation has been logged, but no further action has been taken.
Framing 'https://gtm.bde.itv.com/' violates the following report-only Content Security Policy directive: "frame-src 'self' *.facebook.net *.facebook.com *.flashtalking.com *.stripe.com bugcrowd.com". The violation has been logged, but no further action has been taken.
Target cookie not found
Target cookie not found
Target cookie not found
Target cookie not found
Target cookie not found
Target cookie not found
Target cookie not found
Target cookie not found

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

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.

●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
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
○Redirects HTTP traffic to HTTPS
92

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.

Crawling and Indexing

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

To appear in search results, crawlers need access to your app.

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

Send Feedback