Access lifelinehospitals.co.in.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

38/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value480 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

lifelinehospitals.co.in

565 ms

lifelinehospitals.co.in

881 ms

bootstrap.css

1020 ms

style.css

1097 ms

responsive.css

819 ms

Our browser made a total of 139 requests to load all elements on the main page. We found that 94% of them (130 requests) were addressed to the original Lifelinehospitals.co.in, 3% (4 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (10.8 sec) belongs to the original domain Lifelinehospitals.co.in.

Content Size

7.3 MB

After Optimization

7.1 MB

In fact, the total size of Lifelinehospitals.co.in main page is 7.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 6.6 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 84.8 kB

Original 95.7 kB
After minification 64.0 kB
After compression 10.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 31.6 kB, which is 33% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 84.8 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 31.9 kB

Original 6.6 MB
After minification 6.5 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Lifelinehospitals images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 80.7 kB

Original 518.1 kB
After minification 518.1 kB
After compression 437.4 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 80.7 kB or 16% of the original size.

CSS Optimization

-10%

Potential reduce by 11.0 kB

Original 116.0 kB
After minification 115.7 kB
After compression 104.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Lifelinehospitals.co.in has all CSS files already compressed.

Requests Now

128

After Optimization

The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lifelinehospitals. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

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.

High

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Document doesn't have a <title> element

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

High

Links are not crawlable

High

robots.txt is not valid

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](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifelinehospitals.co.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lifelinehospitals.co.in main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

lifelinehospitals.co.in

Open Graph description is not detected on the main page of Lifelinehospitals. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks:

Report Summary

Performance

Accessibility

Best Practices

SEO

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

lifelinehospitals.co.in

lifelinehospitals.co.in

bootstrap.css

style.css

responsive.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

lifelinehospitals.co.in

lifelinehospitals.co.in

bootstrap.css

style.css

responsive.css

color-switcher-design.css

default-theme.css

location.png

logo.png

certi.png

call.png

logo-small.png

nav-logo.png

wp-section.css

magnific-popup.min.css

popup.css

jquery.js

jquery-ui.js

bootstrap.min.js

wow.js

popper.min.js

jquery.fancybox.js

mixitup.js

parallax.min.js

jquery.paroller.min.js

owl.js

swiper.min.js

appear.js

script.js

color-settings.js

api.js

css

pe-icon-7-stroke.css

simple-line-icons.css

fontawesome-all.css

animate.css

flaticon.css

owl.css

swiper.min.css

jquery-ui.css

custom-animate.css

magnific-popup.css

jquery.fancybox.min.css

jquery.timepicker.min.css