Lighthouse Mobile

· 0 checks — Mobile 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.

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:42.591 source:map[type:text value:[unattributed]]]]

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
section.mp-hero > div.mp-container > div.mp-hero__video-wrapper > video.mp-hero__video `section.mp-hero > div.mp-container > div.mp-hero__video-wrapper > video.mp-hero__video`	www.semrush.com/static/plg_toolkits.webp	65.1 KiB	59.7 KiB
section.mp-promo-cards > div.mp-promo-cards__container > div.mp-promo-cards__video-wrapper > video.mp-promo-cards__video `section.mp-promo-cards > div.mp-promo-cards__container > div.mp-promo-cards__video-wrapper > video.mp-promo-cards__video`	www.semrush.com/static/enterprise_project.webp	43.8 KiB	35.8 KiB
section.mp-promo-cards > div.mp-promo-cards__container > div.mp-promo-cards__video-wrapper > video.mp-promo-cards__video `section.mp-promo-cards > div.mp-promo-cards__container > div.mp-promo-cards__video-wrapper > video.mp-promo-cards__video`	www.semrush.com/static/semrush_one.webp	25.2 KiB	20.6 KiB

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-3-SECTION

nodeLabel: Be found everywhere search happens The leading platform to grow and measure br…

path: 1,HTML,1,BODY,1,DIV,5,DIV,0,MAIN,3,DIV,0,SECTION

selector: div.srf-layout-main-content-wrapper > main#root-content > div.main-page > section.mp-hero

snippet: <section class="mp-hero section-in-view" aria-labelledby="mp-hero-header" data-path="hero" data-ga-sent="true">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.

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

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.

URL	Transfer Size	Duration
www.semrush.com/__static__/webpack/header_2026.a3abf3f058c51fec.js	3.8 KiB
www.semrush.com/__static__/webpack/runtime.cff31325971d89a9.js	23.0 KiB	301 ms
www.semrush.com/__static__/webpack/track_billing_info_usage.ff41acdf4b921b14.js	710 B
www.semrush.com/__static__/webpack/3486.69d076db124b4d99.js	426 B
/css2?family=Inter:ital,opsz,wght@0,14..32,100..900;1,14....	1.6 KiB	755 ms
www.semrush.com/__static__/webpack/speedcurve_lux.5602422b1f465d7f.js	950 B
www.semrush.com/__static__/webpack/data_layer_proxy.2885cafc0b9681bd.js	1.3 KiB
www.semrush.com/__static__/webpack/mf_widgets.19177f4a7cce3516.js	840 B
www.semrush.com/__static__/webpack/observer_limit_options.b96b16e9b1f5e095.js	746 B
www.semrush.com/static/index_rebranding.95296ed8b1dea687d82b.css	17.0 KiB	150 ms
www.semrush.com/__static__/webpack/header_2026.2d973d026289e6a7.css	29.3 KiB	451 ms
www.semrush.com/__static__/webpack/5182.eed5fc28c8e74791.css	6.5 KiB
www.semrush.com/__static__/fonts/factor_a/v2/factor_a.css	522 B
/__static__/webpack/semrush_one_banner_styles.92d5db20bc7...	1.2 KiB
www.semrush.com/__static__/fonts/lazzer/v2/lazzer.css	921 B
www.semrush.com/__static__/webpack/site_info_2026.183215081ed969b0.css	272 B

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
connect.facebook.net/en_US/fbevents.js	1200.0 s	96.6 KiB
/signals/config/239948206198576?v=2.9.303&r=stable&domain...	1200.0 s	46.1 KiB
cdn.cookiehub.eu/c2/06c77e2e.js	86400.0 s	43.2 KiB
schedule.zoominfo.com/zischedule.js	0.0 ms	17.1 KiB
www.google-analytics.com/analytics.js	7200.0 s	20.9 KiB
qz9icofk.micpn.com/p/js/1.js	0.0 ms	14.7 KiB
tags.clickagy.com/data.js?rnd=62fe5c0e6ad96	0.0 ms	14.2 KiB
snap.licdn.com/li.lms-analytics/insight.min.js	10828.0 s	18.7 KiB
js.adsrvr.org/up_loader.1.1.0.js	0.0 ms	12.5 KiB
ws-assets.zoominfo.com/formcomplete.js	3600.0 s	14.5 KiB
scripts.clarity.ms/0.8.59/clarity.js	86400.0 s	26.2 KiB
sdk.voyantis.io/d8x0anTvV24UqmERWFnln59AQOsoIyNVo9jf2JY0/vy-cs-sdk.min.js	604800.0 s	98.8 KiB
cdn.speedcurve.com/js/lux.js?id=384343531	3600.0 s	11.3 KiB
tags.srv.stackadapt.com/events.js	5.0 s	8.1 KiB
rp8920cf.semrush.com/assets/wxyz.rb.js	0.0 ms	7.2 KiB
s.yimg.com/wi/ytc.js	0.0 ms	7.1 KiB
static.semrush.com/ajst/ajst.js	3600.0 s	7.5 KiB
js.zi-scripts.com/zi-tag.js	0.0 ms	5.7 KiB
cookiehub.net/c2/css/06c77e2e.css	86400.0 s	11.9 KiB
widget.intercom.io/widget/cs07vi2k	300.0 s	3.6 KiB
munchkin.marketo.net/munchkin.js	0.0 ms	1.2 KiB
js.adsrvr.org/universal_pixel.js	0.0 ms	934 B
/collect?v=2&fmt=js&pid=387538&time=1776798802818&li_adsI...	0.0 ms	453 B
www.semrush.com/jsi18n/	86400.0 s	962 B
/v2/rb?url=https%3A%2F%2Fwww.semrush.com%2F&action=view&s...	0.0 ms	335 B
/v2/rb?url=https%3A%2F%2Fwww.semrush.com%2F&action=identi...	0.0 ms	335 B
getrockerbox.com/jpuid?jsonp=RB.jsonPUID	0.0 ms	276 B
rp8920cf.semrush.com/integrations?source=semrush	0.0 ms	246 B
/gtm_monitoring?eventName=gtm.init&eventTimestamp=1776798...	0.0 ms	187 B
/lux/?v=4.0402&id=384343531&sid=177679880348530237&uid=17...	0.0 ms	101 B
/gtm_monitoring?eventName=show&eventTimestamp=17767988022...	0.0 ms	81 B
/gtm_monitoring?eventName=gtm.js&eventTimestamp=177679880...	0.0 ms	80 B
/lux/?v=4.0402&id=384343531&sid=177679880348530237&uid=17...	0.0 ms	48 B
/tr/?id=239948206198576&ev=PageView&dl=https%3A%2F%2Fwww....	0.0 ms	16 B

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.

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

URL	Time Spent
semrush.com/	1.7 s
www.semrush.com/	0.0 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 935 ms

URL	Time Spent
www.semrush.com/	1.0 s

Diagnostics

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: 300 ms 48.9 KiB

URL	Transfer Size	Est Savings
www.semrush.com/__static__/webpack/header_2026.2d973d026289e6a7.css	29.2 KiB	26.8 KiB
cookiehub.net/c2/css/06c77e2e.css	11.5 KiB	11.4 KiB
www.semrush.com/static/index_rebranding.95296ed8b1dea687d82b.css	16.9 KiB	10.7 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.

URL	Total CPU Time	Script Evaluation	Script Parse
www.semrush.com/	2.9 s	130 ms	25 ms
Unattributable	2.3 s	222 ms	0.0 ms
www.semrush.com/static/index_rebranding.3ddb9d179720404881e5.js	2.1 s	1.7 s	34 ms
www.googletagmanager.com/gtag/js?id=AW-951049332&cx=c&gtm=4e64h1	1.3 s	1.2 s	57 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	977 ms	614 ms	357 ms
js.intercomcdn.com/frame-modern.db2b74ec.js	971 ms	797 ms	92 ms
www.googletagmanager.com/gtag/js?id=G-HYWKMHR981&cx=c&gtm=4e64h1	568 ms	406 ms	158 ms
cdn.cookiehub.eu/c2/06c77e2e.js	548 ms	453 ms	36 ms
sdk.voyantis.io/d8x0anTvV24UqmERWFnln59AQOsoIyNVo9jf2JY0/vy-cs-sdk.min.js	451 ms	337 ms	52 ms
www.googletagmanager.com/gtm.js?id=GTM-5K82J2	442 ms	208 ms	144 ms
www.googletagmanager.com/gtag/js?id=G-BPNLXP3JQG&cx=c&gtm=4e64h1	434 ms	327 ms	74 ms
scripts.clarity.ms/0.8.59/clarity.js	360 ms	331 ms	11 ms
connect.facebook.net/en_US/fbevents.js	255 ms	189 ms	60 ms
/signals/config/239948206198576?v=2.9.303&r=stable&domain...	253 ms	203 ms	30 ms
www.googletagmanager.com/gtag/js?id=DC-6266241&cx=c&gtm=4e64h1	248 ms	194 ms	51 ms
blob:https://www.semrush.com/346db6a3-fbb5-482e-a22f-330ebe267bdb	145 ms	137 ms	1.0 ms
snap.licdn.com/li.lms-analytics/insight.min.js	145 ms	104 ms	36 ms
js.intercomcdn.com/vendor-modern.80eace52.js	96 ms	24 ms	63 ms
widget.intercom.io/widget/cs07vi2k	91 ms	68 ms	21 ms
bat.bing.com/bat.js	80 ms	72 ms	7.1 ms
www.semrush.com/__static__/webpack/2434-2434.2bc50298605f1a51.js	75 ms	59 ms	13 ms
qz9icofk.micpn.com/p/js/1.js	72 ms	61 ms	6.1 ms
getrockerbox.com/customdomain/rp8920cf.semrush.com/wxyz.rb.js	66 ms	53 ms	13 ms
analytics.tiktok.com/i18n/pixel/static/identify_5cff1caf.js	61 ms	41 ms	20 ms
www.semrush.com/__static__/webpack/smrwv.23959eb008f116fd.js	60 ms	29 ms	2.3 ms
tags.srv.stackadapt.com/events.js	59 ms	51 ms	3.0 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.

Category	Time Spent
Script Evaluation	8.4 s
Other	3.8 s
Script Parsing & Compilation	1.5 s
Style & Layout	1.1 s
Garbage Collection	375 ms
Rendering	347 ms
Parse HTML & CSS	139 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reason	Failure type
The page has an unload handler in the main frame.	Actionable
Pages with WebSocket cannot enter back/forward cache.	Pending browser support

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

URL	Transfer Size	Est Savings
js.intercomcdn.com/frame-modern.db2b74ec.js	192.7 KiB	123.7 KiB
js.intercomcdn.com/vendor-modern.80eace52.js	143.3 KiB	85.7 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	109.2 KiB	84.7 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	109.2 KiB	84.7 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	109.2 KiB	84.7 KiB
www.googletagmanager.com/gtag/js?id=G-BPNLXP3JQG&cx=c&gtm=4e64h1	174.8 KiB	68.3 KiB
www.googletagmanager.com/gtag/js?id=G-HYWKMHR981&cx=c&gtm=4e64h1	177.4 KiB	68.0 KiB
sdk.voyantis.io/d8x0anTvV24UqmERWFnln59AQOsoIyNVo9jf2JY0/vy-cs-sdk.min.js	98.4 KiB	63.5 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	109.2 KiB	56.5 KiB
www.googletagmanager.com/gtag/js?id=AW-951049332&cx=c&gtm=4e64h1	146.5 KiB	56.0 KiB
www.googletagmanager.com/gtag/js?id=DC-6266241&cx=c&gtm=4e64h1	131.7 KiB	53.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-5K82J2	215.7 KiB	53.9 KiB
www.semrush.com/static/index_rebranding.3ddb9d179720404881e5.js	64.8 KiB	37.8 KiB
connect.facebook.net/en_US/fbevents.js	96.5 KiB	30.3 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
www.semrush.com/static/index/videos/plg_toolkits.mp4	2.8 MiB
www.googletagmanager.com/gtm.js?id=GTM-5K82J2	216.1 KiB
js.intercomcdn.com/frame-modern.db2b74ec.js	193.3 KiB
www.googletagmanager.com/gtag/js?id=G-HYWKMHR981&cx=c&gtm=4e64h1	177.5 KiB
www.googletagmanager.com/gtag/js?id=G-BPNLXP3JQG&cx=c&gtm=4e64h1	174.8 KiB
www.googletagmanager.com/gtag/js?id=AW-951049332&cx=c&gtm=4e64h1	146.5 KiB
js.intercomcdn.com/vendor-modern.80eace52.js	143.9 KiB
www.googletagmanager.com/gtag/js?id=DC-6266241&cx=c&gtm=4e64h1	131.8 KiB
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwMQ.js	109.8 KiB
sdk.voyantis.io/d8x0anTvV24UqmERWFnln59AQOsoIyNVo9jf2JY0/vy-cs-sdk.min.js	98.8 KiB

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

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 22 user timings

●Avoid long main-thread tasks 20 long tasks found

●Avoid non-composited animations 2 animated elements found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 250 ms

●Server Backend Latencies 980 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

○INP breakdown

○Avoid large layout shifts

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
43T `li.mp-stats__item > div.mp-stats__item-number > div.mp-stats__item-count-wrapper > b.mp-stats__item-count`
Build credibility with the largest database on the market. `div.mp-container > ul.mp-stats__list > li.mp-stats__item > p.mp-stats__item-description`
808M `li.mp-stats__item > div.mp-stats__item-number > div.mp-stats__item-count-wrapper > b.mp-stats__item-count`
Your (secret) market insights superpower. `div.mp-container > ul.mp-stats__list > li.mp-stats__item > p.mp-stats__item-description`
142 `li.mp-stats__item > div.mp-stats__item-number > div.mp-stats__item-count-wrapper > b.mp-stats__item-count`
You’re covered all around the world. `div.mp-container > ul.mp-stats__list > li.mp-stats__item > p.mp-stats__item-description`
213M+ `li.mp-stats__item > div.mp-stats__item-number > div.mp-stats__item-count-wrapper > b.mp-stats__item-count`
Monitor more prompts. Grow your visibility faster. `div.mp-container > ul.mp-stats__list > li.mp-stats__item > p.mp-stats__item-description`

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
US `div.mp-search__input-wrapper > div.flags-wrap > div.flags-select > button.flags-select__dropdown`

○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

●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

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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

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

○Links are distinguishable without relying on color.

○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

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

○`<td>` elements in a large `<table>` have one or more table headers.

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 / Warning	Source
AttributionReporting	snap.licdn.com/li.lms-analytics/insight.min.js
Unload event listeners are deprecated and will be removed.	www.semrush.com/static/index_rebranding.3ddb9d179720404881e5.js line 1, col 67895

●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

●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

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

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.

Link destination	Link Text
www.semrush.com/stats/	Learn more

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`