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.

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:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:0.793 source:map[column:14445 line:15 type:source-location url: urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:24.122 source:map[column:85417 line:27 type:source-location url:https://explodingtopics.com/_next/static/chunks/commons.50fb11ba8b2d24b63379.js urlProvider:network]] map[reflowTime:5.468 source:map[column:170474 line:27 type:source-location url:https://explodingtopics.com/_next/static/chunks/commons.50fb11ba8b2d24b63379.js urlProvider:network]] map[reflowTime:2.506 source:map[column:151574 line:27 type:source-location url:https://explodingtopics.com/_next/static/chunks/commons.50fb11ba8b2d24b63379.js urlProvider:network]] map[reflowTime:31.547 source:map[type:text value:[unattributed]]] map[reflowTime:0.63 source:map[column:379595 line:19 type:source-location url: urlProvider:network]] map[reflowTime:0.793 source:map[column:6903 line:14 type:source-location url: urlProvider:network]]]

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
Hero image `section.landingHero > div.landingHeroWrapper > picture > img`	explodingtopics.com/static/images/home-page/background-360w.webp	107.8 KiB	76.1 KiB
pickleball `section.landingHero > div.trendingInsights > div.trendingInsightsImg > img`	explodingtopics.com/static/images/sales/pickleball.webp	31.8 KiB	19.2 KiB
perplexity `section.landingHero > div.trendingInsights > div.trendingInsightsImg > img`	explodingtopics.com/static/images/sales/perplexity-ai.webp	27.3 KiB	16.5 KiB

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
explodingtopics.com/static/css/index.7f2ec86c.css	120.8 KiB	2.6 s
explodingtopics.com/static/css/slick.66c413dd.css	1.9 KiB	660 ms
cdnjs.cloudflare.com/polyfill/v3/polyfill.min.js	750 B	890 ms
fonts.googleapis.com/css2?family=Coming+Soon&display=swap	879 B	154 ms
/css2?family=Manrope:wght@200;300;400;500;600;700;800&dis...	912 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
dash.sparkloop.app/styles/default.css	0.0 ms	20.1 KiB
cdn.cookiehub.eu/c2/b3596e70.js	86400.0 s	38.3 KiB
scripts.clarity.ms/0.8.59/clarity.js	86400.0 s	26.2 KiB
explodingtopics.sfo2.digitaloceanspaces.com/Notegpt-01apq.png	0.0 ms	10.4 KiB
explodingtopics.sfo2.digitaloceanspaces.com/Rosebud%20AI-h6tb6h.png	0.0 ms	10.2 KiB
/dcdn/settings.js?a=1074303&settings_type=4&ts=1776871228...	1800.0 s	11.2 KiB
cdn.cookiehub.eu/c2/css/b3596e70.css	86400.0 s	15.9 KiB
explodingtopics.sfo2.digitaloceanspaces.com/Lovable-q7z1o.png	0.0 ms	4.0 KiB
/faviconV2?client=SOCIAL&type=FAVICON&fallback_opts=TYPE,...	604800.0 s	8.2 KiB
/faviconV2?client=SOCIAL&type=FAVICON&fallback_opts=TYPE,...	604800.0 s	7.3 KiB
/faviconV2?client=SOCIAL&type=FAVICON&fallback_opts=TYPE,...	604800.0 s	2.8 KiB
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.3 KiB
cdnjs.cloudflare.com/polyfill/v3/polyfill.min.js	604800.0 s	750 B
/v.gif?cd=0&a=1074303&d=explodingtopics.com&u=D48654023D0...	43200.0 s	147 B

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	5.0 ms

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.

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: 480 ms 146.5 KiB

URL	Transfer Size	Est Savings
explodingtopics.com/static/css/index.7f2ec86c.css	120.2 KiB	112.9 KiB
dash.sparkloop.app/styles/default.css	19.5 KiB	19.5 KiB
cdn.cookiehub.eu/c2/css/b3596e70.css	15.1 KiB	14.1 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
explodingtopics.com/_next/static/chunks/commons.50fb11ba8b2d24b63379.js	4.0 s	2.0 s	235 ms
explodingtopics.com/	3.1 s	954 ms	24 ms
cdn.cookiehub.eu/c2/b3596e70.js	2.0 s	1.9 s	35 ms
explodingtopics.com/_next/static/runtime/main-518f9fb1c232f3d651de.js	1.7 s	1.6 s	3.4 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	1.4 s	1.3 s	137 ms
Unattributable	832 ms	60 ms	0.0 ms
www.googletagmanager.com/gtag/js?id=G-WZRQZRZ1GQ&cx=c&gtm=4e64k1h2	516 ms	428 ms	85 ms
www.googletagmanager.com/gtm.js?id=GTM-W6CJTVL	489 ms	397 ms	64 ms
scripts.clarity.ms/0.8.59/clarity.js	457 ms	371 ms	17 ms
explodingtopics.com/_next/static/gpiFlIfpBLqpmr8YAz9U5/pages/tools/toolView.js	416 ms	164 ms	250 ms
www.googletagmanager.com/gtag/js?id=G-8Q4RX1151X&cx=c&gtm=4e64k1h2	303 ms	234 ms	67 ms
explodingtopics.com/_next/static/gpiFlIfpBLqpmr8YAz9U5/pages/blog/post.js	219 ms	13 ms	205 ms
explodingtopics.com/_next/static/gpiFlIfpBLqpmr8YAz9U5/pages/topic/post.js	94 ms	28 ms	65 ms
explodingtopics.com/static/css/index.7f2ec86c.css	86 ms	0.0 ms	0.0 ms
explodingtopics.com/_next/static/gpiFlIfpBLqpmr8YAz9U5/pages/index.js	86 ms	2.1 ms	83 ms
js.sparkloop.app/team_d3721becc8bb.js	55 ms	33 ms	18 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	10.5 s
Other	3.1 s
Script Parsing & Compilation	1.6 s
Style & Layout	1.3 s
Rendering	381 ms
Garbage Collection	203 ms
Parse HTML & CSS	193 ms

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 1.2 MiB

URL	Transfer Size	Est Savings
explodingtopics.com/_next/static/gpiFlIfpBLqpmr8YAz9U5/pages/blog/post.js	262.5 KiB	260.7 KiB
explodingtopics.com/_next/static/gpiFlIfpBLqpmr8YAz9U5/pages/tools/toolView.js	259.2 KiB	207.6 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.8 KiB	175.9 KiB
explodingtopics.com/_next/static/gpiFlIfpBLqpmr8YAz9U5/pages/topic/post.js	126.0 KiB	119.7 KiB
explodingtopics.com/_next/static/chunks/commons.50fb11ba8b2d24b63379.js	300.7 KiB	114.5 KiB
explodingtopics.com/_next/static/gpiFlIfpBLqpmr8YAz9U5/pages/index.js	114.9 KiB	86.2 KiB
www.googletagmanager.com/gtag/js?id=G-8Q4RX1151X&cx=c&gtm=4e64k1h2	145.9 KiB	72.8 KiB
www.googletagmanager.com/gtag/js?id=G-WZRQZRZ1GQ&cx=c&gtm=4e64k1h2	173.9 KiB	71.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-W6CJTVL	133.0 KiB	59.7 KiB
js.sparkloop.app/team_d3721becc8bb.js	35.9 KiB	22.9 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.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	362.4 KiB
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js	361.9 KiB
explodingtopics.com/_next/static/chunks/commons.50fb11ba8b2d24b63379.js	301.2 KiB
explodingtopics.com/_next/static/gpiFlIfpBLqpmr8YAz9U5/pages/blog/post.js	264.8 KiB
explodingtopics.com/_next/static/gpiFlIfpBLqpmr8YAz9U5/pages/tools/toolView.js	261.4 KiB
explodingtopics.com/static/images/home-page/background-768w.webp	222.1 KiB
www.googletagmanager.com/gtag/js?id=G-WZRQZRZ1GQ&cx=c&gtm=4e64k1h2	173.9 KiB
www.googletagmanager.com/gtag/js?id=G-8Q4RX1151X&cx=c&gtm=4e64k1h2	145.9 KiB
www.googletagmanager.com/gtag/js?id=GTM-W6CJTVL	133.4 KiB
www.googletagmanager.com/gtm.js?id=GTM-W6CJTVL	133.1 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
mlops `section.landingHero > div.trendingInsights > div.trendingInsightsImg > img`	explodingtopics.com/static/images/sales/Mlops.webp
pickleball `section.landingHero > div.trendingInsights > div.trendingInsightsImg > img`	explodingtopics.com/static/images/sales/pickleball.webp
substack `section.landingHero > div.trendingInsights > div.trendingInsightsImg > img`	explodingtopics.com/static/images/sales/substack.webp
snail-mucin `section.landingHero > div.trendingInsights > div.trendingInsightsImg > img`	explodingtopics.com/static/images/sales/Snail-mucin.webp
air-fryer `section.landingHero > div.trendingInsights > div.trendingInsightsImg > img`	explodingtopics.com/static/images/sales/air-fryer.webp
perplexity `section.landingHero > div.trendingInsights > div.trendingInsightsImg > img`	explodingtopics.com/static/images/sales/perplexity-ai.webp
div.grid > div.trendCard > div.trendCardInner > img `div.grid > div.trendCard > div.trendCardInner > img`	explodingtopics.com/static/images/home-page/identify-trends.svg
div.grid > div.trendCard > div.trendCardInner > img `div.grid > div.trendCard > div.trendCardInner > img`	explodingtopics.com/static/images/home-page/analyze-trends.svg
div.grid > div.trendCard > div.trendCardInner > img `div.grid > div.trendCard > div.trendCardInner > img`	explodingtopics.com/static/images/home-page/curate-trends.svg
Graph Trend `div.articleCardInner > div.articleImage > div.articleImageWrapper > img.articleImage`
Graph Trend `div.articleCardInner > div.articleImage > div.articleImageWrapper > img.articleImage`
Graph Trend `div.articleCardInner > div.articleImage > div.articleImageWrapper > img.articleImage`
Graph Trend `div.articleCardInner > div.articleImage > div.articleImageWrapper > img.articleImage`

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

●LCP breakdown

●LCP request discovery

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 5 user timings

●Avoid long main-thread tasks 20 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 140 ms

●Server Backend Latencies 180 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 560 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○Avoid non-composited animations

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
2 Years `div.filterContainer > div.trendDbPageButtonDropdown > div.dropdownFilterButton > span.filterButtonText`
All Categories `div.filterContainer > div.trendDbPageButtonDropdown > div.dropdownFilterButton > span.filterButtonText`
Volume `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom`
+99X+ `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagTop`
Growth `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom`
Volume `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom`
+99X+ `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagTop`
Growth `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom`
Volume `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom`
+1567% `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagTop`
Growth `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom`
Volume `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom`
+900% `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagTop`
Growth `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom`
Volume `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom`
+900% `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagTop`
Growth `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom`
Volume `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom`
+875% `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagTop`
Growth `div.scoresContainer > div.scoresInnerContainer > div.scoreTag > div.scoreTagBottom`
April 22, 2026 `div.articleCard > div.articleCardInner > div.articleContent > p.articleDate`
April 17, 2026 `div.articleCard > div.articleCardInner > div.articleContent > p.articleDate`
April 14, 2026 `div.articleCard > div.articleCardInner > div.articleContent > p.articleDate`
April 9, 2026 `div.articleCard > div.articleCardInner > div.articleContent > p.articleDate`

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
div.grid > div.trendCard > div.trendCardInner > img `div.grid > div.trendCard > div.trendCardInner > img`
div.grid > div.trendCard > div.trendCardInner > img `div.grid > div.trendCard > div.trendCardInner > img`
div.grid > div.trendCard > div.trendCardInner > img `div.grid > div.trendCard > div.trendCardInner > img`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.megaMenuWrapper > div.megaMenuInnerWrapper > div.megaMenuTop > a.logo `div.megaMenuWrapper > div.megaMenuInnerWrapper > div.megaMenuTop > a.logo`
div.container > div.pagerAndResultsContainer > div.pagination-container > a.pagerButton `div.container > div.pagerAndResultsContainer > div.pagination-container > a.pagerButton`
div.container > div.pagerAndResultsContainer > div.pagination-container > a.pagerButton `div.container > div.pagerAndResultsContainer > div.pagination-container > a.pagerButton`
div.container > div.footer_bottom > div.footer_logo > a `div.container > div.footer_bottom > div.footer_logo > a`

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#af-form-1686512983 > div#af-body-1686512983 > div.newsletter_form_inner > input#awf_field-113227448 `div#af-form-1686512983 > div#af-body-1686512983 > div.newsletter_form_inner > input#awf_field-113227448`
div#af-form-1686512983 > div#af-body-1686512983 > div.newsletter_form_inner > input.submit `div#af-form-1686512983 > div#af-body-1686512983 > div.newsletter_form_inner > input.submit`

These are opportunities to improve keyboard navigation in your application.

○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

●Input buttons have discernible text.

●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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

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

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

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

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

○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

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
Hero image `section.landingHero > div.landingHeroWrapper > picture > img`	explodingtopics.com/static/images/home-page/background-360w.webp	412 x 523 (0.79)	360 x 540 (0.67)

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Displayed size	Actual size	Expected size
Hero image `section.landingHero > div.landingHeroWrapper > picture > img`	explodingtopics.com/static/images/home-page/background-360w.webp	412 x 523	360 x 540	618 x 785

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
explodingtopics.com/	`Access to fetch at 'https://www.semrush.com/olaf/init' from origin 'https://explodingtopics.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.`
www.semrush.com/olaf/init	`Failed to load resource: net::ERR_FAILED`

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
explodingtopics.com/_next/static/gpiFlIfpBLqpmr8YAz9U5/pages/tools/toolView.js
explodingtopics.com/_next/static/gpiFlIfpBLqpmr8YAz9U5/pages/blog/post.js
explodingtopics.com/_next/static/chunks/commons.50fb11ba8b2d24b63379.js

●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

●Page has the HTML doctype

●Properly defines charset

●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 clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

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

Content Best Practices

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
div.grid > div.trendCard > div.trendCardInner > img `div.grid > div.trendCard > div.trendCardInner > img`
div.grid > div.trendCard > div.trendCardInner > img `div.grid > div.trendCard > div.trendCardInner > img`
div.grid > div.trendCard > div.trendCardInner > img `div.grid > div.trendCard > div.trendCardInner > img`

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 have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`