Skip to content
https://sureflo.in

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

64

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.

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.

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
div.fusion-column-wrapper > div.fusion-image-element > span.fusion-imageframe > img.img-responsive div.fusion-column-wrapper > div.fusion-image-element > span.fusion-imageframe > img.img-responsive
sureflo.in/wp-content/uploads/2026/08/Sureflo-Factory-responsive-800x674.jpg218.3 KiB195.1 KiB
sureflo_logo div.fusion-column-wrapper > div.fusion-image-element > span.fusion-imageframe > img.img-responsive
sureflo.in/wp-content/uploads/2026/05/sureflo_logo-200x161.png15.7 KiB10.5 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:1139.683 label:Time to first byte subpart:timeToFirstByte] map[duration:915.502 label:Resource load delay subpart:resourceLoadDelay] map[duration:849.556 label:Resource load duration subpart:resourceLoadDuration] map[duration:42.721 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: div.fusion-column-wrapper > div.fusion-image-element > span.fusion-imageframe > img.img-responsive
path: 1,HTML,1,BODY,2,DIV,0,DIV,3,MAIN,0,DIV,0,SECTION,0,DIV,3,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,SPAN,0,IMG
selector: div.fusion-column-wrapper > div.fusion-image-element > span.fusion-imageframe > img.img-responsive
snippet: <img decoding="async" width="831" height="700" src="https://sureflo.in/wp-content/uploads/2026/08/Sureflo-Factory-responsive-8…" data-orig-src="https://sureflo.in/wp-content/uploads/2026/08/Sureflo-Factory-responsive.j…" alt="" class="img-responsive wp-image-2615 lazyautosizes lazyloaded" srcset="https://sureflo.in/wp-content/uploads/2026/08/Sureflo-Factory-responsive-2…" data-srcset="https://sureflo.in/wp-content/uploads/2026/08/Sureflo-Factory-responsive-2…" data-sizes="auto" data-orig-sizes="(max-width: 640px) 100vw, 831px" sizes="412px">

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: div.fusion-column-wrapper > div.fusion-image-element > span.fusion-imageframe > img.img-responsive
path: 1,HTML,1,BODY,2,DIV,0,DIV,3,MAIN,0,DIV,0,SECTION,0,DIV,3,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,SPAN,0,IMG
selector: div.fusion-column-wrapper > div.fusion-image-element > span.fusion-imageframe > img.img-responsive
snippet: <img decoding="async" width="831" height="700" src="https://sureflo.in/wp-content/uploads/2026/08/Sureflo-Factory-responsive-8…" data-orig-src="https://sureflo.in/wp-content/uploads/2026/08/Sureflo-Factory-responsive.j…" alt="" class="img-responsive wp-image-2615 lazyautosizes lazyloaded" srcset="https://sureflo.in/wp-content/uploads/2026/08/Sureflo-Factory-responsive-2…" data-srcset="https://sureflo.in/wp-content/uploads/2026/08/Sureflo-Factory-responsive-2…" data-sizes="auto" data-orig-sizes="(max-width: 640px) 100vw, 831px" sizes="412px">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

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.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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: 996 ms
URLTime Spent
sureflo.in/1.1 s

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: 1.1 s 145.5 KiB
URLTransfer SizeEst Savings
/wp-content/uploads/fusion-styles/31906c55899e82dade0286e...161.3 KiB145.5 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: 600 ms 141.1 KiB
URLTransfer SizeEst Savings
/wp-content/uploads/fusion-scripts/c6c41df8ee14ec1b708f64...185.3 KiB141.1 KiB

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

Max Potential First Input Delay 90 ms
Layout shift culprits
Optimize DOM size
Forced reflow
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 1,068 KiB
JavaScript execution time 0.5 s
Minimizes main-thread work 1.7 s
Avoid long main-thread tasks 3 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 50 ms
Server Backend Latencies 380 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Avoid large layout shifts 1 layout shift found
INP breakdown
User Timing marks and measures
Avoid non-composited animations
94

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
Founded · Mumbai HQ div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-text > p
AVGF units worldwide div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-text > p
Robotic cleaning systems div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-text > p
9001 · 14001 · 45001 div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-text > p
WHAT WE DO div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-title > h2.fusion-title-heading
01 – WE MANUFACTURE div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-title > h3.fusion-title-heading
02 – WE PERFORM ON-SITE div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-title > h3.fusion-title-heading
DOCUMENTED, NOT CLAIMED div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-title > h2.fusion-title-heading
MT div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-title > h4.fusion-title-heading
div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-title > h4.fusion-title-heading
TRUSTED BY div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-title > h2.fusion-title-heading

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
2011 div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-title > h3.fusion-title-heading
EQUIPMENT div.fusion-layout-column > div.fusion-column-wrapper > div.fusion-title > h6.fusion-title-heading

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>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[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
`<frame>` or `<iframe>` elements have a title
`<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.
Skip links are focusable.
Document has a main landmark.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
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
`[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
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 buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
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.
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.
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.
100

Best Practices

General

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.

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
Redirects HTTP traffic to HTTPS
92

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
Indian Oil div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button
Bharat Petroleum div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button
HPCL div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button
SAIL div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button
NMDC div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button
JSW div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button
TATA div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button
L&T div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button
IFFCO div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button
MAHAGENCO div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button
PAHARPUR COOLING TOWERS div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button
NTPC div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button
RIL div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button
ADANI div.fusion-layout-column > div.fusion-column-wrapper > div > a.fusion-button

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

Send Feedback