Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
/s/opensans/v40/memvYaGs126MiZpBA-UvWbX2vVnXBbObj2OVTS-mu...	35 ms
/s/googlesans/v67/4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iq...	30 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: div.container > div.content-block > div.vertical-container > img

path: 1,HTML,1,BODY,1,DIV,7,SECTION,0,DIV,0,DIV,1,DIV,0,IMG

selector: div.container > div.content-block > div.vertical-container > img

snippet: <img src="https://groups.tapatalk-cdn.com/web/homepage/home-image9.png" width="400" height="400">

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

value: No additional origins are good candidates for preconnecting

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
/css?family=Roboto\|Roboto+Mono\|Google+Sans\|Material+Icons...	3.2 KiB	273 ms
use.fontawesome.com/releases/v5.8.2/css/all.css	13.0 KiB	256 ms
stackpath.bootstrapcdn.com/bootstrap/4.1.3/js/bootstrap.min.js	14.7 KiB	329 ms
stackpath.bootstrapcdn.com/bootstrap/4.1.3/css/bootstrap.min.css	22.2 KiB	340 ms
www.tapatalk.com/js/jquery-3.3.1.min.js	30.8 KiB	114 ms
www.tapatalk.com/js/googleonetap.js?time=2024112201	701 B
www.tapatalk.com/js/jquery.easing.js	2.0 KiB	57 ms
www.tapatalk.com/js/slideout.min.js	2.6 KiB
www.tapatalk.com/css/home-responsive.css	686 B
www.tapatalk.com/css/home_views/index.css?time=2024121201	5.5 KiB
www.tapatalk.com/css/font-awesome.min.css	4.9 KiB
www.tapatalk.com/css/home.css?time=20190705	5.5 KiB	57 ms
www.tapatalk.com/css/icomoon.css	739 B

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
/hNF15JGZRT5P1DSK6vhPEdH7QUX0zAPhgLMH-Or3pqfM0k6sfsK7eEKu...	86400.0 s	2.5 KiB

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
div.container > a.logo-title > div > img `div.container > a.logo-title > div > img`	groups.tapatalk-cdn.com/web/tapatalk.png	19.8 KiB	19.6 KiB
div.container > div.content-block > div.vertical-container > img `div.container > div.content-block > div.vertical-container > img`	groups.tapatalk-cdn.com/web/homepage/home-image9.png	14.1 KiB	10.6 KiB
div.container > a.logo-title > div > img `div.container > a.logo-title > div > img`	groups.tapatalk-cdn.com/web/logo.png	6.8 KiB	6.7 KiB

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

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 670 ms

URL	Time Spent
tapatalk.com/	670 ms
www.tapatalk.com/	0.0 ms

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: 40 ms 47.5 KiB

URL	Transfer Size	Est Savings
stackpath.bootstrapcdn.com/bootstrap/4.1.3/css/bootstrap.min.css	21.6 KiB	21.0 KiB
.fc-consent-root .fc-dialog-container.fc-fullscreen { height: 100% !important; … } …	16.2 KiB	14.0 KiB
use.fontawesome.com/releases/v5.8.2/css/all.css	12.5 KiB	12.5 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Reduce unused 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: 0.0 ms 410.4 KiB

URL	Transfer Size	Est Savings
/pagead/managed/js/gpt/m202604160201/pubads_impl.js	187.8 KiB	137.3 KiB
www.googletagmanager.com/gtag/js?id=G-5MK351CLN0	148.5 KiB	104.3 KiB
accounts.google.com/gsi/client	95.6 KiB	72.0 KiB
www.googletagmanager.com/gtag/js?id=G-5MK351CLN0	148.5 KiB	61.0 KiB
fundingchoicesmessages.google.com/i/728035918?ers=3	68.7 KiB	35.8 KiB

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

●Layout shift culprits

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 50 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 934 KiB

●User Timing marks and measures 5 user timings

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.5 s

●Avoid long main-thread tasks 2 long tasks found

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

●Network Requests

●Network Round Trip Times 50 ms

●Server Backend Latencies 420 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

●Avoid large layout shifts 3 layout shifts found

○INP breakdown

○Avoid non-composited animations

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.

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
This website uses cookies to ensure you get the best experience on our website. `body > div.cc-window > span#cookieconsent:desc`
Got it! `body > div.cc-window > div.cc-compliance > a.cc-btn`
Getting Started `div.container > ul.navbar-nav > li.nav-item > a.nav-link`
Tapatalk Groups `div.container > ul.navbar-nav > li.nav-item > a.nav-link`
Tapatalk Mobile `div.container > ul.navbar-nav > li.nav-item > a.nav-link`
Tapatalk VIP `div.container > ul.navbar-nav > li.nav-item > a.nav-link`
Support `div.container > ul.navbar-nav > li.nav-item > a.nav-link`
Log In `div.container > div.login > a > span`
Sign Up `div.vertical-container > div.content-button > a > div.clapat-button`
Start New `div.text-content > div.content-block1 > a > div.content-learn`
Activate My Forum `div.text-content > div.content-block1 > a > div.content-learn`
Migrate My Forum `div.text-content > div.content-block1 > a > div#view_all`
Back to top `body > div#footer > div.back-top > a`
Get the Tapatalk app `body > div#footer > div.l-u > p`
PRODUCTS `div.link-tz > div.link-i > ul > li`
Tapatalk Groups `div.link-i > ul > li > a`
Tapatalk Mobile App `div.link-i > ul > li > a`
SUPPORT `div.link-tz > div.link-i > ul > li`
Support Forum `div.link-i > ul > li > a`
Submit Security Incident `div.link-i > ul > li > a`
ABOUT US `div.link-tz > div.link-i > ul > li`
LinkedIn `div.link-i > ul > li > a`
Crunchbase `div.link-i > ul > li > a`
Privacy Policy `div#footer > ul.nav > li > a`
End-User License Agreement `div#footer > ul.nav > li > a`
Site Owner License Agreement `div#footer > ul.nav > li > a`
Manage Privacy Settings `div#footer > ul.nav > li#manage_privacy > a`
© 2024 Everforo, Inc `div#footer > ul.nav > li > a`
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.

Names and labels

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.container > a.logo-title > div > img `div.container > a.logo-title > div > img`
div.container > a.logo-title > div > img `div.container > a.logo-title > div > img`
div.container > div.content-block > div.vertical-container > img `div.container > div.content-block > div.vertical-container > img`
div.content-block > div.shadow_css > div.img-content > img `div.content-block > div.shadow_css > div.img-content > img`
div.content-block > div.shadow_css > div.img-content > img `div.content-block > div.shadow_css > div.img-content > img`
div.content-block > div.shadow_css > div.img-content > img `div.content-block > div.shadow_css > div.img-content > img`

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.

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
Got it! `body > div.cc-window > div.cc-compliance > a.cc-btn`

○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

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

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

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

○Links are distinguishable without relying on color.

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

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

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
Specifying overflow: visible on img, video and canvas tags may cause them to produce visual content outside of the element bounds. See https://github.com/WICG/shared-element-transitions/blob/main/debugging_overflow_on_images.md.	/_/mss/boq-content-ads-contributor/_/js/k=boq-content-ads... line 19, col 449

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

Source	Description
www.tapatalk.com/	`Not signed in with the identity provider.`
www.tapatalk.com/js/home_views/index.js?v=2020021801 line 336, col 56	`TypeError: Cannot read properties of undefined (reading 'top') at https://www.tapatalk.com/js/home_views/index.js?v=2020021801:337:57`
www.tapatalk.com/js/home_views/index.js?v=2020021801 line 336, col 56	`TypeError: Cannot read properties of undefined (reading 'top') at https://www.tapatalk.com/js/home_views/index.js?v=2020021801:337:57`
www.tapatalk.com/js/home_views/index.js?v=2020021801 line 336, col 56	`TypeError: Cannot read properties of undefined (reading 'top') at https://www.tapatalk.com/js/home_views/index.js?v=2020021801:337:57`
www.tapatalk.com/js/home_views/index.js?v=2020021801 line 336, col 56	`TypeError: Cannot read properties of undefined (reading 'top') at https://www.tapatalk.com/js/home_views/index.js?v=2020021801:337:57`
www.tapatalk.com/js/home_views/index.js?v=2020021801 line 336, col 56	`TypeError: Cannot read properties of undefined (reading 'top') at https://www.tapatalk.com/js/home_views/index.js?v=2020021801:337:57`
www.tapatalk.com/js/home_views/index.js?v=2020021801 line 336, col 56	`TypeError: Cannot read properties of undefined (reading 'top') at https://www.tapatalk.com/js/home_views/index.js?v=2020021801:337:57`
www.tapatalk.com/js/home_views/index.js?v=2020021801 line 336, col 56	`TypeError: Cannot read properties of undefined (reading 'top') at https://www.tapatalk.com/js/home_views/index.js?v=2020021801:337:57`
www.tapatalk.com/js/home_views/index.js?v=2020021801 line 336, col 56	`TypeError: Cannot read properties of undefined (reading 'top') at https://www.tapatalk.com/js/home_views/index.js?v=2020021801:337:57`

●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 DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Mitigate clickjacking with XFO or CSP

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

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
`div#panel > div.home-navbar > div.container > a.show-menu`
Learn More `div.content-block > div.vertical-container > div.content-button > a`
Start New `div.shadow_css > div.text-content > div.content-block1 > a`
Activate My Forum `div.shadow_css > div.text-content > div.content-block1 > a`
Migrate My Forum `div.shadow_css > div.text-content > div.content-block1 > a`

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

Content Best Practices

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.container > a.logo-title > div > img `div.container > a.logo-title > div > img`
div.container > a.logo-title > div > img `div.container > a.logo-title > div > img`
div.container > div.content-block > div.vertical-container > img `div.container > div.content-block > div.vertical-container > img`
div.content-block > div.shadow_css > div.img-content > img `div.content-block > div.shadow_css > div.img-content > img`
div.content-block > div.shadow_css > div.img-content > img `div.content-block > div.shadow_css > div.img-content > img`
div.content-block > div.shadow_css > div.img-content > img `div.content-block > div.shadow_css > div.img-content > img`

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 have descriptive text

●robots.txt is valid

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`