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.

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
cache.betweendigital.com/observerHB.js	7200.0 s	23.2 KiB

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.

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.col-xs-12 > div.row > div.col-xs-10 > img `div.col-xs-12 > div.row > div.col-xs-10 > img`	fastdirect.b-cdn.net/bonus/all-cc/lp1/source/product/ssgif.jpg	22.6 KiB	19.0 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
fastdirect.b-cdn.net/bonus/all-cc/lp1/source/languages3.js	120.2 KiB
code.jquery.com/jquery-3.7.1.min.js	30.0 KiB
fastdirect.b-cdn.net/bonus/all-cc/lp1/source/bootstrap.min.css	32.8 KiB
fastdirect.b-cdn.net/bonus/all-cc/lp1/source/site-protect2.0.js	2.1 KiB
fastdirect.b-cdn.net/bonus/all-cc/lp1/source/main.js	2.4 KiB
fastdirect.b-cdn.net/bonus/all-cc/lp1/source/carriers.js	4.2 KiB

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

Lists the toplevel main thread tasks that executed during page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Collection of useful page vitals.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 9.7 s

URL	Time Spent
fishki.net/	9.4 s
/visit.php?k=3449db5597bb1935d8c1d2aa49928408&mod=h&c=210...	217 ms
/bonus/all-cc/lp1/index.php?ctc=2.99&c=60z627e5zbsz0&k=b3...	0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
document.write(getTranslation('q3_a1')) `div.qu-group > div.row > div#txt26 > script`	0.118
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal > div.modal-dialog > div.modal-content`	0.002
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal > div.modal-dialog > div.modal-content`	0.002
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal > div.modal-dialog`	0.001
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal > div.modal-dialog > div.modal-content`	0.001
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal > div.modal-dialog > div.modal-content`	0.001
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal > div.modal-dialog > div.modal-content`	0.001
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal > div.modal-dialog > div.modal-content`	0.001
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal > div.modal-dialog > div.modal-content`	0.001
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal > div.modal-dialog > div.modal-content`	0.001
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal > div.modal-dialog > div.modal-content`	0.001
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal > div.modal-dialog > div.modal-content`	0.001
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal > div.modal-dialog > div.modal-content`	0.001
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal > div.modal-dialog > div.modal-content`	0.001
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal > div.modal-dialog > div.modal-content`	0.000

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

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.

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.

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 29.2 KiB

URL	Transfer Size	Est Savings
fastdirect.b-cdn.net/bonus/all-cc/lp1/source/bootstrap.min.css	31.8 KiB	29.2 KiB

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 7.4 KiB

URL	Transfer Size	Est Savings
fastdirect.b-cdn.net/bonus/all-cc/lp1/source/bootstrap.min.css	32.8 KiB	7.4 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 24.8 KiB

URL	Transfer Size	Est Savings
fastdirect.b-cdn.net/bonus/all-cc/lp1/source/languages3.js	119.2 KiB	20.0 KiB
fishki.net/js/vue-components/reactions.min.js?57f8151f	10.9 KiB	4.8 KiB

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 21.6 KiB

URL	Transfer Size	Est Savings
code.jquery.com/jquery-3.7.1.min.js	29.6 KiB	21.6 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size
/26/upload/post/2026/04/22/5034382/b95641087404f07bfc4091...	784.4 KiB
cdn.fishki.net/upload/smiles/smiles.png	625.8 KiB
/26/upload/post/2026/04/22/5034274/ab27b6f184f14e50970d1e...	507.4 KiB
fishki.net/js/vue-components/vendor.min.js?57f8151f	246.2 KiB
fishki.net/min/fishki_new/js/min_foot.js?57f8151f	225.0 KiB
statika.mpsuadv.ru/lib/bidder-new.mpsu.js	219.1 KiB
fishki.net/css/fishki_new/img/main-icons.png?15239	169.3 KiB
fishki.net/css/fishki_new/fonts/PTS75F_W.woff	157.0 KiB
fishki.net/min/fishki_new/css/min_base.css?57f8151f	155.5 KiB
tn.fishki.net/26/upload/post/2026/04/22/5034254/gallery/tn/azimut1.jpg	152.2 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
div.col-xs-12 > div.row > div.col-xs-10 > img `div.col-xs-12 > div.row > div.col-xs-10 > img`	fastdirect.b-cdn.net/bonus/all-cc/lp1/source/product/ssgif.jpg
tbody > tr > td > img#logo1 `tbody > tr > td > img#logo1`	fastdirect.b-cdn.net/bonus/all-cc/lp1/source/logo/google-logo.png
tbody > tr > td.logo > img#logo `tbody > tr > td.logo > img#logo`	fastdirect.b-cdn.net/bonus/all-cc/lp1/source/logo/google-logo.png
div.row > div.col-xs-12 > div.copyright-image > img `div.row > div.col-xs-12 > div.copyright-image > img`	fastdirect.b-cdn.net/bonus/all-cc/lp1/source/product/rta.gif

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Network dependency tree

●Optimize viewport for mobile

●Avoid non-composited animations 2 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 170 ms

●Server Backend Latencies 280 ms

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Wednesday, April 22, 2026 Dear Google customer: Congratulations! You… `body#dummybodyid > div#myModal`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
OK `div.modal-dialog > div.modal-content > div.modal-footer > button#txt8`
Google Customer Reward Program `div.slogan-wrap > div.container > div.row > div#txt9`
Congratulations! `div.row > div.col-xs-10 > div.recipe-header > div#txt10`
iPhone 17 Pro `div#recipe-row > div.col-xs-12 > span#txt11 > span.marked`
Samsung Galaxy S25 `div#recipe-row > div.col-xs-12 > span#txt11 > span.marked`
Walmart $1000 Gift Card `div#recipe-row > div.col-xs-12 > span#txt11 > span.marked`
Visa $1000 Gift Card `div#recipe-row > div.col-xs-12 > span#txt11 > span.marked`
3 years of free membership to Netflix `div#recipe-row > div.col-xs-12 > span#txt11 > span.marked`
1 minutes and 38 seconds `div.col-xs-12 > span#txt11 > div#txt13 > span.marked`
38 `span#txt11 > div#txt13 > span.marked > span#timer-secs`
What kind of device are you using at the moment? `div.row > div.qu-group > div.row > div#txt14`
PC / Notebook `div.row > div.qu-group > div.row > div#txt15`
Smartphone `div.row > div.qu-group > div.row > div#txt16`
Tablet `div.row > div.qu-group > div.row > div#txt17`
Other device `div.row > div.qu-group > div.row > div#txt18`
Luca Schultz `div.col-xs-12 > div.row > div.col-xs-10 > span.name`
Sebastian Price `div.col-xs-12 > div.row > div.col-xs-10 > span.name`
Paula Wulf `div.col-xs-12 > div.row > div.col-xs-10 > span.name`
Michael Chalhoub `div.col-xs-12 > div.row > div.col-xs-10 > span.name`
Leonie Kastner `div.col-xs-12 > div.row > div.col-xs-10 > span.name`
Dimitri Grunewal `div.col-xs-12 > div.row > div.col-xs-10 > span.name`
Leave a comment `div.col-xs-12 > div.row > div.col-xs-12 > span#comment-post`

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
tbody > tr > td > img#logo1 `tbody > tr > td > img#logo1`
tbody > tr > td.logo > img#logo `tbody > tr > td.logo > img#logo`
div.col-xs-12 > div.row > div.col-xs-10 > img `div.col-xs-12 > div.row > div.col-xs-10 > img`
div.row > div.col-xs-12 > div.copyright-image > img `div.row > div.col-xs-12 > div.copyright-image > img`

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-xs-12 > div.row > div.col-xs-12 > textarea#comment-area `div.col-xs-12 > div.row > div.col-xs-12 > textarea#comment-area`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○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

●ARIA attributes are used as specified for the element's role

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

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

○Heading elements appear in a sequentially-descending order

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

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

Best Practices

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
Topics	statika.mpsuadv.ru/lib/bidder-new.mpsu.js line 11, col 31697
SharedStorage	line 2, col 12831
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.	line 2, col 12831
Fledge	line 2, col 12831
Unload event listeners are deprecated and will be removed.	cache.betweendigital.com/observerHB.js

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
fishki.net/	`Access to fetch at 'https://yandex.ru/ads/adfox/351299/getCode?p1=dfixb&p2=gmjh&puid1=bank.yuga.ru' from origin 'https://fishki.net' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
yandex.ru/ads/adfox/351299/getCode?p1=dfixb&p2=gmjh&puid1=bank.yuga.ru	`Failed to load resource: net::ERR_FAILED`
about:srcdoc	`ReferenceError: mraid is not defined at about:srcdoc:1:3877`
	`Unsafe attempt to initiate navigation for frame with URL 'https://fishki.net/' from frame with URL 'about:srcdoc'. The frame attempting navigation of the top-level window is sandboxed, but the flag of 'allow-top-navigation' or 'allow-top-navigation-by-user-activation' is not set.`
	`Unsafe attempt to initiate navigation for frame with URL 'https://fishki.net/' from frame with URL 'about:srcdoc'. The frame attempting navigation of the top-level window is sandboxed, but the flag of 'allow-top-navigation' or 'allow-top-navigation-by-user-activation' is not set.`

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
Cookie

●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

●Properly defines charset

●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

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 are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
`head > meta`
`https://sweepvibe.buzz/robots.txt`

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
document.write(getTranslation('claim')… `div.row > div.col-xs-7 > p > a.qu-take-it`
document.write(getTranslation('claim')… `div.row > div.col-xs-7 > p > a.qu-take-it`
document.write(getTranslation('claim')… `div.row > div.col-xs-7 > p > a.qu-take-it`
document.write(getTranslation('claim')… `div.row > div.col-xs-7 > p > a.qu-take-it`
document.write(getTranslation('claim')… `div.row > div.col-xs-7 > p > a.qu-take-it`

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

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
tbody > tr > td > img#logo1 `tbody > tr > td > img#logo1`
tbody > tr > td.logo > img#logo `tbody > tr > td.logo > img#logo`
div.col-xs-12 > div.row > div.col-xs-10 > img `div.col-xs-12 > div.row > div.col-xs-10 > img`
div.row > div.col-xs-12 > div.copyright-image > img `div.row > div.col-xs-12 > div.copyright-image > img`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Document has a `<title>` element

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