Skip to content
https://mbmis.in

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.

87

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.

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
Logo div.login-photo-row > div.login-photo-slot > div.login-photo-circle > img
mbmis.in/media/login/logo.png326.6 KiB325.4 KiB

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: Logo
path: 1,HTML,1,BODY,0,DIV,0,DIV,1,DIV,0,DIV,0,IMG
selector: div.login-photo-row > div.login-photo-slot > div.login-photo-circle > img
snippet: <img src="/media/login/logo.png" alt="Logo">

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

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

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: 0.0 ms 44.3 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

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

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: 648 ms
●Time to Interactive 2.1 s
●Layout shift culprits
●Optimize DOM size
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 536 KiB
●JavaScript execution time 0.0 s
●Minimizes main-thread work 0.1 s
●Avoid non-composited animations 1 animated element found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 160 ms
●Server Backend Latencies 0 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 160 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○User Timing marks and measures
○Avoid long main-thread tasks
97

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.

Best practices

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-hidden="true"]` is not present on the document `<body>`
●Buttons have an accessible name
●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.
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` 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 use only permitted ARIA attributes
○`[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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○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
○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
○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

●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
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
○Ensure proper origin isolation with COOP
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
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

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 #ContentError
1<!DOCTYPE html>Syntax not understood
2<html lang="en">Syntax not understood
3<head>Syntax not understood
5 <meta charset="UTF-8">Syntax not understood
6 <meta name="viewport" content="width=device-width, initial-scale=1.0">Syntax not understood
7 <meta name="description" content="Mission Bhagiratha MIS Portal - Rural Drinking Water Supply Monitoring">Syntax not understood
8 <title>Login | Mission Bhagiratha MIS Portal</title>Syntax not understood
9 <link rel="preconnect" href="https://cdn.jsdelivr.net" crossorigin>Unknown directive
10 <link href="https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/css/bootstrap.min.css" rel="stylesheet">Unknown directive
11 <link href="https://cdn.jsdelivr.net/npm/bootstrap-icons@1.11.3/font/bootstrap-icons.min.css" rel="stylesheet">Unknown directive
12 <link href="/static/css/main.f6ddba205904.css" rel="stylesheet">Syntax not understood
14<style>Syntax not understood
15.login-photo-row {Syntax not understood
16 display: flex;Unknown directive
17 justify-content: center;Unknown directive
18 gap: 1.5rem;Unknown directive
19 margin-bottom: 1.5rem;Unknown directive
20 flex-wrap: wrap;Unknown directive
21}Syntax not understood
22.login-photo-slot {Syntax not understood
23 text-align: center;Unknown directive
24}Syntax not understood
25.login-photo-circle {Syntax not understood
26 width: 92px;Unknown directive
27 height: 92px;Unknown directive
28 border-radius: 50%;Unknown directive
29 border: 3px solid #fff;Unknown directive
30 background: transparent;Unknown directive
31 overflow: hidden;Unknown directive
32 display: flex;Unknown directive
33 align-items: center;Unknown directive
34 justify-content: center;Unknown directive
35 box-shadow: 0 0 0 1px rgba(255,255,255,0.25);Unknown directive
36}Syntax not understood
37.login-photo-circle img {Syntax not understood
38 width: 100%;Unknown directive
39 height: 100%;Unknown directive
40 object-fit: cover;Unknown directive
41}Syntax not understood
42.login-photo-slot span {Syntax not understood
43 display: block;Unknown directive
44 margin-top: 0.4rem;Unknown directive
45 color: rgba(255,255,255,0.9);Unknown directive
46 font-size: 0.75rem;Unknown directive
47}Syntax not understood
48</style>Syntax not understood
50</head>Syntax not understood
51<body class="auth-page">Syntax not understood
53<div class="auth-wrapper">Syntax not understood
54 <div class="login-photo-row">Syntax not understood
56 <div class="login-photo-slot">Syntax not understood
57 <div class="login-photo-circle">Syntax not understood
59 </div>Syntax not understood
60 <span>Chief Minister</span>Syntax not understood
61 </div>Syntax not understood
63 <div class="login-photo-slot">Syntax not understood
64 <div class="login-photo-circle">Syntax not understood
66 <img src="/media/login/logo.png" alt="Logo">Syntax not understood
68 </div>Syntax not understood
69 <span>Logo</span>Syntax not understood
70 </div>Syntax not understood
72 <div class="login-photo-slot">Syntax not understood
73 <div class="login-photo-circle">Syntax not understood
75 </div>Syntax not understood
76 <span>Department Minister</span>Syntax not understood
77 </div>Syntax not understood
79 </div>Syntax not understood
80 <div class="auth-card">Syntax not understood
81 <div class="auth-header text-center mb-4">Syntax not understood
82 <div class="auth-logo mb-3">Syntax not understood
83 <i class="bi bi-droplet-fill"></i>Syntax not understood
84 </div>Syntax not understood
85 <h1 class="h4 fw-bold text-primary mb-1">MB MIS</h1>Syntax not understood
86 <p class="text-muted small mb-0">Mission Bhagiratha MIS Portal</p>Syntax not understood
87 </div>Syntax not understood
91 <form method="post" novalidate>Syntax not understood
92 <input type="hidden" name="csrfmiddlewaretoken" value="cIldSjYQMl1r8gRqVgo4M8Zr0jNn47T030lrRCYX479cRyMUOuV3JlACOwVbX5Ne">Syntax not understood
93 <div class="mb-3">Syntax not understood
94 <label for="id_username" class="form-label fw-semibold">Syntax not understood
95 <i class="bi bi-person-badge me-1"></i> Employee IDSyntax not understood
96 </label>Syntax not understood
97 <input type="text" name="username" class="form-control form-control-lg" placeholder="Enter Employee ID" autocomplete="username" autofocus maxlength="20" required id="id_username">Syntax not understood
99 </div>Syntax not understood
100 <div class="mb-3">Syntax not understood
101 <label for="id_password" class="form-label fw-semibold">Syntax not understood
102 <i class="bi bi-lock me-1"></i> PasswordSyntax not understood
103 </label>Syntax not understood
104 <input type="password" name="password" class="form-control form-control-lg" placeholder="Enter Password" autocomplete="current-password" required id="id_password">Syntax not understood
106 </div>Syntax not understood
107 <div class="mb-3">Syntax not understood
108 <label for="id_captcha" class="form-label fw-semibold">Syntax not understood
109 What is 3 + 7?Syntax not understood
110 </label>Syntax not understood
111 <input type="text" name="captcha" class="form-control form-control-lg" inputmode="numeric" autocomplete="off" maxlength="3" required id="id_captcha">Syntax not understood
113 </div>Syntax not understood
115 <button type="submit" class="btn btn-primary btn-lg w-100 mt-2">Syntax not understood
116 <i class="bi bi-box-arrow-in-right me-1"></i> Sign InSyntax not understood
117 </button>Syntax not understood
118 </form>Syntax not understood
120 <div class="text-center mt-4">Syntax not understood
121 <a href="/accounts/password-reset/" class="text-decoration-none small">Syntax not understood
122 <i class="bi bi-question-circle me-1"></i> Forgot Password?Syntax not understood
123 </a>Syntax not understood
124 </div>Syntax not understood
125 </div>Syntax not understood
126 <p class="text-center text-white-50 small mt-3 mb-0">Syntax not understood
127 Government of Telangana &mdash; Mission BhagirathaSyntax not understood
128 </p>Syntax not understood
129</div>Syntax not understood
132 <script src="https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/js/bootstrap.bundle.min.js"></script>Unknown directive
133 <script src="/static/js/main.3355e6e2403d.js"></script>Syntax not understood
135</body>Syntax not understood
136</html>Syntax not understood

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`

Send Feedback