Skip to content
https://termsfeed.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.

100

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.

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.

RequestCache TTLTransfer Size
www.dwin1.com/19038.js600.0 s15.4 KiB
www.termsfeed.com/public/images/footer-top-promo-card-bg.svg3600.0 s9.5 KiB
www.termsfeed.com/public/images/icon-map-europe.svg3600.0 s8.9 KiB
www.termsfeed.com/public/images/icon-map-canada.svg3600.0 s8.2 KiB
www.termsfeed.com/public/images/home/consent-management-platform.svg3600.0 s7.0 KiB
www.termsfeed.com/public/images/home/agreements-policies-generator.svg3600.0 s6.6 KiB
www.termsfeed.com/public/images/home/notifications.svg3600.0 s6.2 KiB
www.termsfeed.com/public/images/icon-map-uk.svg3600.0 s5.7 KiB
www.termsfeed.com/public/images/icon-law-gdpr.svg3600.0 s4.6 KiB
www.termsfeed.com/public/images/icon-map-australia.svg3600.0 s4.4 KiB
www.termsfeed.com/public/images/icon-map-usa.svg3600.0 s3.4 KiB
www.termsfeed.com/public/images/icon-law-caloppa.svg3600.0 s3.1 KiB
www.termsfeed.com/public/images/home/customization.svg3600.0 s3.0 KiB
www.termsfeed.com/public/images/logo.svg3600.0 s2.8 KiB
www.termsfeed.com/public/images/icon-law-ccpa.svg3600.0 s2.8 KiB
www.termsfeed.com/public/images/rating-stars.svg3600.0 s2.6 KiB
www.termsfeed.com/public/images/icon-termsfeed-cookies-policy-generator.svg3600.0 s2.3 KiB
www.termsfeed.com/public/images/icon-termsfeed-eula-generator.svg3600.0 s2.2 KiB
www.termsfeed.com/public/images/icon-law-pipeda.svg3600.0 s2.1 KiB
www.termsfeed.com/public/images/icon-termsfeed-privacy-policy-generator.svg3600.0 s2.0 KiB
www.termsfeed.com/public/images/icon-termsfeed-privacy-consent.svg3600.0 s1.9 KiB
www.termsfeed.com/public/images/icon-more.svg3600.0 s1.9 KiB
www.termsfeed.com/public/images/icons/paypal.svg3600.0 s1.8 KiB
/public/images/icon-termsfeed-return-refund-policy-genera...3600.0 s1.7 KiB
www.termsfeed.com/plausible/script.js360.0 s1.3 KiB
www.termsfeed.com/public/images/icons/amazon.svg3600.0 s1.4 KiB
www.termsfeed.com/public/images/icons/google-analytics.svg3600.0 s1.4 KiB
www.termsfeed.com/public/images/icon-termsfeed-disclaimer-generator.svg3600.0 s1.3 KiB
www.termsfeed.com/public/images/icons/google-play-store.svg3600.0 s1.2 KiB
www.termsfeed.com/public/images/icons/apple-app-store.svg3600.0 s1.2 KiB
www.termsfeed.com/public/images/icons/google-adsense.svg3600.0 s1.1 KiB
www.termsfeed.com/public/images/icons/google-ads.svg3600.0 s1.0 KiB
www.termsfeed.com/public/images/icon-termsfeed-terms-conditions-generator.svg3600.0 s1.0 KiB
www.termsfeed.com/public/images/icon-search-bar.svg3600.0 s894 B
www.termsfeed.com/public/images/icon-chevron.svg3600.0 s872 B
www.termsfeed.com/public/images/icons/facebook.svg3600.0 s796 B
www.termsfeed.com/public/images/icon-termsfeed-more.svg3600.0 s780 B
www.termsfeed.com/public/web/css/main.css3600.0 s309 B
www.termsfeed.com/public/web/js/main.js3600.0 s289 B
/track.php?fingerprint=4cb8e300-8795-4c72-9baf-47991be1e3...0.0 ms176 B

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: 214 ms
URLTime Spent
termsfeed.com/214 ms
www.termsfeed.com/0.0 ms
●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Time to Interactive 0.5 s
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 143 KiB
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.3 s
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 200 ms
●Server Backend Latencies 40 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 10 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid long main-thread tasks
○Avoid non-composited animations
○Avoid large layout shifts
91

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. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
read the disclaimer div.bottom > div.disclaimer > p > a

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Czech Danish German English Spanish French Italian Dutch Norwegian Polish Portu… div.bottom > div.terms-lang-switch > div.language-switch > select.user_language_switch

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.

○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>`
●`[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
●Background and foreground colors have a sufficient contrast ratio
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○Uses ARIA roles only on compatible elements
○Elements with visible text labels have matching accessible names.
○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 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
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback