Skip to content
https://logotyp.us

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.

41

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.

RequestCache TTLTransfer Size
logotyp.us/file/super-bowl.svg345600.0 s184.4 KiB
logotyp.us/file/tennessee-titans.svg345600.0 s147.4 KiB
/pagead/managed/js/adsense/m202609290101/show_ads_impl_fy...1209600.0 s163.6 KiB
logotyp.us/file/olympics-2026-milano.svg345600.0 s47.0 KiB
logotyp.us/file/canara-bank.svg345600.0 s40.1 KiB
logotyp.us/cdn-cgi/challenge-platform/h/b/scripts/jsd/d76008a69eab/main.js?14400.0 s9.5 KiB
/beacon.min.js/v31edd6df95cf4e85bb4c19e7a9bdbcba178836298...86400.0 s10.1 KiB
/css/style.min.7a16b840d88d0019ea193898d919a31b63248e0b1f...345600.0 s17.2 KiB
logotyp.us/pagefind/pagefind.js345600.0 s13.4 KiB
logotyp.us/file/tampa-bay-buccaneers.svg345600.0 s12.4 KiB
logotyp.us/file/olympics-1980-lake-placid.svg345600.0 s11.8 KiB
logotyp.us/fonts/figtree-600.woff2345600.0 s11.7 KiB
logotyp.us/fonts/figtree-400.woff2345600.0 s11.7 KiB
logotyp.us/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js172789.0 s4.4 KiB
logotyp.us/file/olympics-1994-lillehammer.svg345600.0 s7.4 KiB
logotyp.us/file/olympics-2006-torino.svg345600.0 s6.4 KiB
logotyp.us/file/olympics-1988-calgary.svg345600.0 s6.2 KiB
logotyp.us/file/philadelphia-eagles.svg345600.0 s5.5 KiB
/js/presence.min.aff17592ae2bc643bcac928b3374d5d29081853a...345600.0 s5.0 KiB
logotyp.us/file/united-airlines.svg345600.0 s4.9 KiB
logotyp.us/file/new-york-jets.svg345600.0 s4.8 KiB
logotyp.us/file/olympics-1998-nagano.svg345600.0 s4.8 KiB
logotyp.us/file/olympics-1984-sarajevo.svg345600.0 s4.5 KiB
logotyp.us/file/olympics-1972-sapporo.svg345600.0 s4.0 KiB
logotyp.us/img/logotypus.svg345600.0 s3.7 KiB
logotyp.us/file/olympics-2010-vancouver.svg345600.0 s3.5 KiB
/js/core.min.85c2f82a235a8719abbf65449a5ef8d831958136aea5...345600.0 s3.5 KiB
logotyp.us/file/microsoft.svg345600.0 s3.3 KiB
logotyp.us/file/new-orleans-saints.svg345600.0 s2.9 KiB
logotyp.us/file/stifel.svg345600.0 s2.8 KiB
logotyp.us/file/walmart.svg345600.0 s2.6 KiB
logotyp.us/file/amazon.svg345600.0 s2.5 KiB
logotyp.us/file/nfl.svg345600.0 s2.4 KiB
logotyp.us/file/49ers.svg345600.0 s2.3 KiB
logotyp.us/file/axis-bank.svg345600.0 s2.0 KiB
logotyp.us/file/toyota.svg345600.0 s1.9 KiB
logotyp.us/file/vs-code.svg345600.0 s1.7 KiB
logotyp.us/file/samsung.svg345600.0 s1.7 KiB
logotyp.us/file/cisco.svg345600.0 s1.7 KiB
logotyp.us/file/verizon.svg345600.0 s1.5 KiB
logotyp.us/file/roku.svg345600.0 s1.4 KiB
logotyp.us/file/ibm.svg345600.0 s1.4 KiB
logotyp.us/file/facebook.svg345600.0 s1.2 KiB
logotyp.us/file/oracle.svg345600.0 s1.0 KiB

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.

URLEst Savings
/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...105 ms
/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...45 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-IMG
nodeLabel: Super Bowl logo vector
path: 1,HTML,1,BODY,3,MAIN,0,SECTION,0,DIV,0,DIV,0,DIV,0,A,0,IMG
selector: div.spotlight-grid > div.card > a.card-image > img
snippet: <img src="/file/super-bowl.svg" loading="lazy" width="400" height="200" alt="Super Bowl logo vector">

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

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.

URLTransfer SizeDuration
/css/style.min.7a16b840d88d0019ea193898d919a31b63248e0b1f...17.2 KiB450 ms

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

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: 150 ms 26.6 KiB
URLTransfer SizeEst Savings
.fc-consent-root .fc-dialog-container.fc-landscape-mode { height: 90% !important; … } …16.3 KiB14.1 KiB
/css/style.min.7a16b840d88d0019ea193898d919a31b63248e0b1f...16.8 KiB12.5 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: 2.1 s 286.3 KiB
URLTransfer SizeEst Savings
/pagead/managed/js/adsense/m202609290101/show_ads_impl_fy...163.5 KiB129.9 KiB
www.googletagmanager.com/gtag/js?id=G-27GGWYN65W169.9 KiB69.9 KiB
/i/ca-pub-7227473577075297?href=https%3A%2F%2Flogotyp.us&...70.3 KiB35.3 KiB
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js56.2 KiB27.6 KiB
www.gstatic.com/firebasejs/10.8.0/firebase-database-compat.js46.9 KiB23.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.

URLTotal CPU TimeScript EvaluationScript Parse
logotyp.us/1.5 s40 ms2.2 ms
Unattributable1.3 s31 ms0.0 ms
logotyp.us/cdn-cgi/challenge-platform/scripts/jsd/main.js751 ms629 ms20 ms
/i/ca-pub-7227473577075297?href=https%3A%2F%2Flogotyp.us&...400 ms359 ms34 ms
/f/AGSKWxVrAxasls8kaAxHvrS1x37fZXtY6uL4G1HSy0c59C0Ooz38lI...388 ms171 ms50 ms
www.googletagmanager.com/gtag/js?id=G-27GGWYN65W291 ms244 ms45 ms
logotyp.us/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js222 ms120 ms3.9 ms
www.gstatic.com/firebasejs/10.8.0/firebase-database-compat.js176 ms135 ms13 ms
/pagead/managed/js/adsense/m202609290101/show_ads_impl_fy...160 ms120 ms37 ms
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js154 ms109 ms16 ms
/js/presence.min.aff17592ae2bc643bcac928b3374d5d29081853a...75 ms69 ms1.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.

CategoryTime Spent
Script Evaluation2.1 s
Other1.9 s
Style & Layout893 ms
Rendering343 ms
Script Parsing & Compilation228 ms
Parse HTML & CSS105 ms
Garbage Collection75 ms

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
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Avoids enormous network payloads Total size was 1,277 KiB
●Avoid long main-thread tasks 15 long tasks found
●Avoid non-composited animations 2 animated elements 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 200 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 130 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○User Timing marks and measures
88

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Rating: 4.4 out of 5 div.card > div.card-header > div.spotlight-rating > span.spotlight-stars
Rating: 4.6 out of 5 div.card > div.card-header > div.spotlight-rating > span.spotlight-stars

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
Learn more div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label
List of partners. div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog

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
Super Bowl div.spotlight-grid > div.card > div.card-header > h4.card-title

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
Sports div.card > div.card-header > span.card-meta > a
Sports div.card > div.card-header > span.card-meta > a
Sports div.card > div.card-header > span.card-meta > a
Sports div.card > div.card-header > span.card-meta > a
Sports div.card > div.card-header > span.card-meta > a
Sports div.card > div.card-header > span.card-meta > a
Sports div.card > div.card-header > span.card-meta > a
Sports div.card > div.card-header > span.card-meta > a
Sports div.card > div.card-header > span.card-meta > a
Sports div.card > div.card-header > span.card-meta > a
Sports div.card > div.card-header > span.card-meta > a
NFL div.card > div.card-header > h4.card-title > a
Sports div.card > div.card-header > span.card-meta > a
Super Bowl div.card > div.card-header > h4.card-title > a
Sports div.card > div.card-header > span.card-meta > a
Sports div.card > div.card-header > span.card-meta > a
Sports div.card > div.card-header > span.card-meta > a
49ers div.card > div.card-header > h4.card-title > a
Sports div.card > div.card-header > span.card-meta > a
VS Code div.card > div.card-header > h4.card-title > a
Software div.card > div.card-header > span.card-meta > a
Axis Bank div.card > div.card-header > h4.card-title > a
Banking And Finance div.card > div.card-header > span.card-meta > a
Amazon div.card > div.card-header > h4.card-title > a
Technology div.card > div.card-header > span.card-meta > a
Canara Bank div.card > div.card-header > h4.card-title > a
Banking And Finance div.card > div.card-header > span.card-meta > a
Roku div.card > div.card-header > h4.card-title > a
Electronics div.card > div.card-header > span.card-meta > a
IBM div.card > div.card-header > h4.card-title > a
Electronics div.card > div.card-header > span.card-meta > a
Airlines div.card > div.card-header > span.card-meta > a
Stifel div.card > div.card-header > h4.card-title > a
Microsoft div.card > div.card-header > h4.card-title > a
Technology div.card > div.card-header > span.card-meta > a
Toyota div.card > div.card-header > h4.card-title > a
Automotive div.card > div.card-header > span.card-meta > a
Verizon div.card > div.card-header > h4.card-title > a
Telecom div.card > div.card-header > span.card-meta > a
Walmart div.card > div.card-header > h4.card-title > a
Retail div.card > div.card-header > span.card-meta > a
Oracle div.card > div.card-header > h4.card-title > a
Technology div.card > div.card-header > span.card-meta > a
Samsung div.card > div.card-header > h4.card-title > a
Technology div.card > div.card-header > span.card-meta > a
Cisco div.card > div.card-header > h4.card-title > a
Technology div.card > div.card-header > span.card-meta > a
Facebook div.card > div.card-header > h4.card-title > a
Technology div.card > div.card-header > span.card-meta > a
Louis Vuitton div.card > div.card-header > h4.card-title > a
Technology div.card > div.card-header > span.card-meta > a
Disney div.card > div.card-header > h4.card-title > a
Entertainment div.card > div.card-header > span.card-meta > a
IBM div.card > div.card-header > h4.card-title > a
Electronics div.card > div.card-header > span.card-meta > a
Apple div.card > div.card-header > h4.card-title > a
Technology div.card > div.card-header > span.card-meta > a
Intel div.card > div.card-header > h4.card-title > a
Technology div.card > div.card-header > span.card-meta > a
AT&T div.card > div.card-header > h4.card-title > a
Telecom div.card > div.card-header > span.card-meta > a
General Electric div.card > div.card-header > h4.card-title > a
Technology div.card > div.card-header > span.card-meta > a
McDonalds div.card > div.card-header > h4.card-title > a
Restaurants div.card > div.card-header > span.card-meta > 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
●Form elements have associated labels
●`[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
●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
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○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.
77

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 / WarningSource
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
logotyp.us/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge
logotyp.us/cdn-cgi/challenge-platform/scripts/jsd/main.js

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
logotyp.us/
TypeError: Failed to update a ServiceWorker for scope ('https://logotyp.us/') with script ('Unknown'): Not found
●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 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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
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`

Send Feedback