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

items: [map[reflowTime:79.875 source:map[column:325 line:335 type:source-location url:https://iacesport.com/ 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:79.875 source:map[column:195 line:337 type:source-location url:https://iacesport.com/ urlProvider:network]] map[reflowTime:56.081 source:map[column:6248 line:352 type:source-location url:https://iacesport.com/ urlProvider:network]]]

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

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
Style & Layout	2.8 s
Other	782 ms
Parse HTML & CSS	360 ms
Rendering	229 ms
Script Evaluation	213 ms
Script Parsing & Compilation	25 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

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: 0.0 ms 305.4 KiB

URL	Transfer Size	Est Savings
/wp-content/cache/seraphinite-accelerator/s/m/d/css/1844a...	121.0 KiB	121.0 KiB
/wp-content/cache/seraphinite-accelerator/s/m/d/css/bb139...	65.3 KiB	65.3 KiB
/wp-content/cache/seraphinite-accelerator/s/m/d/css/3436b...	31.1 KiB	31.1 KiB
/wp-content/cache/seraphinite-accelerator/s/m/d/css/1debc...	23.7 KiB	23.7 KiB
/wp-content/cache/seraphinite-accelerator/s/m/d/css/40a05...	18.7 KiB	18.7 KiB
/wp-content/cache/seraphinite-accelerator/s/m/d/css/25e2c...	18.5 KiB	18.5 KiB
:focus{outline:0} …	17.2 KiB	17.2 KiB
/wp-content/cache/seraphinite-accelerator/s/m/d/css/ef714...	10.1 KiB	10.1 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
USA Pickleball ball certification report, page 1 of 3 `div.ia-report-track > figure.ia-report-slide > button.ia-report-image-button > img.lzl`
USA Pickleball ball certification report, page 2 of 3 `div.ia-report-track > figure.ia-report-slide > button.ia-report-image-button > img.lzl`
USA Pickleball ball certification report, page 3 of 3 `div.ia-report-track > figure.ia-report-slide > button.ia-report-image-button > img.lzl`
USA Pickleball paddle certification report, page 2 of 4 `div.ia-report-track > figure.ia-report-slide > button.ia-report-image-button > img.lzl`
USA Pickleball paddle certification report, page 1 of 4 `div.ia-report-track > figure.ia-report-slide > button.ia-report-image-button > img.lzl`
USA Pickleball paddle certification report, page 4 of 4 `div.ia-report-track > figure.ia-report-slide > button.ia-report-image-button > img.lzl`
USA Pickleball paddle certification report, page 3 of 4 `div.ia-report-track > figure.ia-report-slide > button.ia-report-image-button > img.lzl`

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

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●Improve image delivery

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Network dependency tree

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 401 KiB

●JavaScript execution time 0.2 s

●Avoid long main-thread tasks 12 long tasks found

●Network Requests

●Network Round Trip Times 0 ms

●Server Backend Latencies 110 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 2 layout shifts found

○INP breakdown

○User Timing marks and measures

○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
PRODUCT COMPLIANCE EVIDENCE `section.ia-testing-block > div.ia-testing-grid > div > p.ia-testing-eyebrow`
Discuss Certification Requirements `section.ia-testing-block > div.ia-testing-grid > div > a.ia-testing-button`
Drag or swipe to review every page. Click a page to view the original image at … `section.ia-testing-block > div.ia-testing-grid > div.ia-report-browser > p.ia-swipe-note`
YOU HAVE `div.elementor-element > div.elementor-element > div.elementor-widget-container > div.elementor-heading-title`
Market · Price · Quantity `div.elementor-element > div.elementor-element > div.elementor-widget-container > div.elementor-heading-title`
→ WHAT HAPPENS NEXT `div.elementor-element > div.elementor-element > div.elementor-widget-container > div.elementor-heading-title`
Get a Starting Recommendation → `div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text`
YOU HAVE `div.elementor-element > div.elementor-element > div.elementor-widget-container > div.elementor-heading-title`
A Reference Paddle `div.elementor-element > div.elementor-element > div.elementor-widget-container > div.elementor-heading-title`
→ WHAT HAPPENS NEXT `div.elementor-element > div.elementor-element > div.elementor-widget-container > div.elementor-heading-title`
Review My Reference Paddle → `div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text`
YOU HAVE `div.elementor-element > div.elementor-element > div.elementor-widget-container > div.elementor-heading-title`
A Drawing or Product Idea `div.elementor-element > div.elementor-element > div.elementor-widget-container > div.elementor-heading-title`
→ WHAT HAPPENS NEXT `div.elementor-element > div.elementor-element > div.elementor-widget-container > div.elementor-heading-title`
Discuss My Product Idea → `div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text`
Not sure which starting point fits? `div.elementor-element > div.elementor-element > div.elementor-widget-container > h3.elementor-heading-title`
Send a photo, your target price, and your estimated quantity. We will ask for t… `div.elementor-element > div.elementor-element > div.elementor-widget-container > p`
Send What I Have → `div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text`
YOUR PRODUCT · YOUR SPECIFICATION `section#homepage-08-custom-paddle-development-native-performance-v3 > div.elementor-element > div.elementor-widget-container > p`
Discuss Your Custom Paddle `div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text`
Discuss Testing for Your Paddle `div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text`
REAL CUSTOMER FEEDBACK `div.elementor-element > div.elementor-element > div.elementor-widget-container > div.elementor-heading-title`
QUESTIONS BEFORE YOU START `div.elementor-element > div.elementor-element > div.elementor-widget-container > div.elementor-heading-title`
GET YOUR FACTORY QUOTE `div.elementor-element > div.elementor-element > div.elementor-widget-container > div.elementor-heading-title`
Send Project Details `div.elementor-field-group > button.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text`
Get a Factory Quote `div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text`
© 2026 iAcesport. All rights reserved. `div.elementor-element > div.elementor-element > div.elementor-widget-container > p`
Terms of Service `div.elementor-element > div.elementor-widget-container > p > span`
Privacy Policy `div.elementor-element > div.elementor-widget-container > p > span`
Cookie Policy `div.elementor-element > div.elementor-widget-container > p > span`

These are opportunities to improve the legibility of your content.

Names and labels

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
div.elementor-element > div.elementor-element > div.elementor-widget-container > a `div.elementor-element > div.elementor-element > div.elementor-widget-container > a`
div.elementor-element > div.elementor-element > div.elementor-widget-container > a `div.elementor-element > div.elementor-element > div.elementor-widget-container > a`
div.elementor-element > div.elementor-element > div.elementor-widget-container > a `div.elementor-element > div.elementor-element > div.elementor-widget-container > a`
div.elementor-element > div.elementor-element > div.elementor-widget-container > a `div.elementor-element > div.elementor-element > div.elementor-widget-container > a`
div.elementor-element > div.elementor-element > div.elementor-widget-container > a `div.elementor-element > div.elementor-element > div.elementor-widget-container > a`
div.elementor-element > div.elementor-element > div.elementor-widget-container > a `div.elementor-element > div.elementor-element > div.elementor-widget-container > a`
div.elementor-element > div.elementor-element > div.elementor-widget-container > a `div.elementor-element > div.elementor-element > div.elementor-widget-container > a`
div.elementor-element > div.elementor-element > div.elementor-widget-container > a `div.elementor-element > div.elementor-element > div.elementor-widget-container > a`
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon `div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-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.

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
Get a Factory Quote `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Start With What You Have `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Get a Starting Recommendation → `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Review My Reference Paddle → `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Discuss My Product Idea → `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Discuss this model `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Discuss this model `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Discuss this model `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Discuss this model `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Discuss this model `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Discuss this model `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Discuss this model `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Discuss this model `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Discuss this model `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Discuss this model `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Discuss this model `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Discuss this model `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Compare My Paddle Options `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Click to Chat `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Click to Chat `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Click to Chat `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Click to Chat `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Click to Chat `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`
Click to Chat `div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button`

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

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

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` 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

○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

○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

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

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

100

Best Practices

●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 browser errors logged to the console

●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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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`