Skip to content
https://amittravelsjbp.netlify.app

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.

65

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.

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
Ertiga - MPV taxi in Jabalpur div.grid > div.fleet-card > div.fleet-image > img
amittravelsjbp.netlify.app/Ertiga.png1.6 MiB1.6 MiB
Tempo Traveller - Mini Bus taxi in Jabalpur div.grid > div.fleet-card > div.fleet-image > img
amittravelsjbp.netlify.app/Tempo_Traveller.png1.5 MiB1.5 MiB
Swift Dzire - Sedan taxi in Jabalpur div.grid > div.fleet-card > div.fleet-image > img
amittravelsjbp.netlify.app/Dzire.png1.3 MiB1.3 MiB
Amit Travels logo header.site-header > div.container > a.logo-block > img.logo-img
amittravelsjbp.netlify.app/logo.png1.3 MiB1.3 MiB
Innova Crysta - Premium MPV taxi in Jabalpur div.grid > div.fleet-card > div.fleet-image > img
amittravelsjbp.netlify.app/Innova_Crysta.png1.2 MiB1.2 MiB
Force Urbania premium van interior main > section#urbania > div.urbania-bg > img
amittravelsjbp.netlify.app/Urbania.png1.2 MiB1.1 MiB
Dhuandhar Falls sightseeing in Jabalpur div.grid > div.sight-card > div.sight-image > img
/photos/39256059/pexels-photo-39256059.jpeg?auto=compress...86.7 KiB74.2 KiB
Marble Rocks – Bhedaghat sightseeing in Jabalpur div.grid > div.sight-card > div.sight-image > img
/photos/10483174/pexels-photo-10483174.jpeg?auto=compress...68.0 KiB53.2 KiB
Balance Rock sightseeing in Jabalpur div.grid > div.sight-card > div.sight-image > img
/photos/10483147/pexels-photo-10483147.jpeg?auto=compress...42.1 KiB30.9 KiB
Kachnar Shiv Temple sightseeing in Jabalpur div.grid > div.sight-card > div.sight-image > img
/photos/35775959/pexels-photo-35775959.jpeg?auto=compress...40.0 KiB29.5 KiB
Comfortable highway travel with Amit Travels taxi service in Jabalpur div.container > div.intro-grid > div.intro-image > img
/photos/3576685/pexels-photo-3576685.jpeg?auto=compress&c...11.2 KiB4.1 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.

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.

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 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: 700 ms 99.7 KiB
URLTransfer SizeEst Savings
amittravelsjbp.netlify.app/assets/index-C1wlI81J.js169.8 KiB99.7 KiB

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

●Use efficient cache lifetimes
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●JavaScript execution time 0.4 s
●Minimizes main-thread work 1.5 s
●Avoid long main-thread tasks 6 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 30 ms
●Server Backend Latencies 480 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 140 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
○Avoid large layout shifts
79

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
WhatsApp div.container > nav.nav-menu > div.nav-cta-mobile > a.btn
WhatsApp Now div.container > div.hero-text > div.hero-cta > a.btn
Book on WhatsApp section.final-cta-section > div.container > div.cta-buttons > a.btn
© 2026 Amit Travels – Car Rental in Jabalpur. All rights reserved. footer.footer > div.container > div.footer-bottom > p

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
Get Instant Quote div.hero-form-wrap > div#booking-form-section > form.booking-form > h3
Safe Travel div.container > div.grid > div.trust-card > h4
Luxury Pushback Seats div.container > div.grid > div.urbania-card > h4
Airport Pickup & Drop div.container > div.grid > div.service-card > h4
Address div.contact-info > div.contact-card > div > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form.booking-form > div.bf-grid > div.bf-field > input form.booking-form > div.bf-grid > div.bf-field > input
form.booking-form > div.bf-grid > div.bf-field > input form.booking-form > div.bf-grid > div.bf-field > input

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Vehicle Type Swift Dzire Ertiga Innova Crysta Tempo Traveller Force Urbania form.booking-form > div.bf-grid > div.bf-field > select
Trip Type Local One Way Round Trip Airport Railway Station Sightseeing Outstati… form.booking-form > div.bf-grid > div.bf-field > select
Vehicle Type Swift Dzire Ertiga Innova Crysta Tempo Traveller Force Urbania form.booking-form > div.bf-grid > div.bf-field > select
Trip Type Local One Way Round Trip Airport Railway Station Sightseeing Outstati… form.booking-form > div.bf-grid > div.bf-field > select

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
Go to review 2 section.section > div.container > div.slider-dots > button.slider-dot
Go to review 3 section.section > div.container > div.slider-dots > button.slider-dot
Go to review 4 section.section > div.container > div.slider-dots > button.slider-dot
Go to review 5 section.section > div.container > div.slider-dots > button.slider-dot
Go to review 6 section.section > div.container > div.slider-dots > button.slider-dot

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>`
●`[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
●Document has a main landmark.
●Identical links have the same purpose.
○`[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
○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.
○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
○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.
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
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Detected JavaScript libraries
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