https://flarelighters.com/product-category/custom-lighter/

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
cdn.refersion.com/refersion.js	0.0 ms	22.0 KiB
s.pinimg.com/ct/lib/main.c61fa7c9.js	1209600.0 s	37.6 KiB
cdn.refersion.com/xdlspma.min.js	0.0 ms	3.0 KiB
s.pinimg.com/ct/core.js	7200.0 s	2.2 KiB
ct.pinterest.com/static/ct/token_create.js	7200.0 s	2.1 KiB

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:46.896 source:map[column:325 line:30 type:source-location url:https://flarelighters.com/product-category/custom-lighter/ 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:0.118 source:map[type:text value:[unattributed]]] map[reflowTime:43.701 source:map[column:28 line:32 type:source-location url:https://flarelighters.com/product-category/custom-lighter/ urlProvider:network]] map[reflowTime:3.195 source:map[column:256 line:32 type:source-location url:https://flarelighters.com/product-category/custom-lighter/ urlProvider:network]]]

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-0-IMG

nodeLabel: Custom 360 degree full-wrap photo-printed lighter collection

path: 1,HTML,1,BODY,1,DIV,1,MAIN,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,FIGURE,0,IMG

selector: div.elementor-element > div.elementor-widget-container > figure.wp-caption > img.lzl-ed

snippet: <img src="https://flarelighters.com/wp-content/uploads/2026/02/Custom-Lighters-110.w…" alt="Custom 360 degree full-wrap photo-printed lighter collection" class="lzl-ed lzl-cached" data-lzl-src="https://flarelighters.com/wp-content/uploads/2026/02/Custom-Lighters-110.w…">

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

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

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
/wp-content/plugins/woocommerce/assets/js/jquery-blockui/...	3.4 KiB
flarelighters.com/wp-content/plugins/slicewp/assets/js/script-trk.js	1.3 KiB
/wp-content/plugins/woocommerce/assets/js/js-cookie/js.co...	1007 B
flarelighters.com/wp-includes/js/jquery/jquery-migrate.min.js	4.8 KiB
flarelighters.com/wp-content/plugins/elementor/assets/js/frontend.min.js	18.0 KiB
flarelighters.com/wp-content/plugins/elementor/assets/js/frontend-modules.min.js	15.7 KiB
/wp-content/plugins/google-site-kit/dist/assets/js/google...	24.3 KiB
/wp-content/plugins/elementor-pro/assets/lib/sticky/jquer...	1.7 KiB
/wp-content/plugins/elementor-pro/assets/lib/smartmenus/j...	6.9 KiB
flarelighters.com/wp-includes/js/jquery/ui/core.min.js	6.4 KiB
flarelighters.com/wp-content/plugins/elementor/assets/js/webpack.runtime.min.js	330 B
/wp-content/plugins/woocommerce/assets/js/frontend/woocom...	1.6 KiB
/wp-content/plugins/google-site-kit/dist/assets/js/sign-i...	1.4 KiB
flarelighters.com/wp-includes/js/jquery/jquery.min.js	29.2 KiB	80 ms
flarelighters.com/wp-content/plugins/refersion-for-woocommerce/rfsn_v4_main.js	489 B
accounts.google.com/gsi/client	100.6 KiB

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
Custom 360 degree full-wrap photo-printed lighter collection `div.elementor-element > div.elementor-widget-container > figure.wp-caption > img.lzl-ed`	flarelighters.com/wp-content/uploads/2026/02/Custom-Lighters-110.webp	50.4 KiB	7.0 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: 742 ms

URL	Time Spent
flarelighters.com/product-category/custom-lighter/	740 ms
/.well-known/sgcaptcha/?r=%2Fproduct-category%2Fcustom-li...	2.0 ms
/.well-known/sgcaptcha/?r=%2Fproduct-category%2Fcustom-li...	0.0 ms
flarelighters.com/product-category/custom-lighter/	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
	0.102
Showing 1–12 of 15 results Default sorting Sort by popularity Sort by average … `div.e-con-inner > div.elementor-element > div.elementor-element > div.elementor-widget-container`	0.017
Custom Brass Armor Lighter – CNC Engraved $54.99 ADD TO CART `div.elementor-widget-container > div.woocommerce > ul.products > li.product`	0.003
CUSTOM LIGHTERS `div.e-con-inner > div.elementor-element > div.elementor-widget-container > h1.elementor-heading-title`	0.001
1-Year Warranty: Complimentary coverage for all lighters! `div.elementor-element > div.elementor-widget-container > ul.elementor-icon-list-items > li.elementor-icon-list-item`	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

Diagnostics

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: 410 ms 268.3 KiB

URL	Transfer Size	Est Savings
accounts.google.com/gsi/client	99.8 KiB	78.3 KiB
www.googletagmanager.com/gtag/js?id=GT-MQR2CB2H	176.2 KiB	72.8 KiB
/wp-content/plugins/elementor-pro/assets/js/elements-hand...	65.7 KiB	60.6 KiB
/wp-content/plugins/elementor/assets/lib/swiper/v8/swiper...	36.7 KiB	35.5 KiB
flarelighters.com/wp-content/plugins/elementor-pro/assets/js/frontend.min.js	23.3 KiB	21.2 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 3.7 KiB

URL	Transfer Size	Est Savings
inline: (function(){ 'use strict'; functi…	13.7 KiB	3.7 KiB

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: 0.0 ms 10.7 KiB

URL	Transfer Size	Est Savings
/wp-content/cache/seraphinite-accelerator/s/m/d/css/75141...	10.7 KiB	10.7 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
Custom 360 degree full-wrap photo-printed lighter collection `div.elementor-element > div.elementor-widget-container > figure.wp-caption > img.lzl-ed`	flarelighters.com/wp-content/uploads/2026/02/Custom-Lighters-110.webp

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

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 20 ms

●Minify CSS

●Avoids enormous network payloads Total size was 1,137 KiB

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.9 s

●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 150 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
FILTERS Clear all Close VIEW RESULTS SORT Close VIEW RESULTS `body#neve_body > div.flareOverlay`

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
form#mc4wp-form-1 > div.mc4wp-form-fields > p > input `form#mc4wp-form-1 > div.mc4wp-form-fields > p > input`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
JOIN THE VIP LIST `div.e-con-inner > div.elementor-element > div.elementor-widget-container > h4.elementor-heading-title`
Customer Care `div.elementor-element > div.elementor-element > div.elementor-widget-container > h6.elementor-heading-title`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.elementor-widget-container > div.elementor-social-icons-wrapper > span.elementor-grid-item > a.elementor-icon `div.elementor-widget-container > div.elementor-social-icons-wrapper > span.elementor-grid-item > a.elementor-icon`

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search `div.elementor-widget-container > search > form.elementor-search-form > div.elementor-search-form__toggle`

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

●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

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

●Select elements have associated label elements.

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

●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

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

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

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

○Identical links have the same purpose.

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

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

100

Best Practices

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #	Content	Error
1	`<html><head><link rel="icon" href="data:;"><meta http-equiv="refresh" content="0;/.well-known/sgcaptcha/?r=%2Frobots.txt&y=ipc:141.227.188.120:1793074241.191"></meta></head></html>`	`Unknown directive`

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

○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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`