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
i.ytimg.com/vi/IjuGOUn_JBw/sddefault.jpg	7200.0 s	68.9 KiB
consent.cookiebot.com/uc.js?cbid=1aea8925-08ec-43d4-ad52-162129f5ba86	222.0 s	35.7 KiB
static.cdn.prismic.io/prismic.js?new=true&repo=ticket-tailor	0.0 ms	9.8 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...	14400.0 s	13.0 KiB
widget.intercom.io/widget/4frgqf4m	300.0 s	3.6 KiB
js.tickettailor.com/tickettailor-stitching.js	3600.0 s	1.3 KiB
js.tickettailor.com/tickettailor-production.js	3600.0 s	1.2 KiB

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:120.738 source:map[type:text value:[unattributed]]] map[reflowTime:0.686 source:map[column:380 line:580 type:source-location url:https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js urlProvider:network]] map[reflowTime:1.43 source:map[column:47 line:303 type:source-location url:https://www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js urlProvider:network]]]

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

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
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	10 ms

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
div.intercom-lightweight-app > div.intercom-lightweight-app-launcher > div.intercom-lightweight-app-launcher-icon > img.intercom-lightweight-app-launcher-custom-icon-open `div.intercom-lightweight-app > div.intercom-lightweight-app-launcher > div.intercom-lightweight-app-launcher-icon > img.intercom-lightweight-app-launcher-custom-icon-open`	/i/o/4frgqf4m/689147/32d30d532bd5311cf9f81a93b8f4/d4506ed...	32.0 KiB	32.0 KiB
div.video-player__video-wrap > div.video > figure.image > img.video__image__image `div.video-player__video-wrap > div.video > figure.image > img.video__image__image`	/ZnGXG5m069VX12SY_Herothumbnail1.png?auto=format%2Ccompre...	36.7 KiB	27.4 KiB
div.two-column__column > div.two-column__image-wrap > figure.image > img.two-column__image__image `div.two-column__column > div.two-column__image-wrap > figure.image > img.two-column__image__image`	/ZhkiITjCgu4jzx-1_CreateanEvent.png?auto=format%2Ccompres...	15.7 KiB	13.5 KiB
null `div.cta-block__inner > div.cta-block__column > h2.cta-block__title > img.cta-block__title-icon`	/ticket-tailor/65b37a60615e73009ec3f40c_Icon23.png?auto=f...	4.9 KiB	4.4 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

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: 774 ms

URL	Time Spent
tickettailor.com/	774 ms
www.tickettailor.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.

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: 310 ms 78.1 KiB

URL	Transfer Size	Est Savings
www.tickettailor.com/_next/static/css/2771ae339d50cec7.css	53.1 KiB	39.2 KiB
@charset "UTF-8";@import url(https://fonts.googleapis.com/css2?family=Montserrat:wght@500&display=s…	27.1 KiB	27.1 KiB
	13.5 KiB	11.8 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.

Estimated savings: 3.0 s 1.1 MiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	176.2 KiB
js.intercomcdn.com/frame-modern.db2b74ec.js	192.7 KiB	121.9 KiB
/gtm.js?id=GTM-K4B6RL&gtm_auth=Uf1tdGnzovcVuPQ65z3Ddw&gtm...	158.1 KiB	112.6 KiB
/gtm.js?id=GTM-K4B6RL&gtm_auth=Uf1tdGnzovcVuPQ65z3Ddw&gtm...	158.1 KiB	87.6 KiB
js.intercomcdn.com/vendor-modern.80eace52.js	143.3 KiB	85.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-P9676DH2	151.1 KiB	83.1 KiB
www.googletagmanager.com/gtag/destination?id=AW-AW-969936808&cx=c&gtm=4e64h1	134.1 KiB	58.7 KiB
www.tickettailor.com/_next/static/chunks/9307-b7733ed38ad918f8.js	57.6 KiB	57.4 KiB
www.googletagmanager.com/gtag/js?id=AW-969936808&cx=c&gtm=4e64h1	143.5 KiB	55.7 KiB
www.tickettailor.com/_next/static/chunks/eaa36ebd.491d64239365efb8.js	97.0 KiB	47.7 KiB
www.tickettailor.com/_next/static/chunks/6817-88e3984464ba60f5.js	44.6 KiB	43.3 KiB
www.tickettailor.com/_next/static/chunks/7827-22d29d6524d9bea8.js	30.4 KiB	30.3 KiB
/_next/static/chunks/app/[lang]/pricing/page-b8e34d21f8e4...	30.4 KiB	29.7 KiB
www.tickettailor.com/_next/static/chunks/2900-e537ff71b9d21712.js	29.7 KiB	25.7 KiB
www.tickettailor.com/_next/static/chunks/4970-4f22c6dfd5af2df3.js	25.4 KiB	25.2 KiB
/1aea8925-08ec-43d4-ad52-162129f5ba86/cc.js?renew=false&r...	105.4 KiB	24.9 KiB
consent.cookiebot.com/uc.js?cbid=1aea8925-08ec-43d4-ad52-162129f5ba86	35.5 KiB	22.6 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
www.tickettailor.com/	2.3 s	190 ms	104 ms
Unattributable	1.4 s	59 ms	0.0 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	1.4 s	1.2 s	141 ms
www.tickettailor.com/_next/static/chunks/2570-7a8d28e54fe70fec.js	1.0 s	155 ms	9.2 ms
js.intercomcdn.com/frame-modern.db2b74ec.js	892 ms	707 ms	78 ms
www.tickettailor.com/_next/static/chunks/1255-aab1fab69a431920.js	890 ms	755 ms	18 ms
/1aea8925-08ec-43d4-ad52-162129f5ba86/cc.js?renew=false&r...	653 ms	250 ms	37 ms
www.tickettailor.com/_next/static/chunks/webpack-cc2c82c9fa12c022.js	386 ms	362 ms	1.1 ms
/gtm.js?id=GTM-K4B6RL&gtm_auth=Uf1tdGnzovcVuPQ65z3Ddw&gtm...	352 ms	223 ms	114 ms
www.googletagmanager.com/gtag/js?id=AW-969936808&cx=c&gtm=4e64h1	350 ms	273 ms	69 ms
www.googletagmanager.com/gtag/destination?id=AW-AW-969936808&cx=c&gtm=4e64h1	305 ms	261 ms	37 ms
www.tickettailor.com/cdn-cgi/challenge-platform/scripts/jsd/main.js	305 ms	287 ms	2.9 ms
www.tickettailor.com/_next/static/chunks/c15bf2b0-1894ff94ed039d0f.js	303 ms	36 ms	26 ms
www.tickettailor.com/_next/static/chunks/4bd1b696-182b6b13bdad92e3.js	217 ms	61 ms	17 ms
www.googletagmanager.com/gtm.js?id=GTM-P9676DH2	217 ms	166 ms	46 ms
consent.cookiebot.com/uc.js?cbid=1aea8925-08ec-43d4-ad52-162129f5ba86	207 ms	166 ms	12 ms
www.tickettailor.com/_next/static/chunks/eaa36ebd.491d64239365efb8.js	178 ms	120 ms	58 ms
eomail1.com/form/d2a0f0fa-c5d6-11ee-a1d9-8fe4d440c56a.js	165 ms	91 ms	25 ms
js.intercomcdn.com/vendor-modern.80eace52.js	116 ms	11 ms	81 ms
www.youtube.com/s/player/218d9d92/www-widgetapi.vflset/www-widgetapi.js	103 ms	92 ms	3.6 ms
static.cdn.prismic.io/prismic.js?new=true&repo=ticket-tailor	52 ms	48 ms	3.1 ms
www.tickettailor.com/_next/static/chunks/6203-bd076b314a90452f.js	51 ms	11 ms	28 ms
www.tickettailor.com/_next/static/chunks/4674-f90d1831e5f67f99.js	51 ms	40 ms	5.5 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	5.8 s
Other	2.6 s
Style & Layout	1.7 s
Script Parsing & Compilation	1.0 s
Rendering	566 ms
Parse HTML & CSS	476 ms
Garbage Collection	203 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 reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable
Pages with WebSocket cannot enter back/forward cache.	Pending browser support
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
Back/forward cache is disabled because WebSocket has been used.	Not actionable

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
www.tickettailor.com/	492.7 KiB
www.youtube-nocookie.com/s/player/218d9d92/player_embed_es6.vflset/en_US/base.js	435.8 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	362.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.9 KiB
www.tickettailor.com/_next/static/chunks/8552.68bdb9eea2a92983.js	333.4 KiB
js.intercomcdn.com/frame-modern.db2b74ec.js	193.3 KiB
/s/_/ytembeds/_/js/k=ytembeds.base.en_US.CYE28xQTWxU.2021...	193.0 KiB
/gtm.js?id=GTM-K4B6RL&gtm_auth=Uf1tdGnzovcVuPQ65z3Ddw&gtm...	158.4 KiB
/gtm.js?id=GTM-K4B6RL&gtm_auth=Uf1tdGnzovcVuPQ65z3Ddw&gtm...	158.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-P9676DH2	151.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
div.intercom-lightweight-app > div.intercom-lightweight-app-launcher > div.intercom-lightweight-app-launcher-icon > img.intercom-lightweight-app-launcher-custom-icon-open `div.intercom-lightweight-app > div.intercom-lightweight-app-launcher > div.intercom-lightweight-app-launcher-icon > img.intercom-lightweight-app-launcher-custom-icon-open`	/i/o/4frgqf4m/689147/32d30d532bd5311cf9f81a93b8f4/d4506ed...
null `div.cta-block__inner > div.cta-block__column > h2.cta-block__title > img.cta-block__title-icon`	/ticket-tailor/Zhkl1TjCgu4jzyA0_plugicon.png?auto=format,...
null `div.cta-block__inner > div.cta-block__column > h2.cta-block__title > img.cta-block__title-icon`	/ticket-tailor/65b37a60615e73009ec3f40c_Icon23.png?auto=f...

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

●Layout shift culprits

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 10 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 1 animated element found

●Network Requests

●Network Round Trip Times 70 ms

●Server Backend Latencies 640 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○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
div.video-player__sticky > div.video-player__video-wrap > div.video > button.button `div.video-player__sticky > div.video-player__video-wrap > div.video > button.button`
div.swiper-wrapper > div.swiper-slide > div.testimonials__slide > button.button `div.swiper-wrapper > div.swiper-slide > div.testimonials__slide > button.button`
div.swiper-wrapper > div.swiper-slide > div.testimonials__slide > button.button `div.swiper-wrapper > div.swiper-slide > div.testimonials__slide > button.button`
div.swiper-wrapper > div.swiper-slide > div.testimonials__slide > button.button `div.swiper-wrapper > div.swiper-slide > div.testimonials__slide > button.button`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.video-player__video-wrap > div.video > figure.image > img.video__image__image `div.video-player__video-wrap > div.video > figure.image > img.video__image__image`
div.center-title__inner > div.center-title__column > figure.image > img.accent__image `div.center-title__inner > div.center-title__column > figure.image > img.accent__image`
div.two-column__column > div.two-column__image-wrap > figure.image > img.two-column__image__image `div.two-column__column > div.two-column__image-wrap > figure.image > img.two-column__image__image`
div.two-column__column > div.two-column__image-wrap > figure.image > img.two-column__image__image `div.two-column__column > div.two-column__image-wrap > figure.image > img.two-column__image__image`
div.two-column__column > div.two-column__image-wrap > figure.image > img.two-column__image__image `div.two-column__column > div.two-column__image-wrap > figure.image > img.two-column__image__image`
div.accordion__slide-overflow > div.accordion__column > figure.image > img.image__image `div.accordion__slide-overflow > div.accordion__column > figure.image > img.image__image`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.page--home > header.header > div.header__container > a.header__logo `body.page--home > header.header > div.header__container > a.header__logo`
div.footer__top > div.footer__column > div.footer__socials-icons > a.footer__socials-icon `div.footer__top > div.footer__column > div.footer__socials-icons > a.footer__socials-icon`
div.footer__top > div.footer__column > div.footer__socials-icons > a.footer__socials-icon `div.footer__top > div.footer__column > div.footer__socials-icons > a.footer__socials-icon`
div.footer__top > div.footer__column > div.footer__socials-icons > a.footer__socials-icon `div.footer__top > div.footer__column > div.footer__socials-icons > a.footer__socials-icon`
div.footer__top > div.footer__column > div.footer__socials-icons > a.footer__socials-icon `div.footer__top > div.footer__column > div.footer__socials-icons > a.footer__socials-icon`
div.footer__top > div.footer__column > div.footer__socials-icons > a.footer__socials-icon `div.footer__top > div.footer__column > div.footer__socials-icons > a.footer__socials-icon`
div.footer__top > div.footer__column > div.footer__socials-icons > a.footer__socials-icon `div.footer__top > div.footer__column > div.footer__socials-icons > a.footer__socials-icon`

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Don’t just take our word for it! `div.container > div.hero-banner__inner > div.hero-banner__column > h3.hero-banner__subtitle`
How it works `section.center-title > div.center-title__container > div.center-title__inner > h4.center-title__subtitle`
Get inspired `div.discover-events__container > div.discover-events__inner > div.discover-events__column > h4.discover-events__subtitle`

These are opportunities to improve keyboard navigation in your application.

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
Site credit. `div.footer__inner > div.footer__bottom > div.footer__column > 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

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

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

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

●`[lang]` attributes have a valid value

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

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
SharedStorage	www.tickettailor.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	www.tickettailor.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge	www.tickettailor.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

●Uses HTTPS

●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

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.tickettailor.com/first-timers	Learn more
www.tickettailor.com/event-pros	Learn more
www.tickettailor.com/free-events	Learn more
www.tickettailor.com/developers	Learn more
www.tickettailor.com/charities	Learn more
www.tickettailor.com/tours-and-attractions	Learn more

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.video-player__video-wrap > div.video > figure.image > img.video__image__image `div.video-player__video-wrap > div.video > figure.image > img.video__image__image`
div.center-title__inner > div.center-title__column > figure.image > img.accent__image `div.center-title__inner > div.center-title__column > figure.image > img.accent__image`
div.two-column__column > div.two-column__image-wrap > figure.image > img.two-column__image__image `div.two-column__column > div.two-column__image-wrap > figure.image > img.two-column__image__image`
div.two-column__column > div.two-column__image-wrap > figure.image > img.two-column__image__image `div.two-column__column > div.two-column__image-wrap > figure.image > img.two-column__image__image`
div.two-column__column > div.two-column__image-wrap > figure.image > img.two-column__image__image `div.two-column__column > div.two-column__image-wrap > figure.image > img.two-column__image__image`
div.accordion__slide-overflow > div.accordion__column > figure.image > img.image__image `div.accordion__slide-overflow > div.accordion__column > figure.image > img.image__image`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○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 are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`