Tools & Wizards About Us
nanolife.in screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

nanolife.in

Nanolife : Nanomedicine Products & Speciality Medical Centre

Page Load Speed

15.2 sec in total

First Response

148 ms

Resources Loaded

14.3 sec

Page Rendered

708 ms

nanolife.in screenshot

About Website

Click here to check amazing Nanolife content. Otherwise, check out these important facts you probably never knew about nanolife.in

NanOlife is the pioneer to use the scientific concept of 'Green Nanotechnology' to develop Nanomedicine for crucial diseases and Lifestyle Products.x

Visit nanolife.in

Key Findings

We analyzed Nanolife.in page load time and found that the first response time was 148 ms and then it took 15 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

nanolife.in performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value17.6 s

0/100

10%

TBT (Total Blocking Time)

Value1,660 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.541

14/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

nanolife.in

148 ms

nanolife.in

1076 ms

bootstrap.min.css

1052 ms

font-awesome.min.css

1036 ms

css

57 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 85% of them (66 requests) were addressed to the original Nanolife.in, 5% (4 requests) were made to Fonts.googleapis.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (7.7 sec) belongs to the original domain Nanolife.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (18%)

Content Size

5.9 MB

After Optimization

4.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nanolife.in main page is 5.9 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. Images take 5.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 47.7 kB

  • Original 56.3 kB
  • After minification 39.3 kB
  • After compression 8.6 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 17.0 kB, which is 30% 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 47.7 kB or 85% of the original size.

Image Optimization

-16%

Potential reduce by 856.5 kB

  • Original 5.5 MB
  • After minification 4.6 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. Obviously, Nanolife needs image optimization as it can save up to 856.5 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-45%

Potential reduce by 141.7 kB

  • Original 316.2 kB
  • After minification 316.2 kB
  • After compression 174.5 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 141.7 kB or 45% of the original size.

CSS Optimization

-10%

Potential reduce by 6.8 kB

  • Original 68.1 kB
  • After minification 67.8 kB
  • After compression 61.3 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. Nanolife.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (54%)

Requests Now

69

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nanolife.in

nanolife.in

148 ms

nanolife.in

nanolife.in

1076 ms

bootstrap.min.css

bootstrap.min.css

1052 ms

font-awesome.min.css

font-awesome.min.css

1036 ms

css

css

57 ms

lightbox.css

lightbox.css

1025 ms

fontastic.css

fontastic.css

1930 ms

style.default.css

style.default.css

1089 ms

custom.css

custom.css

1036 ms

animate.min.css

animate.min.css

2032 ms

swiper.min.css

swiper.min.css

2046 ms

colorfulTab.min.css

colorfulTab.min.css

2067 ms

reset.css

reset.css

2028 ms

demo.css

demo.css

2138 ms

input-material.css

input-material.css

2924 ms

style.css

style.css

3042 ms

flickity.css

flickity.css

3064 ms

js

js

77 ms

jquery.js

jquery.js

44 ms

swc.js

swc.js

3098 ms

swc.css

swc.css

3099 ms

jquery.preloadinator.min.js

jquery.preloadinator.min.js

3151 ms

email-decode.min.js

email-decode.min.js

2925 ms

header.js

header.js

4654 ms

jquery.min.js

jquery.min.js

4083 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

4097 ms

jquery.cookie.js

jquery.cookie.js

4860 ms

lightbox.js

lightbox.js

4112 ms

front.js

front.js

4176 ms

flickity.pkgd.js

flickity.pkgd.js

5125 ms

wow.min.js

wow.min.js

5129 ms

particles.min.js

particles.min.js

5142 ms

mobile-nav_home.js

mobile-nav_home.js

5207 ms

waypoints.min.js

waypoints.min.js

5710 ms

counterup.min.js

counterup.min.js

5850 ms

swiper.min.js

swiper.min.js

6197 ms

colorfulTab.min.js

colorfulTab.min.js

6904 ms

jquery.validate.min.js

jquery.validate.min.js

49 ms

materialize-inputs.jquery.js

materialize-inputs.jquery.js

6144 ms

scc-c2.min.js

scc-c2.min.js

12 ms

css

css

24 ms

css

css

23 ms

css

css

22 ms

gtm.js

gtm.js

43 ms

preloader-1.gif

preloader-1.gif

3164 ms

logo.svg

logo.svg

3617 ms

banner-bg-new1.jpg

banner-bg-new1.jpg

3743 ms

banner-bg-new2.jpg

banner-bg-new2.jpg

4115 ms

banner-bg-new3.png

banner-bg-new3.png

4147 ms

banner-bg-new6.jpg

banner-bg-new6.jpg

4173 ms

nano-product.png

nano-product.png

4617 ms

curved-img1-new.png

curved-img1-new.png

5492 ms

animated-leaf.png

animated-leaf.png

4795 ms

no-risk-img.svg

no-risk-img.svg

5178 ms

30years-img.svg

30years-img.svg

5195 ms

certified-img.svg

certified-img.svg

5169 ms

150plus-img.svg

150plus-img.svg

6442 ms

curved-img2-new.png

curved-img2-new.png

6630 ms

animated-leaf1.png

animated-leaf1.png

6194 ms

curved-img3-new.png

curved-img3-new.png

7264 ms

phs-lemon-curved.png

phs-lemon-curved.png

6928 ms

mail-icon.svg

mail-icon.svg

6490 ms

footer-logo.png

footer-logo.png

6466 ms

pxiEyp8kv8JHgFVrJJfedA.woff

pxiEyp8kv8JHgFVrJJfedA.woff

17 ms

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

pxiByp8kv8JHgFVrLDz8Z1xlEw.woff

19 ms

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

pxiByp8kv8JHgFVrLEj6Z1xlEw.woff

23 ms

golden-leaf-right.png

golden-leaf-right.png

7367 ms

dots-bg.png

dots-bg.png

7679 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

6754 ms

golden-leaf-left.png

golden-leaf-left.png

7489 ms

right-dots-bg.png

right-dots-bg.png

6190 ms

m_v-img-new.png

m_v-img-new.png

7645 ms

leaf2.png

leaf2.png

6655 ms

leaf1.png

leaf1.png

7546 ms

prev.png

prev.png

4897 ms

next.png

next.png

4879 ms

loading.gif

loading.gif

6102 ms

close.png

close.png

5639 ms

Accessibility Review

nanolife.in accessibility score

53

Accessibility Issues

ARIA

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.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Best Practices

nanolife.in best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

nanolife.in SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nanolife.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Nanolife.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

nanolife.in

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