https://esignature.com.np/website-design-development-nepal

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
esignature.com.np/frontend-asset/images/main-bg.png	14400.0 s	52.0 KiB
esignature.com.np/media/2025/02/13/website-design-and-d-1739426498.jpeg	14400.0 s	44.1 KiB
esignature.com.np/frontend-asset/css/main.css	14400.0 s	35.3 KiB
esignature.com.np/images/services/17272439201727243920.png	14400.0 s	34.8 KiB
esignature.com.np/frontend-asset/images/menu-bg.webp	14400.0 s	32.5 KiB
kit.fontawesome.com/91ae640590.js	60.0 s	6.0 KiB
esignature.com.np/frontend-asset/images/icons/LOGO-eig.png	14400.0 s	7.0 KiB
esignature.com.np/frontend-asset/images/icons/brand.png	14400.0 s	7.0 KiB
esignature.com.np/frontend-asset/images/profile_image_bg.jpg	14400.0 s	6.2 KiB
esignature.com.np/frontend-asset/js/aos.js	14400.0 s	4.8 KiB
esignature.com.np/frontend-asset/images/whatsapp.png	14400.0 s	4.2 KiB
esignature.com.np/admin-asset/plugins/alertify/alertify.min.css	14400.0 s	4.2 KiB
esignature.com.np/frontend-asset/images/service/book.webp	14400.0 s	3.1 KiB
esignature.com.np/frontend-asset/css/aos.css	14400.0 s	2.1 KiB
esignature.com.np/frontend-asset/js/app.js	14400.0 s	1.9 KiB
esignature.com.np/frontend-asset/js/custom.js	14400.0 s	1.8 KiB
esignature.com.np/frontend-asset/images/icons/enter-arrow.png	14400.0 s	1009 B
esignature.com.np/frontend-asset/images/double-quote.svg	14400.0 s	899 B
esignature.com.np/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js	172749.0 s	1.0 KiB
www.gstatic.com/recaptcha/api2/logo_48.png	604800.0 s	2.2 KiB

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.

URL	Est Savings
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff2	55 ms
ka-f.fontawesome.com/releases/v5.15.4/webfonts/free-fa-solid-900.woff2	40 ms
ka-f.fontawesome.com/releases/v5.15.4/webfonts/free-fa-regular-400.woff2	30 ms
use.fontawesome.com/releases/v5.0.6/webfonts/fa-solid-900.woff2	25 ms
use.fontawesome.com/releases/v5.0.6/webfonts/fa-regular-400.woff2	25 ms

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: about us

path: 1,HTML,1,BODY,8,HEADER,1,DIV,0,DIV,3,DIV,0,DIV,0,IMG

selector: div.row > div.col-lg-5 > div.img-wrapper > img.img-fluid

snippet: <img width="100%" height="100%" src="/images/services/17272439201727243920.png" alt="about us" class="img-fluid about-img">

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.

URL	Transfer Size	Duration
/css2?family=Poppins:ital,wght@0,100;0,200;0,300;0,400;0,...	1.4 KiB	287 ms
use.fontawesome.com/releases/v5.0.6/css/all.css	8.3 KiB	257 ms
cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.3.1/css/bootstrap.min.css	17.5 KiB	321 ms
stackpath.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css	7.4 KiB	262 ms
esignature.com.np/frontend-asset/css/aos.css	2.1 KiB	185 ms
esignature.com.np/frontend-asset/css/main.css	35.3 KiB	245 ms
esignature.com.np/admin-asset/plugins/alertify/alertify.min.css	4.2 KiB	185 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.

	URL	Resource Size	Est Savings
about us `div.row > div.col-lg-5 > div.img-wrapper > img.img-fluid`	esignature.com.np/images/services/17272439201727243920.png	34.3 KiB	7.5 KiB
about us `div.row > div.col-lg-5 > div.content-wrapper > img.list-img`	esignature.com.np/media/2025/02/13/website-design-and-d-1739426498.jpeg	43.6 KiB	7.1 KiB
E Signature `nav#navbar > div.container > a.e-nav-brand > img.e-nav-brand__img`	esignature.com.np/frontend-asset/images/icons/LOGO-eig.png	6.5 KiB	5.1 KiB

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

Diagnostics

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: 30 ms 7.8 KiB

URL	Transfer Size	Est Savings
esignature.com.np/frontend-asset/css/main.css	35.3 KiB	7.8 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: 30 ms 57.2 KiB

URL	Transfer Size	Est Savings
esignature.com.np/frontend-asset/css/main.css	34.8 KiB	29.5 KiB
cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.3.1/css/bootstrap.min.css	16.8 KiB	15.7 KiB
/! Font Awesome Free 5.15.4 by @fontawesome - https://fontawesome.com * License - https://font…	12.0 KiB	12.0 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: 0.0 ms 584.8 KiB

URL	Transfer Size	Est Savings
www.gstatic.com/recaptcha/releases/bSuJ2xBC8cFy7pM4Z3Hu9boH/recaptcha__en.js	348.1 KiB	177.7 KiB
www.googletagmanager.com/gtag/js?id=G-WZD0HVMYD3&cx=c&gtm=4e6b21	176.9 KiB	123.7 KiB
www.googletagmanager.com/gtag/js?id=G-1ZVX604DV6&cx=c&gtm=4e6b21	194.2 KiB	79.3 KiB
www.googletagmanager.com/gtag/js?id=G-WZD0HVMYD3	177.0 KiB	74.9 KiB
www.googletagmanager.com/gtm.js?id=GTM-W4H6CLSN	120.7 KiB	65.1 KiB
www.googletagmanager.com/gtag/destination?id=AW-16641349306&cx=c&gtm=4e6b21	165.2 KiB	64.2 KiB

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

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify JavaScript

●Avoids enormous network payloads Total size was 2,242 KiB

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.8 s

●Avoid long main-thread tasks 2 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 70 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 250 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

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.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
We start by trying to understand your objectives, business requirements, and ex… `article.list-section__article > div.details > div.service-list > li`
Our expert web designers and developers suggest you the best choice of tech sel… `article.list-section__article > div.details > div.service-list > li`
The next step is to sign an NDA (Non-disclosure Agreement) to secure your web d… `article.list-section__article > div.details > div.service-list > li`
Finally, we design a sitemap and wireframe of the website which gives a basic i… `article.list-section__article > div.details > div.service-list > li`
We conduct a comprehensive custom website development workshop to analyze all c… `article.list-section__article > div.details > div.service-list > li`
From there, our experienced UI/UX team will create website pages based on the p… `article.list-section__article > div.details > div.service-list > li`
You will get involved and updated continuously throughout the process. Based on… `article.list-section__article > div.details > div.service-list > li`
The website starts to take shape as we begin the actual website design and deve… `article.list-section__article > div.details > div.service-list > li`
The world project will be divided into numerous sprints. `article.list-section__article > div.details > div.service-list > li`
Our website design, and development team with QAs and Scrum masters work in eac… `article.list-section__article > div.details > div.service-list > li`
We start by designing the home page and then gradually the rest of the web page… `article.list-section__article > div.details > div.service-list > li`
The QA team tests the website from start to finish until the website is issue-f… `article.list-section__article > div.details > div.service-list > li`
You'll get a regular CMS and plugin update. `article.list-section__article > div.details > div.service-list > li`
We provide ongoing web server maintenance and repair services. `article.list-section__article > div.details > div.service-list > li`
We will help you build a customer service strategy and refine your website serv… `article.list-section__article > div.details > div.service-list > li`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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-*]` 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

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

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

●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

●Background and foreground colors have a sufficient contrast ratio

●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 are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

○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

●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

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`