0% found this document useful (0 votes)
71 views6 pages

Amrut Performance Report

The document summarizes the results of an audit of the website amrut.co using Google's Lighthouse tool. The audit found issues with performance, accessibility, best practices, SEO and PWA compliance. Key metrics like first contentful paint and largest contentful paint were over 2 seconds. Opportunities to improve loading, such as deferring offscreen images, were identified.

Uploaded by

Govind Prajapati
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
71 views6 pages

Amrut Performance Report

The document summarizes the results of an audit of the website amrut.co using Google's Lighthouse tool. The audit found issues with performance, accessibility, best practices, SEO and PWA compliance. Key metrics like first contentful paint and largest contentful paint were over 2 seconds. Opportunities to improve loading, such as deferring offscreen images, were identified.

Uploaded by

Govind Prajapati
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

https://amrut.

co/

25 77 69 90

Performance Accessibility Best SEO PWA


Practices

There were issues affecting this run of Lighthouse:

Chrome extensions negatively affected this page's load performance. Try auditing the page in incognito
mode or from a Chrome profile without extensions.

25

Performance
Values are estimated and may vary. The performance score is
calculated directly from these metrics. See calculator.

0–49 50–89 90–100

METRICS Expand view

First Contentful Paint Time to Interactive

2.1 s 136.4 s

Speed Index Total Blocking Time

49.1 s 2,490 ms

Largest Contentful Paint Cumulative Layout Shift

8.8 s 0.038

View Original Trace View Treemap


Show audits relevant to: All FCP TBT LCP CLS

OPPORTUNITIES

Opportunity Estimated Savings

Defer offscreen images 219.0


9 s

Serve images in next-gen formats 172.7


2 s

Efficiently encode images 84.62 


s

Properly size images 79.56 


s

Use HTTP/2 37.46 


s

Reduce unused JavaScript 1.33 s

Reduce unused CSS 0.73 s

Eliminate render-blocking resources 0.65 s

These suggestions can help your page load faster. They don't directly affect the Performance score.

DIAGNOSTICS

Avoid enormous network payloads — Total size was 47,011 KiB

Serve static assets with an efficient cache policy — 335 resources found

Minimize main-thread work — 18.1 s

Ensure text remains visible during webfont load

Reduce the impact of third-party code — Third-party code blocked the main thread for 380 ms

Does not use passive listeners to improve scrolling performance

Image elements do not have explicit width and height

Avoid an excessive DOM size — 3,562 elements


Reduce JavaScript execution time — 6.9 s

Avoid chaining critical requests — 11 chains found

Keep request counts low and transfer sizes small — 390 requests • 47,011 KiB

Largest Contentful Paint element — 1 element found

Avoid large layout shifts — 1 element found

Avoid long main-thread tasks — 20 long tasks found

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

PASSED AUDITS (17) Show

77

Accessibility
These checks highlight opportunities to improve the accessibility of your web
app. Only a subset of accessibility issues can be automatically detected so
manual testing is also encouraged.

ARIA

[role]s do not have all required [aria-*] attributes

ARIA IDs are not unique

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive
technology, like a screen reader.

BEST PRACTICES

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

These items highlight common accessibility best practices.

CONTRAST

Background and foreground colors do not have a sufficient contrast ratio.


These are opportunities to improve the legibility of your content.

NAMES AND LABELS

Links do not have a discernible name

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.

NAVIGATION

Heading elements are not in a sequentially-descending order

These are opportunities to improve keyboard navigation in your application.

ADDITIONAL ITEMS TO MANUALLY CHECK (10) Show

These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility
review.

PASSED AUDITS (19) Show

NOT APPLICABLE (19) Show

69

Best Practices

TRUST AND SAFETY

Includes front-end JavaScript libraries with known security vulnerabilities — 9 vulnerabilities detected

Ensure CSP is effective against XSS attacks

USER EXPERIENCE

Displays images with incorrect aspect ratio


GENERAL

Browser errors were logged to the console

Issues were logged in the Issues panel in Chrome Devtools

Detected JavaScript libraries

PASSED AUDITS (10) Show

NOT APPLICABLE (1) Show

90

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.

CRAWLING AND INDEXING

Links are not crawlable

To appear in search results, crawlers need access to your app.

MOBILE FRIENDLY

Tap targets are not sized appropriately — 73% appropriately sized tap targets

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.

ADDITIONAL ITEMS TO MANUALLY CHECK (1) Show

Run these additional validators on your site to check additional SEO best practices.

PASSED AUDITS (11) Show


NOT APPLICABLE (1) Show

PWA
These checks validate the aspects of a Progressive Web App. Learn more.

INSTALLABLE

Web app manifest or service worker do not meet the installability requirements — 1 reason

PWA OPTIMIZED

Does not register a service worker that controls page and start_url

Is not configured for a custom splash screen Failures: No manifest was fetched.

Does not set a theme color for the address bar.


Failures: No manifest was fetched,
No `<meta name="theme-color">` tag found.

Content is sized correctly for the viewport

Has a <meta name="viewport"> tag with width or initial-scale

Does not provide a valid apple-touch-icon

Manifest doesn't have a maskable icon No manifest was fetched

ADDITIONAL ITEMS TO MANUALLY CHECK (3) Show

These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your
score but it's important that you verify them manually.

Captured at Feb 24, 2022, 2:07 Emulated Moto G4 with Single page load
PM GMT+5:30 Lighthouse 9.1.0
Initial page load Slow 4G throttling Using Chromium 98.0.4758.102
with devtools

Generated by Lighthouse 9.1.0 | File an issue

You might also like