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 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:57.643 source:map[column:40 line:4346 type:source-location url:https://fantasyteamadvice.com/assets/application-4d48e3e3acd4e131e01be126aecaa727dcf77d0a1fb967e2d1daa14f69b0e531.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.

	URL	Resource Size	Est Savings
div.max-w-[1800px] > div.mx-auto > div.bg-gradient-to-br > div.absolute `div.max-w-[1800px] > div.mx-auto > div.bg-gradient-to-br > div.absolute`	/assets/baseball-stadium-28ce5dfe477b26c12a7c2a5636f36f12...	187.3 KiB	53.5 KiB
KJ's $100,000 winning DraftKings lineup — built with the Fantasy Team Advice DF… `div#features > div.grid > div.bg-surface-secondary > img.rounded-lg`	/assets/DFSWinningLineup-fe2df64aefec2e193b8cbe06eac36e9c...	68.8 KiB	46.6 KiB
FantasyTeamAdvice Logo `body.w-full > div.site-header > a > img.header-logo`	/assets/ftaMiniLogo-20d4b6166dd7860c0005fea1f06422c0eb883...	4.5 KiB	4.4 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:355.978 label:Time to first byte subpart:timeToFirstByte] map[duration:11.327 label:Resource load delay subpart:resourceLoadDelay] map[duration:292.956 label:Resource load duration subpart:resourceLoadDuration] map[duration:1863.311 label:Element render delay subpart:elementRenderDelay]]

lhId: page-0-DIV

nodeLabel: div.max-w-[1800px] > div.mx-auto > div.bg-gradient-to-br > div.absolute

path: 1,HTML,1,BODY,4,MAIN,0,DIV,0,DIV,1,DIV,1,DIV,0,DIV

selector: div.max-w-[1800px] > div.mx-auto > div.bg-gradient-to-br > div.absolute

snippet: <div class="absolute inset-0 opacity-20 bg-cover bg-center" style="background-image: url("/assets/baseball-stadium-28ce5dfe477b26c12a7c2a5636…");">

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
fonts.googleapis.com/css2?family=Inter:wght@500;600;700;800;900&display=swap	1.2 KiB	871 ms

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

Diagnostics

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: 450 ms 90.1 KiB

URL	Transfer Size	Est Savings
/assets/application-4d48e3e3acd4e131e01be126aecaa727dcf77...	324.2 KiB	90.1 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: 1.8 s 340.6 KiB

URL	Transfer Size	Est Savings
/assets/application-4d48e3e3acd4e131e01be126aecaa727dcf77...	323.8 KiB	271.8 KiB
accounts.google.com/gsi/client	95.6 KiB	68.8 KiB

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

●Max Potential First Input Delay 70 ms

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP request discovery

●Modern HTTP

●Network dependency tree

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

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

●JavaScript execution time 0.3 s

●Minimizes main-thread work 1.0 s

●Avoid long main-thread tasks 3 long tasks found

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

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 170 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 340 ms

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

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

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
We use cookies to improve your experience. By clicking "Accept", you agree to o… `body.w-full > div.fixed`

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. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Log In `body.w-full > div.site-header > div.flex > a.btn`
Crush daily MLB DFS contests with our advanced lineup optimizer. Get pitcher/hi… `div.py-8 > div.container > div.max-w-4xl > p.text-base`
Six premium tools that give FTA+ members an edge on player props, PrizePicks en… `div.container > div.max-w-6xl > div.text-center > p.text-lg`
Today's best +EV NBA player props ranked by edge. Per-minute projections compar… `div.max-w-6xl > div.grid > div.bg-white/5 > p.text-on-surface-subtle`
Daily NBA MORE/LESS picks with confidence ratings and transparent hit rate trac… `div.max-w-6xl > div.grid > div.bg-white/5 > p.text-on-surface-subtle`
Proprietary EFF, HV, and PROD ratings across L1 through season windows. Compare… `div.max-w-6xl > div.grid > div.bg-white/5 > p.text-on-surface-subtle`
See how every NBA defense performs against each position. Color-coded matchup g… `div.max-w-6xl > div.grid > div.bg-white/5 > p.text-on-surface-subtle`
Complete player pages with per-minute stat projections, live prop lines from 4 … `div.max-w-6xl > div.grid > div.bg-white/5 > p.text-on-surface-subtle`
Projected pace, pace boosts, offensive/defensive ratings, and calculated target… `div.max-w-6xl > div.grid > div.bg-white/5 > p.text-on-surface-subtle`

These are opportunities to improve the legibility of your content.

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
DFS Lineup Optimizer for DraftKings, FanDuel & Yahoo `div.space-y-6 > div.flex > div > h4.text-base`
Weekly — $9.99/week `div.bg-white/5 > div.space-y-4 > div > h4.text-lg`
Site Links `body.w-full > div.footer > div.link-container > h4`

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
Homepage `div.footer > div.link-container > div > a`
Contact Us `div.footer > div.link-container > div > a`
Mock Draft `div.footer > div.link-container > div > a`
MLB Props Today `div.footer > div.link-container > div > a`
MLB Top Stacks Today `div.footer > div.link-container > div > a`
MLB DFS Hub `div.footer > div.link-container > div > a`
MLB DFS Picks `div.footer > div.link-container > div > a`
DraftKings MLB Picks `div.footer > div.link-container > div > a`
FanDuel MLB Picks `div.footer > div.link-container > div > a`
DraftKings MLB Props `div.footer > div.link-container > div > a`
FanDuel MLB Props `div.footer > div.link-container > div > a`
BetMGM MLB Props `div.footer > div.link-container > div > a`
Caesars MLB Props `div.footer > div.link-container > div > a`
MLB Park Factors `div.footer > div.link-container > div > a`
Batter vs Pitcher `div.footer > div.link-container > div > a`
MLB Batting Splits `div.footer > div.link-container > div > a`
MLB Stat Leaders `div.footer > div.link-container > div > a`
MLB Pitcher Matchups `div.footer > div.link-container > div > a`
MLB Player Comparison `div.footer > div.link-container > div > a`
MLB Fantasy Calculator `div.footer > div.link-container > div > a`
MLB Hot & Cold Players `div.footer > div.link-container > div > a`
NHL Optimizer `div.footer > div.link-container > div > a`
NHL Player Search `div.footer > div.link-container > div > a`
Popular NHL Players `div.footer > div.link-container > div > a`
NHL Ownerships `div.footer > div.link-container > div > a`
NHL Starting Lineups `div.footer > div.link-container > div > a`
DraftKings NHL Picks `div.footer > div.link-container > div > a`
FanDuel NHL Picks `div.footer > div.link-container > div > a`

These items highlight common accessibility best practices.

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

●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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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

○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

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

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

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

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.

Source	Description
fantasyteamadvice.com/	`Not signed in with the identity provider.`

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
/assets/application-4d48e3e3acd4e131e01be126aecaa727dcf77...

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

○Redirects HTTP traffic to HTTPS

○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
fantasyteamadvice.com/privacy_policy	Learn more

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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`