Skip to content
https://cookieyes.com

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.

27

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.246534] map[node:map[boundingRect:map[bottom:714 height:97 left:24 right:388 top:617 width:364] lhId:page-1-DIV nodeLabel:GDPR (EU & UK) CCPA/CPRA VCDPA PIPEDA More path:1,HTML,1,BODY,9,MAIN,0,DIV,0,DIV,1,SECTION,0,DIV,0,DIV,0,DIV,0,DIV,4,DIV selector:div.container > div.row > div.col-12 > div.laws snippet:<div class="laws green-tick tick-icon pr-lg-5 mr-lg-5"> type:node] score:0.246411 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:7392 height:161 left:61 right:351 top:7231 width:290] lhId:page-13-IMG nodeLabel:G2 Rating Badges path:1,HTML,1,BODY,10,FOOTER,0,DIV,0,DIV,0,DIV,1,IMG selector:div.container > div.divider-bottom > div.d-flex > img.g2-badge snippet:<img src="https://www.cookieyes.com/wp-content/themes/cookieyes-new/assets/images/g2…" class="g2-badge d-block d-sm-none small" height="162" width="290" alt="G2 Rating Badges"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:520 height:24 left:1 right:411 top:496 width:410] lhId:page-5-P nodeLabel:We value your privacy path:1,HTML,1,BODY,2,DIV,0,DIV,0,DIV,0,P selector:div.cky-consent-container > div.cky-consent-bar > div.cky-notice > p.cky-title snippet:<p class="cky-title" data-cky-tag="title" aria-level="2" role="heading" style="color: #212121;"> type:node] score:0.000123]]

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.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:55.553 source:map[type:text value:[unattributed]]] map[reflowTime:12.752 source:map[column:62380 line:5 type:source-location url:https://www.cookieyes.com/wp-content/themes/cookieyes-new/assets/bootstrap/js/bootstrap.bundle.min.js urlProvider:network]]]

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

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
script.tapfiliate.com/tapfiliate.js?ver=6.9.44.5 KiB905 ms
www.gstatic.com/charts/loader.js18.6 KiB1.7 s
cdnjs.cloudflare.com/ajax/libs/Chart.js/2.9.4/Chart.js86.1 KiB3.3 s
www.cookieyes.com/wp-includes/js/jquery/jquery.js?ver=3.7.192.1 KiB2.3 s
www.cookieyes.com/wp-content/plugins/mailin/js/mailin-front.js?ver=17758467063.7 KiB330 ms
www.cookieyes.com/wp-content/themes/cookieyes-new/scan-page/scan.js?ver=6.9.42.0 KiB180 ms
www.cookieyes.com/wp-includes/js/jquery/jquery-migrate.js?ver=3.4.111.0 KiB631 ms
/wp-content/plugins/sitepress-multilingual-cms/templates/...806 B180 ms
/wp-content/themes/cookieyes-new/assets/css/company-logos...732 B180 ms
www.cookieyes.com/wp-content/plugins/mailin/css/mailin-front.css?ver=6.9.41.0 KiB180 ms
/wp-content/themes/cookieyes-new/assets/css/guideline/cy-...1.5 KiB180 ms
/wp-content/plugins/enlighter/cache/enlighterjs.min.css?v...11.9 KiB781 ms
/wp-content/themes/cookieyes-new/assets/css/guideline/cy-...2.0 KiB180 ms
/wp-content/themes/cookieyes-new/assets/css/guideline/cy-...2.0 KiB180 ms
/wp-content/themes/cookieyes-new/assets/css/owl-carousel....681 B180 ms
/wp-content/themes/cookieyes-new/assets/bootstrap/css/boo...27.3 KiB1.8 s
/wp-content/themes/cookieyes-new/assets/css/guideline/cy-...2.9 KiB480 ms
/wp-content/themes/cookieyes-new/assets/css/guideline/cy-...5.1 KiB631 ms
www.cookieyes.com/wp-content/themes/cookieyes-new/style.css?v=1.0.9&ver=6.9.41.9 KiB480 ms
www.cookieyes.com/wp-includes/css/dist/block-library/style.css?ver=6.9.419.8 KiB1.1 s
/wp-content/plugins/sitepress-multilingual-cms/templates/...863 B480 ms

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.

URLResource SizeEst Savings
Integrate with industry-standards div > div.row > div.col-12 > img
www.cookieyes.com/wp-content/themes/cookieyes-new/assets/videos/integration.png1.0 MiB978.3 KiB
Automated consent management div > div.row > div.col-12 > img
/wp-content/themes/cookieyes-new/assets/videos/cookie-sca...506.3 KiB456.0 KiB
Customisation of CookieYes banner div > div.row > div.col-12 > img
/wp-content/themes/cookieyes-new/assets/videos/customisat...313.8 KiB263.4 KiB

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: 1.1 s
URLTime Spent
cookieyes.com/1.1 s
www.cookieyes.com/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.

ElementLayout shift score
GDPR (EU & UK) CCPA/CPRA VCDPA PIPEDA More div.container > div.row > div.col-12 > div.laws
0.246
We value your privacy div.cky-consent-container > div.cky-consent-bar > div.cky-notice > p.cky-title
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

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.

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.

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.

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.

CategoryTime Spent
Script Evaluation2.7 s
Other1.7 s
Style & Layout959 ms
Rendering683 ms
Script Parsing & Compilation496 ms
Parse HTML & CSS119 ms
Garbage Collection112 ms

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

●Optimize DOM size
●Font display
●LCP breakdown
●LCP request discovery
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●User Timing marks and measures 5 user timings
●Avoid long main-thread tasks 19 long tasks found
●Avoid non-composited animations 7 animated elements found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 60 ms
●Server Backend Latencies 380 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 180 ms
○INP breakdown
100

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.

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
Try for free div.menu-container > nav.navbar > div.d-flex > a.button
English div.wpml-ls-sidebars-cookieyes_translator_widget > ul > li.wpml-ls-slot-cookieyes_translator_widget > a.js-wpml-ls-item-toggle
○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
●ARIA `progressbar` elements have accessible names
●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 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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[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
○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
○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.
○`<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.
○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.
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.

SourceDescription
Loading the script 'https://cdn.by.wonderpush.com/sdk/1.1/wonderpush-loader.min.js' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' 'unsafe-eval' https://static.cloudflareinsights.com https://js.stripe.com https://scatec.io https://cdn-cookieyes.com https://analytics.ahrefs.com https://widget.intercom.io https://*.bing.com https://embed.reddit.com https://js.intercomcdn.com https://www.googleadservices.com https://embed.typeform.com https://*.cloudflare.com https://*.googlesyndication.com https://*.ads-twitter.com https://*.tawk.to https://*.doubleclick.net https://cdnjs.cloudflare.com https://*.calendly.com https://snap.licdn.com https://*.cookieyes.com https://unpkg.com https://cdn.jsdelivr.net https://script.tapfiliate.com https://connect.facebook.net https://cdn.segment.com https://www.google.com https://www.gstatic.com https://*.getresponse.com https://*.clarity.ms https://*.gr-cdn.com https://*.googletagmanager.com https://*.hotjar.com https://*.googleoptimize.com https://*.google-analytics.com". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. The action has been blocked.

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
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Mitigate clickjacking with XFO or CSP
92

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.

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

○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 are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback