Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

saplings.live

Online Plant Nursery In Bangalore | Saplings Live Nursery | Bengaluru

Page Load Speed

2.8 sec in total

First Response

192 ms

Resources Loaded

2.6 sec

Page Rendered

62 ms

saplings.live screenshot

About Website

Welcome to saplings.live homepage info - get ready to check Saplings best content right away, or after learning these important things about saplings.live

Online Plant Nursery in Bangalore| Indoor Plants for Office. saplings.live #1 Online Plant Nursery in Bangalore, offers to Buy Indoor and outdoor Plants | Buy Indoor Plants for Office & Home

Visit saplings.live

Key Findings

We analyzed Saplings.live page load time and found that the first response time was 192 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

saplings.live performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value2,210 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

www.saplings.live

192 ms

minified.js

36 ms

focus-within-polyfill.js

81 ms

polyfill.min.js

413 ms

wix_loader.js

138 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Saplings.live, 58% (42 requests) were made to Static.wixstatic.com and 19% (14 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (69%)

Content Size

2.1 MB

After Optimization

637.3 kB

In fact, the total size of Saplings.live main page is 2.1 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. 30% of websites need less resources to load. HTML takes 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 1.4 MB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 296.8 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 1.4 MB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 10.9 kB

  • Original 129.9 kB
  • After minification 119.0 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. Saplings images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.3 kB

  • Original 224.9 kB
  • After minification 224.8 kB
  • After compression 221.6 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.

Requests Breakdown

Number of requests can be reduced by 11 (19%)

Requests Now

57

After Optimization

46

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

Accessibility Review

saplings.live accessibility score

98

Accessibility Issues

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.

Best Practices

saplings.live best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

saplings.live SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Saplings.live 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 Saplings.live 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

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