Tools & Wizards About Us
easyplant.co.in screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% 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

  • 81

    SEO

    Google-friendlier than
    42% of websites

easyplant.co.in

Page Load Speed

6.5 sec in total

First Response

1.1 sec

Resources Loaded

5.3 sec

Page Rendered

209 ms

easyplant.co.in screenshot

About Website

Welcome to easyplant.co.in homepage info - get ready to check Easyplant best content right away, or after learning these important things about easyplant.co.in

The all in one plant app in 10 Indian languages that helps homemakers live their jungle dream.

Visit easyplant.co.in

Key Findings

We analyzed Easyplant.co.in page load time and found that the first response time was 1.1 sec and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

easyplant.co.in performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value7.2 s

5/100

25%

SI (Speed Index)

Value5.6 s

52/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

easyplant.co.in

1055 ms

jongl.in

1131 ms

custom.css

1648 ms

jquery-ui.css

44 ms

JongL_Logo.png

1601 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Easyplant.co.in, 63% (19 requests) were made to Jongl.in and 23% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Jongl.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 51.3 kB (25%)

Content Size

202.7 kB

After Optimization

151.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-94%

Potential reduce by 30.3 kB

  • Original 32.3 kB
  • After minification 5.1 kB
  • After compression 2.0 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 27.2 kB, which is 84% 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 30.3 kB or 94% of the original size.

Image Optimization

-18%

Potential reduce by 17.0 kB

  • Original 96.6 kB
  • After minification 79.6 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, Easyplant needs image optimization as it can save up to 17.0 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 636 B

  • Original 55.8 kB
  • After minification 55.8 kB
  • After compression 55.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. This website has mostly compressed JavaScripts.

CSS Optimization

-18%

Potential reduce by 3.3 kB

  • Original 18.0 kB
  • After minification 18.0 kB
  • After compression 14.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. Easyplant.co.in needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (62%)

Requests Now

13

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

easyplant.co.in

easyplant.co.in

1055 ms

jongl.in

jongl.in

1131 ms

custom.css

custom.css

1648 ms

jquery-ui.css

jquery-ui.css

44 ms

JongL_Logo.png

JongL_Logo.png

1601 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

1669 ms

popper.min.js

popper.min.js

1372 ms

bootstrap.min.js

bootstrap.min.js

1634 ms

plugins.js

plugins.js

1911 ms

back-stretch.js

back-stretch.js

2753 ms

active.js

active.js

2724 ms

iframe_api.js

iframe_api.js

2736 ms

www-widgetapi.js

www-widgetapi.js

3024 ms

videosPlayerController.js

videosPlayerController.js

3047 ms

css

css

34 ms

bootstrap.min.css

bootstrap.min.css

267 ms

classy-nav.css

classy-nav.css

266 ms

owl.carousel.min.css

owl.carousel.min.css

266 ms

animate.css

animate.css

267 ms

magnific-popup.css

magnific-popup.css

267 ms

font-awesome.min.css

font-awesome.min.css

266 ms

elegant-icon.css

elegant-icon.css

266 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl2xMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl2xMB.ttf

48 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7Ml2xMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7Ml2xMB.ttf

35 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl2xMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl2xMB.ttf

39 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ml2xMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ml2xMB.ttf

40 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl2xMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl2xMB.ttf

37 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJ0LQl2xMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJ0LQl2xMB.ttf

41 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ql2xMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ql2xMB.ttf

42 ms

www-widgetapi.js

www-widgetapi.js

182 ms

Accessibility Review

easyplant.co.in 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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

Best Practices

easyplant.co.in 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

easyplant.co.in SEO score

81

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Easyplant.co.in can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Easyplant.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

easyplant.co.in

Open Graph data is detected on the main page of Easyplant. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: