6.4 sec in total
957 ms
5.3 sec
117 ms
Click here to check amazing Planty content for India. Otherwise, check out these important facts you probably never knew about planty.in
Visit planty.inWe analyzed Planty.in page load time and found that the first response time was 957 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
planty.in performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value3.0 s
78/100
25%
Value2.5 s
98/100
10%
Value160 ms
93/100
30%
Value0.09
92/100
15%
Value3.3 s
94/100
10%
957 ms
324 ms
621 ms
35 ms
672 ms
Our browser made a total of 22 requests to load all elements on the main page. We found that 82% of them (18 requests) were addressed to the original Planty.in, 9% (2 requests) were made to Fonts.gstatic.com and 5% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Planty.in.
Page size can be reduced by 135.6 kB (14%)
944.5 kB
809.0 kB
In fact, the total size of Planty.in main page is 944.5 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. 25% of websites need less resources to load. Images take 835.0 kB which makes up the majority of the site volume.
Potential reduce by 3.4 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 814 B, which is 16% 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 3.4 kB or 68% of the original size.
Potential reduce by 42.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. Planty images are well optimized though.
Potential reduce by 87.0 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 87.0 kB or 86% of the original size.
Potential reduce by 2.6 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. Planty.in needs all CSS files to be minified and compressed as it can save up to 2.6 kB or 73% of the original size.
Number of requests can be reduced by 6 (32%)
19
13
The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Planty. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
planty.in
957 ms
maximage.css
324 ms
styles.css
621 ms
jquery.js
35 ms
jquery.easing.min.js
672 ms
jquery.cycle.all.js
672 ms
jquery.maximage.js
673 ms
jquery.fullscreen.js
669 ms
jquery.ba-hashchange.js
675 ms
main.js
931 ms
icon-facebook.png
965 ms
icon-twitter.png
962 ms
icon-google.png
966 ms
icon-dribbble.png
967 ms
icon-linkedin.png
965 ms
icon-pinterest.png
1242 ms
bg-img-1.jpg
4330 ms
gradient.png
2829 ms
css
22 ms
full-screen-btn.png
624 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
6 ms
A3DqZ8KQbto2lGg0IL8SIvesZW2xOQ-xsNqO47m55DA.ttf
8 ms
planty.in accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
planty.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
planty.in SEO score
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
Document uses legible font sizes
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Planty.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 Planty.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.
planty.in
Open Graph description is not detected on the main page of Planty. 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: