https://aitextwatermarkremover.com
Lighthouse Desktop
· 0 checks — Desktop 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.
99
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.
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
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 |
|---|---|---|
| scripts.clarity.ms/0.8.69/clarity.js | 86400.0 s | 25.2 KiB |
| analytics.ahrefs.com/analytics.js | 14400.0 s | 3.0 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 | |
|---|---|---|---|
Before noise. After clarity. section.section-wash-fade > div.mx-auto > div.mt-10 > img.h-auto | aitextwatermarkremover.com/images/demo-before-after.webp | 83.6 KiB | 52.5 KiB |
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 |
|---|---|---|
| aitextwatermarkremover.com/_next/static/chunks/1uu-vq6qvbrgj.css | 14.5 KiB | 58 ms |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
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: 0.0 ms 168.5 KiB
| URL | Transfer Size | Est Savings |
|---|---|---|
| accounts.google.com/gsi/client | 96.4 KiB | 72.8 KiB |
| www.googletagmanager.com/gtag/js?id=G-2R8NV0Q070 | 165.5 KiB | 70.1 KiB |
| aitextwatermarkremover.com/_next/static/chunks/2aqhk1adku7v0.js | 71.6 KiB | 25.6 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
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Time to Interactive 1.0 s
●Max Potential First Input Delay 40 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 923 KiB
●JavaScript execution time 0.2 s
●Minimizes main-thread work 0.6 s
●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 90 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 70 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid non-composited animations
96
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 |
|---|
Cleans invisible Unicode locally in your browser. Hidden marks vary by source. div.flex > div.px-3 > div.relative > p.pointer-events-none |
0 characters · 0 words div.px-3 > div.relative > div.pointer-events-none > span.whitespace-nowrap |
Paste div.border-t > div.flex > div.flex > button.inline-flex |
Clear div.border-t > div.flex > div.flex > button.shrink-0 |
Try a Sample div.border-t > div.flex > div.flex > button.inline-flex |
Claude main#top > section.section-wash > div.mx-auto > span.font-display |
ChatGPT main#top > section.section-wash > div.mx-auto > span.font-display |
Gemini main#top > section.section-wash > div.mx-auto > span.font-display |
Docs main#top > section.section-wash > div.mx-auto > span.font-display |
CMS main#top > section.section-wash > div.mx-auto > span.font-display |
Email main#top > section.section-wash > div.mx-auto > span.font-display |
3 hidden · Markdown noise div.mt-6 > div.overflow-hidden > div.mb-4 > span.text-xs |
Visible text intact div.mt-6 > div.overflow-hidden > div.mb-4 > span.text-xs |
01 div.mx-auto > ol.mt-12 > li.rounded-2xl > div.flex |
02 div.mx-auto > ol.mt-12 > li.rounded-2xl > div.flex |
03 div.mx-auto > ol.mt-12 > li.rounded-2xl > div.flex |
FEATURES section#what > div.mx-auto > div.mx-auto > p.section-label |
DEFINITION main#top > section#definition > div.mx-auto > p.section-label |
SOURCES section#sources > div.mx-auto > div.mx-auto > p.section-label |
Anthropic, How Claude’s text watermark works (14 Aug 2026) blockquote.rounded-2xl > footer.mt-4 > cite > a.font-semibold |
Unicode Standard, General Punctuation (U+2000 block) blockquote.rounded-2xl > footer.mt-4 > cite > a.font-semibold |
CommonMark spec section#sources > div.mx-auto > p.mt-5 > a.font-semibold |
USE CASES section#cases > div.mx-auto > div.mx-auto > p.section-label |
01 div.mt-14 > article.grid > div.flex > div.flex |
Open the tool → div.mt-14 > article.grid > div.flex > a.mt-6 |
02 div.mt-14 > article.grid > div.flex > div.flex |
Open the tool → div.mt-14 > article.grid > div.flex > a.mt-6 |
03 div.mt-14 > article.grid > div.flex > div.flex |
Open the tool → div.mt-14 > article.grid > div.flex > a.mt-6 |
04 div.mt-14 > article.grid > div.flex > div.flex |
Open the tool → div.mt-14 > article.grid > div.flex > a.mt-6 |
TESTIMONIALS section#testimonials > div.mx-auto > div.mx-auto > p.section-label |
SEO & CMS div.mx-auto > div.mt-12 > article.flex > p.text-xs |
Publishing div.mx-auto > div.mt-12 > article.flex > p.text-xs |
Docs & support div.mx-auto > div.mt-12 > article.flex > p.text-xs |
GUIDES section.bg-white > div.mx-auto > div.mx-auto > p.section-label |
Claude guide → div.mx-auto > div.mt-12 > a.group > span.mt-5 |
ChatGPT guide → div.mx-auto > div.mt-12 > a.group > span.mt-5 |
Gemini guide → div.mx-auto > div.mt-12 > a.group > span.mt-5 |
View all tools → section.bg-white > div.mx-auto > div.mt-6 > a.text-sm |
BLOG section.bg-white > div.mx-auto > div.mt-12 > p.section-label |
Read more → div.mt-5 > a.group > div.flex > span.mt-4 |
Read more → div.mt-5 > a.group > div.flex > span.mt-4 |
PRICING div.px-4 > div.mx-auto > div.mx-auto > p.section-label |
Monthly div.px-4 > div.mx-auto > div.mx-auto > button.relative |
−50% div.mx-auto > div.mx-auto > button.relative > span.rounded-full |
Credit Packs div.px-4 > div.mx-auto > div.mx-auto > button.relative |
CREDITS / MO article.relative > div.mt-4 > div.rounded-xl > div.text-[10px] |
WORDS / MO article.relative > div.mt-4 > div.rounded-xl > div.text-[10px] |
CREDITS / MO article.relative > div.mt-4 > div.rounded-xl > div.text-[10px] |
WORDS / MO article.relative > div.mt-4 > div.rounded-xl > div.text-[10px] |
CREDITS / MO article.relative > div.mt-4 > div.rounded-xl > div.text-[10px] |
WORDS / MO article.relative > div.mt-4 > div.rounded-xl > div.text-[10px] |
Available payment methods are confirmed on the Stripe Checkout page. div.px-4 > div.mx-auto > div.mt-14 > p.mt-4 |
support@aitextwatermarkremover.com div.mx-auto > div.mt-14 > p.mt-3 > a.font-semibold |
ABOUT US section#about > div.mx-auto > div.text-center > p.section-label |
PRODUCT div.mx-auto > div.grid > div > div.text-xs |
TOOLS div.mx-auto > div.grid > div > div.text-xs |
MODEL GUIDES div.mx-auto > div.grid > div > div.text-xs |
About Us footer.border-t > div.mx-auto > nav.mt-12 > a.hover:text-ink |
Contact footer.border-t > div.mx-auto > nav.mt-12 > a.hover:text-ink |
Privacy footer.border-t > div.mx-auto > nav.mt-12 > a.hover:text-ink |
Terms footer.border-t > div.mx-auto > nav.mt-12 > a.hover:text-ink |
Refund Policy footer.border-t > div.mx-auto > nav.mt-12 > a.hover:text-ink |
Email Support footer.border-t > div.mx-auto > nav.mt-12 > a.hover:text-ink |
These are opportunities to improve the legibility of your content.
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 |
|---|
EN div.flex > div.hidden > div.relative > button.inline-flex |
Install App body.min-h-screen > div.fixed > div.group > button.inline-flex |
○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
●`[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
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<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.
○Identical links have the same purpose.
92
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 |
|---|---|
scripts.clarity.ms/0.8.69/clarity.js line 1, col 49436 | Connecting to 'https://g.clarity.ms/collect' violates the following Content Security Policy directive: "connect-src 'self' https://accounts.google.com https://apis.google.com https://api.stripe.com https://checkout.stripe.com https://api.indexnow.org https://www.google-analytics.com https://region1.google-analytics.com https://analytics.google.com https://stats.g.doubleclick.net https://umami.bestvid.net https://www.clarity.ms https://c.clarity.ms https://e.clarity.ms https://r.clarity.ms https://analytics.ahrefs.com". The action has been blocked. |
scripts.clarity.ms/0.8.69/clarity.js line 1, col 49447 | Connecting to 'https://g.clarity.ms/collect' violates the following Content Security Policy directive: "connect-src 'self' https://accounts.google.com https://apis.google.com https://api.stripe.com https://checkout.stripe.com https://api.indexnow.org https://www.google-analytics.com https://region1.google-analytics.com https://analytics.google.com https://stats.g.doubleclick.net https://umami.bestvid.net https://www.clarity.ms https://c.clarity.ms https://e.clarity.ms https://r.clarity.ms https://analytics.ahrefs.com". The action has been blocked. |
scripts.clarity.ms/0.8.69/clarity.js line 1, col 49101 | Connecting to 'https://g.clarity.ms/collect' violates the following Content Security Policy directive: "connect-src 'self' https://accounts.google.com https://apis.google.com https://api.stripe.com https://checkout.stripe.com https://api.indexnow.org https://www.google-analytics.com https://region1.google-analytics.com https://analytics.google.com https://stats.g.doubleclick.net https://umami.bestvid.net https://www.clarity.ms https://c.clarity.ms https://e.clarity.ms https://r.clarity.ms https://analytics.ahrefs.com". The action has been blocked. |
scripts.clarity.ms/0.8.69/clarity.js line 1, col 49101 | Connecting to 'https://g.clarity.ms/collect' violates the following Content Security Policy directive: "connect-src 'self' https://accounts.google.com https://apis.google.com https://api.stripe.com https://checkout.stripe.com https://api.indexnow.org https://www.google-analytics.com https://region1.google-analytics.com https://analytics.google.com https://stats.g.doubleclick.net https://umami.bestvid.net https://www.clarity.ms https://c.clarity.ms https://e.clarity.ms https://r.clarity.ms https://analytics.ahrefs.com". The action has been blocked. |
accounts.google.com/gsi/client line 287, col 14 | Loading the stylesheet 'https://accounts.google.com/gsi/style' violates the following Content Security Policy directive: "style-src 'self' 'unsafe-inline'". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback. The action has been blocked. |
Not signed in with the identity provider. |
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Content security policy |
●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
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`