Skip to content
https://seowebchecker.com/ai-website-tester

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.

45

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.

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...30 ms

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
seowebchecker.com/css/ai-llm-website-tester.css13.8 KiB334 ms
/css2?family=Inter:opsz,wght@14..32,300;14..32,400;14..32...1.4 KiB842 ms

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
/pagead/managed/js/adsense/m202611030101/show_ads_impl_fy...1209600.0 s167.9 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

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 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.3 s 465.8 KiB
URLTransfer SizeEst Savings
/pagead/managed/js/adsense/m202611030101/show_ads_impl_fy...167.8 KiB135.6 KiB
cdnjs.cloudflare.com/ajax/libs/jspdf/2.5.1/jspdf.umd.min.js93.2 KiB77.3 KiB
www.googletagmanager.com/gtag/js?id=G-96YN5SEMCD&cx=c&gtm=4e6b50162.2 KiB71.6 KiB
www.googletagmanager.com/gtag/js?id=UA-142294912-2132.4 KiB71.1 KiB
cdnjs.cloudflare.com/ajax/libs/Chart.js/4.4.1/chart.umd.min.js58.7 KiB52.3 KiB
/i/ca-pub-6869302511765147?href=https%3A%2F%2Fseowebcheck...70.0 KiB36.5 KiB
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js56.2 KiB21.4 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
seowebchecker.com/ai-website-tester1.3 s39 ms3.3 ms
Unattributable344 ms8.2 ms0.0 ms
/f/AGSKWxVU4JEfb7JvG1TIPU-HCbiw9wm6QIi5lTm-8JYbJuS9w-kXLi...323 ms147 ms49 ms
/cdn-cgi/challenge-platform/scripts/jsd/main.js?ray=a57f0...251 ms230 ms4.3 ms
www.googletagmanager.com/gtag/js?id=G-96YN5SEMCD&cx=c&gtm=4e6b50244 ms197 ms45 ms
/i/ca-pub-6869302511765147?href=https%3A%2F%2Fseowebcheck...215 ms189 ms23 ms
www.googletagmanager.com/gtag/js?id=UA-142294912-2171 ms122 ms37 ms
/pagead/managed/js/adsense/m202611030101/show_ads_impl_fy...153 ms103 ms48 ms
pagead2.googlesyndication.com/pagead/js/adsbygoogle.js149 ms102 ms16 ms
cdnjs.cloudflare.com/ajax/libs/jspdf/2.5.1/jspdf.umd.min.js72 ms35 ms36 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 Evaluation1.2 s
Other828 ms
Style & Layout671 ms
Script Parsing & Compilation284 ms
Rendering173 ms
Parse HTML & CSS75 ms
Garbage Collection70 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.3 KiB
URLTransfer SizeEst Savings
seowebchecker.com/css/ai-llm-website-tester.css13.8 KiB2.3 KiB

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: 0.0 ms 3.1 KiB
URLTransfer SizeEst Savings
seowebchecker.com/js/website-test-ai.js12.8 KiB3.1 KiB

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 14.4 KiB
URLTransfer SizeEst Savings
.fc-consent-root .fc-dialog-container.fc-landscape-mode { height: 90% !important; … } …16.6 KiB14.4 KiB

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
●Avoids enormous network payloads Total size was 1,002 KiB
●Avoid long main-thread tasks 13 long tasks found
●Avoid non-composited animations 1 animated element 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 250 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 220 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid large layout shifts
95

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
Supports HTTP & HTTPS · No account required · Results in ~15–30s body > section#hero > div#tester-card > p#url-hint
Meta, titles, schema, canonicals div.test-options > label.test-option > span.to-body > em
TTFB, compression, caching div.test-options > label.test-option > span.to-body > em
WCAG 2.1 AA/AAA checks div.test-options > label.test-option > span.to-body > em
Headers, HTTPS, CSP, XSS div.test-options > label.test-option > span.to-body > em
Viewport, touch targets div.test-options > label.test-option > span.to-body > em
Live 404/301 checks (30 links) div.test-options > label.test-option > span.to-body > em
Render-blocking, inline styles div.test-options > label.test-option > span.to-body > em
Sync scripts, eval, jQuery div.test-options > label.test-option > span.to-body > em
JSON-LD, Schema.org div.test-options > label.test-option > span.to-body > em
OG, Twitter/X cards div.test-options > label.test-option > span.to-body > em
Alt, lazy-load, dimensions div.test-options > label.test-option > span.to-body > em
Soft-404, cookie consent div.test-options > label.test-option > span.to-body > em
Font-display, web fonts div.test-options > label.test-option > span.to-body > em
Doctype, deprecated tags, IDs div.test-options > label.test-option > span.to-body > em
HTTPS redirect, www/non-www div.test-options > label.test-option > span.to-body > em
Secure, HttpOnly, SameSite div.test-options > label.test-option > span.to-body > em
Free AI-powered tools for SEO, web testing, content generation, and developer u… footer > div.footer-grid > div.footer-brand > p
⚠️ Disclaimer: All product names, logos, and trademarks are property of their re… footer > div.footer-grid > div.footer-brand > p.disclaimer
Disclaimer: div.footer-grid > div.footer-brand > p.disclaimer > strong
Generator Tools div.footer-col > ul.footer-links > li > a
Converter Tools div.footer-col > ul.footer-links > li > a
AI Tools div.footer-col > ul.footer-links > li > a
Testing Tools div.footer-col > ul.footer-links > li > a
Calculators div.footer-col > ul.footer-links > li > a
Time Tools div.footer-col > ul.footer-links > li > a
Image Tools div.footer-col > ul.footer-links > li > a
Encryption Tools div.footer-col > ul.footer-links > li > a
Networking Tools div.footer-col > ul.footer-links > li > a
Dev Tools div.footer-col > ul.footer-links > li > a
Text Tools div.footer-col > ul.footer-links > li > a
Fractal Generator div.footer-col > ul.footer-links > li > a
PDF Tools div.footer-col > ul.footer-links > li > a
Binary Translator div.footer-col > ul.footer-links > li > a
Security Tools div.footer-col > ul.footer-links > li > a
SEO AI Directory div.footer-col > ul.footer-links > li > a
© 2026 SEOWebChecker.com — All Rights Reserved body > footer > div.footer-bottom > span
Privacy Policy footer > div.footer-bottom > div.footer-legal > a
Cookie Policy footer > div.footer-bottom > div.footer-legal > a
Feedback footer > div.footer-bottom > div.footer-legal > 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.

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
Tool Categories footer > div.footer-grid > div.footer-col > h4

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
Got it! body > div#cookie-banner > button#cookie-dismiss
Analyze Now section#hero > div#tester-card > div.input-row > button#analyze-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
●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
●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 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
●Touch targets have sufficient size and spacing.
●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.
○Image elements have `[alt]` attributes
○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.
○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.
81

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
FencedFrame
/cdn-cgi/challenge-platform/scripts/jsd/main.js?ray=a57f0...
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
/cdn-cgi/challenge-platform/scripts/jsd/main.js?ray=a57f0...
Fledge
/cdn-cgi/challenge-platform/scripts/jsd/main.js?ray=a57f0...
●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
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○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
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`
○Image elements have `[alt]` attributes

Send Feedback