Tools & Wizards About Us
lifetrenz.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

lifetrenz.com

Lifetrenz - EHR integrated Hospital Management System(HMS)

Page Load Speed

4.7 sec in total

First Response

412 ms

Resources Loaded

4.1 sec

Page Rendered

260 ms

lifetrenz.com screenshot

About Website

Click here to check amazing Lifetrenz content for India. Otherwise, check out these important facts you probably never knew about lifetrenz.com

Lifetrenz Hospital Information System, EHR and Hospital ERP, to help your hospital go paperless and manage workflows with our solution available on cloud/ site.

Visit lifetrenz.com

Key Findings

We analyzed Lifetrenz.com page load time and found that the first response time was 412 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

lifetrenz.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value870 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.244

51/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

lifetrenz.com

412 ms

www.lifetrenz.com

774 ms

animate.css

190 ms

font-awesome.css

379 ms

owl.carousel.css

557 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 80% of them (57 requests) were addressed to the original Lifetrenz.com, 6% (4 requests) were made to Marketing.mylifetrenz.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Lifetrenz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 839.9 kB (62%)

Content Size

1.4 MB

After Optimization

511.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lifetrenz.com main page is 1.4 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. 55% of websites need less resources to load. Javascripts take 889.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 23.2 kB

  • Original 29.1 kB
  • After minification 24.0 kB
  • After compression 5.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 5.1 kB, which is 17% 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 23.2 kB or 80% of the original size.

Image Optimization

-51%

Potential reduce by 202.9 kB

  • Original 395.3 kB
  • After minification 192.5 kB

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. Obviously, Lifetrenz needs image optimization as it can save up to 202.9 kB or 51% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-68%

Potential reduce by 608.0 kB

  • Original 889.0 kB
  • After minification 779.4 kB
  • After compression 281.1 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 608.0 kB or 68% of the original size.

CSS Optimization

-16%

Potential reduce by 5.9 kB

  • Original 37.8 kB
  • After minification 37.8 kB
  • After compression 31.8 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. Lifetrenz.com needs all CSS files to be minified and compressed as it can save up to 5.9 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (56%)

Requests Now

62

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lifetrenz.com

lifetrenz.com

412 ms

www.lifetrenz.com

www.lifetrenz.com

774 ms

animate.css

animate.css

190 ms

font-awesome.css

font-awesome.css

379 ms

owl.carousel.css

owl.carousel.css

557 ms

jquery.fancybox.css

jquery.fancybox.css

558 ms

layerslider.css

layerslider.css

561 ms

styles.css

styles.css

757 ms

share.css

share.css

566 ms

css

css

21 ms

addthis_widget.js

addthis_widget.js

346 ms

firecart-integration.js

firecart-integration.js

878 ms

jquery.min.js

jquery.min.js

938 ms

jquery-ui.min.js

jquery-ui.min.js

1480 ms

jquery.migrate.min.js

jquery.migrate.min.js

742 ms

jquery.isotope.min.js

jquery.isotope.min.js

933 ms

jquery.form.min.js

jquery.form.min.js

948 ms

jquery.validate.min.js

jquery.validate.min.js

928 ms

jquery.countdown.min.js

jquery.countdown.min.js

949 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

1112 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

1119 ms

retina.min.js

retina.min.js

1126 ms

SmoothScroll.js

SmoothScroll.js

1128 ms

owl.carousel.min.js

owl.carousel.min.js

1132 ms

jquery.tweet.js

jquery.tweet.js

1299 ms

wow.min.js

wow.min.js

1305 ms

jquery.flot.js

jquery.flot.js

1505 ms

jquery.flot.pie.js

jquery.flot.pie.js

1315 ms

jquery.flot.categories.js

jquery.flot.categories.js

1319 ms

greensock.js

greensock.js

1668 ms

layerslider.transitions.js

layerslider.transitions.js

1505 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

1694 ms

scripts.js

scripts.js

1520 ms

parallax.js

parallax.js

1662 ms

css

css

17 ms

analytics.js

analytics.js

86 ms

rss2html.php

rss2html.php

435 ms

14

14

1185 ms

page-header-top-switcher.png

page-header-top-switcher.png

905 ms

logo.png

logo.png

905 ms

macbook.png

macbook.png

912 ms

iphone.png

iphone.png

1060 ms

ipad-shadow.png

ipad-shadow.png

1066 ms

ipad.png

ipad.png

1263 ms

slide-1-button1.png

slide-1-button1.png

1087 ms

index-awareness.jpg

index-awareness.jpg

1091 ms

index-exsting.jpg

index-exsting.jpg

1095 ms

index-newhospitals.jpg

index-newhospitals.jpg

1244 ms

bg-out.png

bg-out.png

1251 ms

icon-out-patient-g.png

icon-out-patient-g.png

1274 ms

icon-in-patient-g.png

icon-in-patient-g.png

1279 ms

ico_ims-g.png

ico_ims-g.png

1283 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

21 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

22 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

21 ms

collect

collect

17 ms

js

js

63 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1293 ms

icon-mis-report-g.png

icon-mis-report-g.png

1302 ms

ico-operation-g.png

ico-operation-g.png

1294 ms

icon-er&daycare-g.png

icon-er&daycare-g.png

1305 ms

icon-dashboard-g.png

icon-dashboard-g.png

1311 ms

icon-contact-g.png

icon-contact-g.png

1150 ms

rss2html.php

rss2html.php

1368 ms

mtc.js

mtc.js

1108 ms

skin.css

skin.css

694 ms

bg_slide1.jpg

bg_slide1.jpg

702 ms

mautic-form.js

mautic-form.js

297 ms

modal.min.css

modal.min.css

188 ms

blank.gif

blank.gif

188 ms

skin.png

skin.png

186 ms

Accessibility Review

lifetrenz.com accessibility score

76

Accessibility Issues

Names and labels

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.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

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

Impact

Issue

High

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

Tables and lists

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

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

lifetrenz.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

lifetrenz.com SEO score

96

Search Engine Optimization Advices

Mobile Friendly

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

Impact

Issue

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

lifetrenz.com

Open Graph description is not detected on the main page of Lifetrenz. 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: