8.6 sec in total
910 ms
7.2 sec
540 ms
Welcome to plantfile.com homepage info - get ready to check Plant File best content right away, or after learning these important things about plantfile.com
Visit plantfile.comWe analyzed Plantfile.com page load time and found that the first response time was 910 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
plantfile.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value9.5 s
0/100
25%
Value10.8 s
6/100
10%
Value170 ms
93/100
30%
Value1.041
2/100
15%
Value12.0 s
16/100
10%
910 ms
251 ms
883 ms
437 ms
1536 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 95% of them (59 requests) were addressed to the original Plantfile.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Adobe.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Plantfile.com.
Page size can be reduced by 611.6 kB (14%)
4.3 MB
3.7 MB
In fact, the total size of Plantfile.com main page is 4.3 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. 40% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 35.5 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 6.7 kB, 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 35.5 kB or 82% of the original size.
Potential reduce by 224.4 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. Plant File images are well optimized though.
Potential reduce by 329.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 329.0 kB or 74% of the original size.
Potential reduce by 22.7 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. Plantfile.com needs all CSS files to be minified and compressed as it can save up to 22.7 kB or 84% of the original size.
Number of requests can be reduced by 29 (48%)
61
32
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plant File. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
plantfile.com
910 ms
stylesheet_front.css
251 ms
jquery-1.4.2.min.js
883 ms
jquery.cookie.js
437 ms
jquery-ui.min.js
1536 ms
jquery.pretty_photo.js
653 ms
script.js
741 ms
switchcontent.js
741 ms
lightbox.js
658 ms
coin-slider-styles.css
870 ms
lightbox.css
876 ms
coin-slider.js
988 ms
swfobject_modified.js
1239 ms
jquery.cycle.all.latest.js
1304 ms
get_flash_player.gif
24 ms
mainbackground.jpg
2962 ms
headerbg.png
221 ms
logo.png
439 ms
aboutbtn.png
219 ms
contactbtn.png
253 ms
sales_flag.png
228 ms
nav_bg.png
521 ms
nav_sep.jpg
564 ms
navbg_h.jpg
445 ms
home_icon.png
510 ms
plafile_tag.jpg
662 ms
divider.png
662 ms
banner_bg.png
758 ms
617-266-Cedrus-liban_1422325731.gif
975 ms
617-266-Passiflora-caerulea-_1422337091.gif
1441 ms
617-266-Trillium-chloropetalum-_1422337930.gif
1759 ms
617-266-Primula-auricula_1422325126.gif
1318 ms
617-266-Nymphaea-species_1422324562.gif
1999 ms
617-266-Actinotus-helianth_1422338828.gif
1418 ms
617-266-Tulipa-x-hybrida_1422339498.gif
1772 ms
onlinedemo_tag.png
1666 ms
demo_bg.png
1658 ms
plantfile_online_demo.png
4285 ms
contentbg.png
1883 ms
grey_title.gif
2002 ms
tour_btn.png
1990 ms
plantfilestandard.jpg
2103 ms
iplantfilepro.jpg
2216 ms
facebook_icon.png
2250 ms
twitter_icon.png
2219 ms
new_prev.png
2302 ms
new_next.png
2414 ms
newsdivider.png
2411 ms
dotteddivider.png
2471 ms
readmore_btn.png
2606 ms
footerbg.png
2625 ms
ga.js
38 ms
__utm.gif
15 ms
bullet.png
2439 ms
testimonialbg.png
2534 ms
test_prev.png
2626 ms
test_next.png
2632 ms
blank.gif
393 ms
loading.gif
309 ms
close.gif
354 ms
circle_sel.png
219 ms
circle.png
250 ms
plantfile.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
plantfile.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
plantfile.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plantfile.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 Plantfile.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.
plantfile.com
Open Graph description is not detected on the main page of Plant File. 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: