Skip to content
https://gminsights.com

Lighthouse Desktop

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

76

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.

RequestCache TTLTransfer Size
/l/font?kit=2sDPZGJYnIjSi6H75xkZZE1I0yCmYzzQtuZnEGI&skey=...86400.0 s25.3 KiB
/l/font?kit=2sDPZGJYnIjSi6H75xkZZE1I0yCmYzzQttRnEGI&skey=...86400.0 s25.2 KiB
/l/font?kit=2sDPZGJYnIjSi6H75xkZZE1I0yCmYzzQtjhgEGI&skey=...86400.0 s25.1 KiB
/cdn-cgi/challenge-platform/h/b/scripts/jsd/0b8fb825cb67/...14400.0 s12.9 KiB
/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode....2872.0 s752 B
cdn.jsdelivr.net/gh/lipis/flag-icons/flags/4x3/fr.svg604800.0 s594 B

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.

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.

URLEst Savings
www.gminsights.com/_next/static/media/fontawesome-webfont.e9955780.woff235 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
Logo 12 div.jsx-409577639 > div.jsx-409577639 > div.jsx-409577639 > img.jsx-409577639
cdn.gminsights.com/company/Unilever.png62.1 KiB61.9 KiB
Global Market Insights citation in CNBC div.mediaCitiaonsImages > a > div.mediCitainInnerImage > img
cdn.gminsights.com/media_citation/cnbc.jpg20.7 KiB20.3 KiB
Logo 0 div.jsx-409577639 > div.jsx-409577639 > div.jsx-409577639 > img.jsx-409577639
cdn.gminsights.com/company/Accenture.webp19.7 KiB19.7 KiB
Logo 10 div.jsx-409577639 > div.jsx-409577639 > div.jsx-409577639 > img.jsx-409577639
cdn.gminsights.com/company/TexasInstruments-Logo.png19.5 KiB18.6 KiB
Global Market Insights citation in BBC div.mediaCitiaonsImages > a > div.mediCitainInnerImage > img
cdn.gminsights.com/media_citation/bbc.png17.3 KiB17.3 KiB
Logo 2 div.jsx-409577639 > div.jsx-409577639 > div.jsx-409577639 > img.jsx-409577639
cdn.gminsights.com/company/Deloitte.png11.3 KiB10.9 KiB
Logo 8 div.jsx-409577639 > div.jsx-409577639 > div.jsx-409577639 > img.jsx-409577639
cdn.gminsights.com/company/Samsung_wordmark.png10.0 KiB9.7 KiB
Logo 5 div.jsx-409577639 > div.jsx-409577639 > div.jsx-409577639 > img.jsx-409577639
cdn.gminsights.com/company/Microsoft_logo.png9.3 KiB9.2 KiB
Logo 1 div.jsx-409577639 > div.jsx-409577639 > div.jsx-409577639 > img.jsx-409577639
cdn.gminsights.com/company/Cognizant_logo_2022.png9.6 KiB8.9 KiB
Logo 11 div.jsx-409577639 > div.jsx-409577639 > div.jsx-409577639 > img.jsx-409577639
cdn.gminsights.com/company/Toyota.png8.6 KiB8.3 KiB
Logo 9 div.jsx-409577639 > div.jsx-409577639 > div.jsx-409577639 > img.jsx-409577639
cdn.gminsights.com/company/Sony_logo.png8.5 KiB8.2 KiB
Logo 4 div.jsx-409577639 > div.jsx-409577639 > div.jsx-409577639 > img.jsx-409577639
cdn.gminsights.com/company/JPMorganChase.png6.5 KiB5.9 KiB
Logo 7 div.jsx-409577639 > div.jsx-409577639 > div.jsx-409577639 > img.jsx-409577639
cdn.gminsights.com/company/Panasonic_logo.png5.0 KiB4.5 KiB
Logo 3 div.jsx-409577639 > div.jsx-409577639 > div.jsx-409577639 > img.jsx-409577639
cdn.gminsights.com/company/Hitachi_logo.png4.5 KiB4.3 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

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: 250 ms
URLTime Spent
gminsights.com/250 ms
www.gminsights.com/0.0 ms

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 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: 80 ms 139.9 KiB
URLTransfer SizeEst Savings
www.gminsights.com/_next/static/css/a6b884ee55a2c17e.css146.8 KiB139.9 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 290 ms 563.9 KiB
URLTransfer SizeEst Savings
www.gminsights.com/_next/static/chunks/9810-9540bbf2dcedc951.js295.9 KiB184.5 KiB
www.googletagmanager.com/gtag/js?id=G-F01HGT5N4X&cx=c&gtm=4e64m0h2174.0 KiB63.7 KiB
www.googletagmanager.com/gtm.js?id=GTM-TKV3WHJ147.8 KiB63.2 KiB
www.googletagmanager.com/gtag/js?id=AW-730798613&cx=c&gtm=4e64m0h2143.7 KiB62.7 KiB
www.gminsights.com/_next/static/chunks/2669-a8c29b36c62a9e83.js45.3 KiB44.6 KiB
www.gminsights.com/_next/static/chunks/5904-c6a4b3a46e6bf637.js52.7 KiB39.2 KiB
www.gminsights.com/_next/static/chunks/2445-daeb9c4415a11889.js37.1 KiB36.8 KiB
www.gminsights.com/_next/static/chunks/3959-28ac55d255e6e118.js36.4 KiB35.7 KiB
www.gminsights.com/_next/static/chunks/framework-01be286159f12911.js64.8 KiB33.5 KiB

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 reasonFailure type
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable
Pages whose main resource has cache-control:no-store cannot enter back/forward cache.Not actionable
Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header.Not actionable

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 27.0 KiB
URLTransfer SizeEst Savings
www.gminsights.com/_next/static/css/a6b884ee55a2c17e.css147.0 KiB27.0 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
Global Market Insights citation in BBC div.mediaCitiaonsImages > a > div.mediCitainInnerImage > img
cdn.gminsights.com/media_citation/bbc.png
Global Market Insights citation in CNBC div.mediaCitiaonsImages > a > div.mediCitainInnerImage > img
cdn.gminsights.com/media_citation/cnbc.jpg
Global Market Insights featured in Business Insider div.mediaCitiaonsImages > a > div.mediCitainInnerImage > img
cdn.gminsights.com/media_citation/businessinsider_com.png
Global Market Insights featured in Times of India, Indiatimes div.mediaCitiaonsImages > a > div.mediCitainInnerImage > img
cdn.gminsights.com/media_citation/timesofindia_indiatimes_com.png
Global Market Insights featured in National Geographic div.mediaCitiaonsImages > a > div.mediCitainInnerImage > img
cdn.gminsights.com/media_citation/nationalgeographic_com.png
Global Market Insights citation in Investing div.mediaCitiaonsImages > a > div.mediCitainInnerImage > img
cdn.gminsights.com/media_citation/investing.png

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

●Max Potential First Input Delay 80 ms
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify JavaScript
●Avoids enormous network payloads Total size was 2,568 KiB
●User Timing marks and measures 9 user timings
●JavaScript execution time 0.4 s
●Minimizes main-thread work 1.1 s
●Avoid long main-thread tasks 3 long tasks found
●Network Requests
●Network Round Trip Times 40 ms
●Server Backend Latencies 140 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 580 ms
○INP breakdown
○LCP request discovery
○Avoid non-composited animations
○Avoid large layout shifts
84

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn

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.

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
Published: April 2026 div.image_box > div.authour_details > p > a
Published: April 2026 div.image_box > div.authour_details > p > a
Published: April 2026 div.image_box > div.authour_details > p > a
Explore All Reports div.row > div > a > div.search-button
Privacy Policy div#page > div.CookieConsent > div > a

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
Yutaka Hosoyamada div.card-body > div.d-flex > div > h6.mb-0

These are opportunities to improve keyboard navigation in your application.

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
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn
div.container > div.position-relative > div.d-flex > button.btn div.container > div.position-relative > div.d-flex > button.btn

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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 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
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<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.
○No element has a `[tabindex]` value greater than 0
○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
○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.
58

Best Practices

Trust and Safety

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
cdn.gminsights.com/home/slider_image_one.webpAutomatically upgraded to HTTPS

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 / WarningSource
SharedStorage
www.gminsights.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
www.gminsights.com/cdn-cgi/challenge-platform/scripts/jsd/main.js
Fledge
www.gminsights.com/cdn-cgi/challenge-platform/scripts/jsd/main.js

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
Mixed content

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
www.gminsights.com/_next/static/chunks/2266-107a2dca37360e35.js
●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
●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
100

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.

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

Send Feedback