2.5 sec in total
373 ms
1.8 sec
285 ms
Visit plantdex.com now to see the best up-to-date Plantdex content and also check out these interesting facts you probably never knew about plantdex.com
Plantdex is a resource for learning about gardening, growing plants and a variety of cultivation techniques.
Visit plantdex.comWe analyzed Plantdex.com page load time and found that the first response time was 373 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
plantdex.com performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value4.5 s
37/100
25%
Value6.4 s
40/100
10%
Value1,480 ms
14/100
30%
Value0.016
100/100
15%
Value19.8 s
2/100
10%
373 ms
530 ms
532 ms
578 ms
25 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 56% of them (27 requests) were addressed to the original Plantdex.com, 17% (8 requests) were made to Apis.google.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (914 ms) belongs to the original domain Plantdex.com.
Page size can be reduced by 281.6 kB (37%)
755.9 kB
474.3 kB
In fact, the total size of Plantdex.com main page is 755.9 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. 50% of websites need less resources to load. Javascripts take 386.9 kB which makes up the majority of the site volume.
Potential reduce by 30.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 11.2 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 30.5 kB or 82% of the original size.
Potential reduce by 2.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. Plantdex images are well optimized though.
Potential reduce by 247.9 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 247.9 kB or 64% of the original size.
Potential reduce by 756 B
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. Plantdex.com needs all CSS files to be minified and compressed as it can save up to 756 B or 75% of the original size.
Number of requests can be reduced by 32 (70%)
46
14
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plantdex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
plantdex.com
373 ms
css-b825f3c52f788bffb336b70841e64d5d.php
530 ms
css-65e8a0c34a9ba3c33bde936c312763e7.php
532 ms
css-c56635325fc55b65605b8593686ea2c0.php
578 ms
css
25 ms
css-770185ec8ef391b42bf11c0f65dcd00c.php
526 ms
style.css
391 ms
mootools-core.js
576 ms
core.js
457 ms
caption.js
527 ms
mootools-more.js
914 ms
js-68f271c6951b263039b23963e42aae0c.php
620 ms
ti.js
47 ms
e3c32f8d-35aa-41d1-87a1-ee269b3aade9.jpg
206 ms
logo.png
113 ms
dark-70.png
113 ms
diag-lines2.png
113 ms
menu-arrows.png
111 ms
arrow-accent.png
111 ms
Venus%20Flytrap.jpg
337 ms
Oncidium.jpg
226 ms
Snowy%20Lady%20Slipper%20Orchids.jpg
442 ms
delicious.png
202 ms
facebook.png
201 ms
stumbleupon.png
238 ms
technorati.png
236 ms
twitter.png
256 ms
plusone.js
117 ms
dark-10.png
259 ms
horz-line.png
269 ms
xIAtSaglM8LZOYdGmG1JqQ.woff
51 ms
ga.js
67 ms
p
62 ms
aQw38yfiyr4OSjacwqm_6r.js
14 ms
__utm.gif
26 ms
cb=gapi.loaded_0
13 ms
cb=gapi.loaded_1
10 ms
fastbutton
64 ms
postmessageRelay
43 ms
v2
51 ms
cb=gapi.loaded_0
12 ms
cb=gapi.loaded_1
15 ms
3193398744-postmessagerelay.js
25 ms
rpc:shindig_random.js
47 ms
dpx
6 ms
cb=gapi.loaded_0
4 ms
xrefid.xgi
6 ms
ca.png
167 ms
plantdex.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
plantdex.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
plantdex.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plantdex.com 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 Plantdex.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.
plantdex.com
Open Graph description is not detected on the main page of Plantdex. 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: