Website performance of https://amarvyas.in

Generated on January 25, 2021 at 6:22 AM

https://amarvyas.in/
94
Performance
78
Accessibility
93
Best Practices
93
SEO
Progressive Web App
94
Performance
78
Accessibility
93
Best Practices
93
SEO
Progressive Web App
94
Performance
Values are estimated and may vary. The performance score is calculated directly from these metrics.See calculator.
0–49 50–89 90–100
Final Screenshot
Metrics
First Contentful Paint
1.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Speed Index
3.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Largest Contentful Paint
1.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn More
Time to Interactive
2.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Cumulative Layout Shift
1.025
Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more.
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Screenshot
Opportunities
Opportunity
Estimated Savings
Reduce initial server response time
1.27 s
Keep the server response time for the main document short because all other requests depend on it. Learn more.
URL
Time Spent
https://amarvyas.in
1,370 ms
These suggestions can help your page load faster. They don't directly affect the Performance score.
Diagnostics
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
URL
Potential Savings
…font/fontello2.woff
(s3.amazonaws.com)
660 ms
Serve static assets with an efficient cache policy 5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
WordPressRead about Browser Caching in WordPress.
URL
Cache TTL
Transfer Size
…font/fontello2.woff
(s3.amazonaws.com)
1 h 40 m
8 KiB
/analytics.js
(www.google-analytics.com)
2 h
19 KiB
/playht-pageplayer-plugin-v12.js
(static.play.ht)
4 h
29 KiB
/playht-pageplayer-plugin-v10.css
(static.play.ht)
4 h
4 KiB
…cloudflare-static/rocket-loader.min.js
(ajax.cloudflare.com)
2 d
5 KiB
Avoid chaining critical requests 4 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Maximum critical path latency: 3,900 ms
Initial Navigation
https://amarvyas.in
…css/autoptimize_2824fa4….css
(amarvyas.in)
- 1,380 ms, 22.67 KiB
/playht-pageplayer-plugin-v10.css
(static.play.ht)
/css?family=Montserrat:600&display=swap
(fonts.googleapis.com)
- 120 ms, 0.98 KiB
…font/fontello2.woff
(s3.amazonaws.com)
- 660 ms, 7.84 KiB
…themeisle-gutenberg/post-11562-161….css
(amarvyas.in)
- 10 ms, 0.39 KiB
Keep request counts low and transfer sizes small 16 requests • 281 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Resource Type
Requests
Transfer Size
Total
16
281.1 KiB
Script
7
145.2 KiB
Image
2
89.4 KiB
Stylesheet
4
27.6 KiB
Document
1
10.9 KiB
Font
1
7.8 KiB
Other
1
0.1 KiB
Media
0
0.0 KiB
Third-party
9
104.7 KiB
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport. Learn More
Element
AMAR'S POSTS
<h1 class="main-title" itemprop="headline">
Avoid large layout shifts 2 elements found
These DOM elements contribute most to the CLS of the page.
Element
CLS Contribution
Search for: CATEGORIES Cloud Storage Content Management Systems daily blogging …
<div id="right-sidebar" class="widget-area sidebar is-right-sidebar" itemtype="https://schema.org/WPSideBar" itemscope="">
0.863
Post navigation Page 1 Page 2 … Page 13 Next →
<nav id="nav-below" class="paging-navigation masonry-brick" style="opacity: 1;">
0.163
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
URL
Start Time
Duration
/playht-pageplayer-plugin-v12.js
(static.play.ht)
1,975 ms
52 ms
More information about the performance of your application. These numbers don't directly affect the Performance score.
Passed audits (28)
Show Hide
Eliminate render-blocking resources
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
WordPressThere are a number of WordPress plugins that can help you inline critical assets or defer less important resources. Beware that optimizations provided by these plugins may break features of your theme or plugins, so you will likely need to make code changes.
Properly size images Potential savings of 13 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
WordPressUpload images directly through the media library to ensure that the required image sizes are available, and then insert them from the media library or use the image widget to ensure the optimal image sizes are used (including those for the responsive breakpoints). Avoid using `Full Size` images unless the dimensions are adequate for their usage. Learn More.
URL
Resource Size
Potential Savings
…01/Girl-writ….webp
(amarvyas.in)
88.5 KiB
13.2 KiB
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
WordPressInstall a lazy-load WordPress plugin that provides the ability to defer any offscreen images, or switch to a theme that provides that functionality. Also consider using the AMP plugin.
Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.
WordPressA number of WordPress plugins can speed up your site by concatenating, minifying, and compressing your styles. You may also want to use a build process to do this minification up-front if possible.
Minify JavaScript
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
WordPressA number of WordPress plugins can speed up your site by concatenating, minifying, and compressing your scripts. You may also want to use a build process to do this minification up front if possible.
Remove unused CSS Potential savings of 21 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
WordPressConsider reducing, or switching, the number of WordPress plugins loading unused CSS in your page. To identify plugins that are adding extraneous CSS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the stylesheet. Look out for plugins that have many stylesheets in the list which have a lot of red in code coverage. A plugin should only enqueue a stylesheet if it is actually used on the page.
URL
Transfer Size
Potential Savings
…css/autoptimize_2824fa4….css
(amarvyas.in)
22.7 KiB
21.2 KiB
Remove unused JavaScript Potential savings of 49 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
WordPressConsider reducing, or switching, the number of WordPress plugins loading unused JavaScript in your page. To identify plugins that are adding extraneous JS, try running code coverage in Chrome DevTools. You can identify the theme/plugin responsible from the URL of the script. Look out for plugins that have many scripts in the list which have a lot of red in code coverage. A plugin should only enqueue a script if it is actually used on the page.
URL
Transfer Size
Potential Savings
/gtag/js?id=UA-111…-10
(www.googletagmanager.com)
39.2 KiB
26.6 KiB
/playht-pageplayer-plugin-v12.js
(static.play.ht)
29.5 KiB
22.1 KiB
Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.
WordPressConsider using an image optimization WordPress plugin that compresses your images while retaining quality.
Serve images in next-gen formats
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
WordPressConsider using a plugin or service that will automatically convert your uploaded images to the optimal formats.
Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
WordPressYou can enable text compression in your web server configuration.
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.
Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.
Preload key requests
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Use HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers, multiplexing, and server push. Learn more.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more
WordPressConsider uploading your GIF to a service which will make it available to embed as an HTML5 video.
Remove duplicate modules in JavaScript bundles
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn More
URL
Potential Savings
/playht-pageplayer-plugin-v12.js
(static.play.ht)
0.1 KiB
/playht-pageplayer-plugin-v12.js:1:14155
(static.play.ht)
@babel/plugin-transform-classes
Preload Largest Contentful Paint image
Preload the image used by the LCP element in order to improve your LCP time. Learn more.
Avoids enormous network payloads Total size was 281 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
WordPressConsider showing excerpts in your post lists (e.g. via the more tag), reducing the number of posts shown on a given page, breaking your long posts into multiple pages, or using a plugin to lazy-load comments.
URL
Transfer Size
…01/Girl-writ….webp
(amarvyas.in)
89.2 KiB
/gtag/js?id=UA-111…-10
(www.googletagmanager.com)
39.2 KiB
…jquery/jquery.min.js
(amarvyas.in)
29.8 KiB
/playht-pageplayer-plugin-v12.js
(static.play.ht)
29.5 KiB
…css/autoptimize_2824fa4….css
(amarvyas.in)
22.7 KiB
…js/autoptimize_c0039bd….js
(amarvyas.in)
19.3 KiB
/analytics.js
(www.google-analytics.com)
18.8 KiB
https://amarvyas.in
10.9 KiB
…font/fontello2.woff
(s3.amazonaws.com)
7.8 KiB
…cloudflare-static/rocket-loader.min.js
(ajax.cloudflare.com)
4.5 KiB
Avoids an excessive DOM size 553 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Statistic
Element
Value
Total DOM Elements
553
Maximum DOM Depth
path
<path d="M0 112c0-26.51 21.49-48 48-48h110.014a48 48 0 0 1 43.592 27.907l12.349 26.…" fill-rule="nonzero">
13
Maximum Child Elements
body
<body class="home blog wp-embed-responsive post-image-below-header post-image-aligned-c…" itemtype="https://schema.org/Blog" itemscope="">
20
User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
JavaScript execution time 0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
URL
Total CPU Time
Script Evaluation
Script Parse
https://amarvyas.in
301 ms
57 ms
1 ms
…js/autoptimize_c0039bd….js
(amarvyas.in)
96 ms
70 ms
1 ms
/playht-pageplayer-plugin-v12.js
(static.play.ht)
52 ms
44 ms
2 ms
Minimizes main-thread work 0.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Category
Time Spent
Script Evaluation
262 ms
Style & Layout
173 ms
Other
85 ms
Rendering
62 ms
Parse HTML & CSS
27 ms
Script Parsing & Compilation
20 ms
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Third-Party
Transfer Size
Main-Thread Blocking Time
Google Tag Manager
39 KiB
0 ms
/gtag/js?id=UA-111…-10
(www.googletagmanager.com)
39 KiB
0 ms
Google Analytics
19 KiB
0 ms
/analytics.js
(www.google-analytics.com)
19 KiB
0 ms
Amazon Web Services
8 KiB
0 ms
…font/fontello2.woff
(s3.amazonaws.com)
8 KiB
0 ms
Cloudflare
5 KiB
0 ms
…cloudflare-static/rocket-loader.min.js
(ajax.cloudflare.com)
5 KiB
0 ms
Google Fonts
1 KiB
0 ms
Uses passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Avoids document.write()
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn more
Image elements have explicit width and height
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn more
78
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.
Names and labels
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Failing Elements
img
<img src="data:image/svg+xml,%3Csvg%20xmlns=%22http://www.w3.org/2000/svg%22%20viewB…" data-src="https://amarvyas.in/wp-content/uploads/2021/01/Keyboard-India-Flag-AVyas-7…" class="lazyload attachment-medium_large size-medium_large wp-post-image sp-no-webp" itemprop="image" height="512" width="768" data-srcset="https://amarvyas.in/wp-content/uploads/2021/01/Keyboard-India-Flag-AVyas-7…" data-sizes="(max-width: 768px) 100vw, 768px">
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
Failing Elements
input
<input class="playht-custom-audio-range__input playht-custom-audio-range__input--mobile" type="range" name="speed" min="0.5" max="2.5" step="0.1" value="1">
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
Failing Elements
a
<a href="https://amarvyas.in/a-tale-of-two-domains/">
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.
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Failing Elements
00:00
<span class="playht-custom-audio__played-time">
00:00
<span class="playht-custom-audio__total-time">
by Play.ht
<a class="playht-custom-audio__brand-link" href="https://play.ht/" target="_blank">
Play.ht
<span>
.ht
<b>
00:00
<span class="playht-custom-audio__played-time playht-custom-audio__played-time--mobile">
00:00
<span class="playht-custom-audio__total-time playht-custom-audio__total-time--mobile">
by play.ht
<a class="playht-custom-audio__brand-link playht-custom-audio__brand-link--mobile" href="https://play.ht/" target="_blank">
play.ht
<span>
.ht
<b>
These are opportunities to improve the legibility of your content.
Additional items to manually check (10)
Show Hide
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn more.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn more.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn more.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more.
These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
Passed audits (15)
Show Hide
[aria-*] attributes match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
[aria-hidden="true"] is not present on the document <body>
Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`. Learn more.
[aria-*] attributes have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
[aria-*] attributes are valid and not misspelled
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.
[aria-hidden="true"] elements do not contain focusable descendents
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn more.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
<html> element has a [lang] attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
<html> element has a valid value for its [lang] attribute
Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.
List items (<li>) are contained within <ul> or <ol> parent elements
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
Heading elements appear in a sequentially-descending order
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.
Not applicable (22)
Show Hide
[accesskey] values are unique
Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.
ARIA input fields have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
[role]s have all required [aria-*] attributes
Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
[role]s are contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.
[role] values are valid
ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
Definition list items are wrapped in <dl> elements
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.
[id] attributes on active, focusable elements are unique
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn more.
<frame> or <iframe> elements have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
<input type="image"> elements have [alt] text
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn more.
Presentational <table> elements avoid using <th>, <caption> or the [summary] attribute.
A table being used for layout purposes should not include data elements, such as the th or caption elements or the summary attribute, because this can create a confusing experience for screen reader users. Learn more.
The document does not use <meta http-equiv="refresh">
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more.
<object> elements have [alt] text
Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey meaning to users. Learn more.
No element has a [tabindex] value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.
[lang] attributes have a valid value
Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.
<video> elements contain a <track> element with [kind="captions"]
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
<video> elements contain a <track> element with [kind="description"]
Audio descriptions provide relevant information for videos that dialogue cannot, such as facial expressions and scenes. Learn more.
93
Best Practices
Trust and Safety
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Failing Anchors
by Play.ht
<a class="playht-custom-audio__brand-link" href="https://play.ht/" target="_blank">
by play.ht
<a class="playht-custom-audio__brand-link playht-custom-audio__brand-link--mobile" href="https://play.ht/" target="_blank">
Passed audits (16)
Show Hide
Uses HTTPS
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more.
Avoids front-end JavaScript libraries with known security vulnerabilities
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Allows users to paste into password fields
Preventing password pasting undermines good security policy. Learn more.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Serves images with appropriate resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.
Properly defines charset
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more.
Avoids unload event listeners
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn More
Avoids Application Cache
Application Cache is deprecated. Learn more.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more.
No browser errors logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
No issues in the Issues panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
Name
Version
jQuery
3.5.1
WordPress
Page has valid source maps
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.
Not applicable (1)
Show Hide
Fonts with font-display: optional are preloaded
Preload `optional` fonts so first-time visitors may use them. Learn More
93
SEO
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking. Learn more.
Content Best Practices
Image elements do not have [alt] attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Failing Elements
img
<img src="data:image/svg+xml,%3Csvg%20xmlns=%22http://www.w3.org/2000/svg%22%20viewB…" data-src="https://amarvyas.in/wp-content/uploads/2021/01/Keyboard-India-Flag-AVyas-7…" class="lazyload attachment-medium_large size-medium_large wp-post-image sp-no-webp" itemprop="image" height="512" width="768" data-srcset="https://amarvyas.in/wp-content/uploads/2021/01/Keyboard-India-Flag-AVyas-7…" data-sizes="(max-width: 768px) 100vw, 768px">
Format your HTML in a way that enables crawlers to better understand your app’s content.
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.
Run these additional validators on your site to check additional SEO best practices.
Passed audits (13)
Show Hide
Has a <meta name="viewport"> tag with width or initial-scale
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more.
Document has a <title> element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
Document has a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn more.
Links are crawlable
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 More
Page isn’t blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.
robots.txt is valid
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.
Document has a valid hreflang
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more.
Document has a valid rel=canonical
Canonical links suggest which URL to show in search results. Learn more.
Document uses legible font sizes 100% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more.
Source
Selector
% of Page Text
Font Size
Legible text
100.00%
≥ 12px
 
 
  
   Document avoids plugins   
     
 
  
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
 
 
 
 
  
   Tap targets are sized appropriately 100% appropriately sized tap targets  
     
 
  
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
 
 
 
 
 
                                  
Progressive Web App
 
 
These checks validate the aspects of a Progressive Web App. Learn more.
 
Fast and reliable
 
  
   Page load is fast enough on mobile networks   
     
 
  
A fast page load over a cellular network ensures a good mobile user experience. Learn more.
 
 
 
 
  
   Current page does not respond with a 200 when offline   
     
 
  
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
 
 
 
 
  
   start_url does not respond with a 200 when offline
No usable web app manifest found on page.
   
     
 
  
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more.
 
 
 
Installable
 
  
   Uses HTTPS   
     
 
  
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
 
 
 
 
  
   Does not register a service worker that controls page and start_url   
     
 
  
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
 
 
 
 
  
   Web app manifest does not meet the installability requirements
Failures: No manifest was fetched.
   
     
 
  
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
 
 
 
PWA Optimized
 
  
   Redirects HTTP traffic to HTTPS   
     
 
  
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
 
 
 
 
  
   Is not configured for a custom splash screen
Failures: No manifest was fetched.
   
     
 
  
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more.
 
 
 
 
  
   Does not set a theme color for the address bar.
Failures: No manifest was fetched,
No `<meta name="theme-color">` tag found.
   
     
 
  
The browser address bar can be themed to match your site. Learn more.
 
 
 
 
  
   Content is sized correctly for the viewport   
     
 
  
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more.
 
 
 
 
  
   Has a <meta name="viewport"> tag with width or initial-scale   
     
 
  
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more.
 
 
 
 
  
   Contains some content when JavaScript is not available   
     
 
  
Your app should display some content when JavaScript is disabled, even if it's just a warning to the user that JavaScript is required to use the app. Learn more.
 
 
 
 
  
   Provides a valid apple-touch-icon   
     
 
  
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
 
 
 
 
  
   Manifest doesn't have a maskable icon
No manifest was fetched
   
     
 
  
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more.
 
 
 
  
  
 
 Additional items to manually check (3)   
 
 Show Hide 
 
  
 
  
   Site works cross-browser   
     
 
  
To reach the most number of users, sites should work across every major browser. Learn more.
 
 
 
 
  
   Page transitions don't feel like they block on the network   
     
 
  
Transitions should feel snappy as you tap around, even on a slow network. This experience is key to a user's perception of performance. Learn more.
 
 
 
 
  
   Each page has a URL   
     
 
  
Ensure individual pages are deep linkable via URL and that URLs are unique for the purpose of shareability on social media. Learn more.
 
 
 
 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 Jan 25, 2021, 6:22 AM UTC
  • Emulated Moto G4 with Lighthouse 6.5.0
    CPU/Memory Power: 1020
CPU throttling: 1x slowdown (Simulated)
Axe version: 3.5.5
  • Single page load
    This data is taken from a single page load, as opposed to field data summarizing many sessions.
  • Initial page load
  • Custom throttling
    Network throttling: 0 ms TCP RTT, 5,000 Kbps throughput (Simulated)
  • Using HeadlessChromium 87.0.4280.88 with cli
    User agent (network): "Mozilla/5.0 (Linux; Android 7.0; Moto G (4)) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4143.7 Mobile Safari/537.36 Chrome-Lighthouse"
 
  Generated by Lighthouse 6.5.0 | File an issue