858 ms in total
112 ms
630 ms
116 ms
Click here to check amazing Perennials content for United States. Otherwise, check out these important facts you probably never knew about perennials.com
A perennial plant database of over 4000 perennials, photos, detailed perennial plant profiles, gardening tips and information, resources, videos and more featuring Heritage Perennials.
Visit perennials.comWe analyzed Perennials.com page load time and found that the first response time was 112 ms and then it took 746 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
perennials.com performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value8.0 s
2/100
25%
Value3.0 s
94/100
10%
Value90 ms
99/100
30%
Value0
100/100
15%
Value4.5 s
82/100
10%
112 ms
176 ms
118 ms
14 ms
26 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 80% of them (43 requests) were addressed to the original Perennials.com, 6% (3 requests) were made to Maxcdn.bootstrapcdn.com and 4% (2 requests) were made to The.gatekeeperconsent.com. The less responsive or slowest element that took the longest time to load (234 ms) belongs to the original domain Perennials.com.
Page size can be reduced by 63.6 kB (28%)
230.9 kB
167.3 kB
In fact, the total size of Perennials.com main page is 230.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. 40% of websites need less resources to load. Javascripts take 114.3 kB which makes up the majority of the site volume.
Potential reduce by 36.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. 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 36.0 kB or 74% of the original size.
Potential reduce by 18.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, Perennials needs image optimization as it can save up to 18.6 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 8.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.
Potential reduce by 897 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. Perennials.com needs all CSS files to be minified and compressed as it can save up to 897 B or 16% of the original size.
Number of requests can be reduced by 30 (67%)
45
15
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Perennials. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
perennials.com
112 ms
www.perennials.com
176 ms
gppstub.js
118 ms
boise.js
14 ms
abilene.js
26 ms
et.js
23 ms
main_bs.css
21 ms
bootstrap.min.css
39 ms
font-awesome.min.css
51 ms
jquery-1.6.1.min.js
28 ms
main.js
28 ms
bootstrap.min.js
70 ms
jquery.autocomplete.js
26 ms
jquery.autocomplete.css
46 ms
jquery.simplemodal.js
43 ms
simplemodal.css
30 ms
jquery.cycle.js
46 ms
ccpaplus.js
116 ms
v.js
44 ms
mulvane.js
22 ms
wichita.js
23 ms
raleigh.js
24 ms
vista.js
45 ms
olathe.js
66 ms
gtm.js
67 ms
ga.js
44 ms
ezoic.png
71 ms
vitals.js
36 ms
drake.js
36 ms
chanute.js
35 ms
jellyfish.js
53 ms
home.gif
28 ms
dash_white.gif
28 ms
dash_brown.gif
29 ms
button_fb.gif
30 ms
button_twitter.gif
30 ms
text.png
34 ms
search_mag.gif
34 ms
search_adv.gif
34 ms
index_randomimage_show.html
219 ms
indextab2.png
99 ms
header_wp.png
102 ms
showpic_source.html
187 ms
showpic_source.html
186 ms
showpic_source.html
156 ms
showpic_source.html
234 ms
header_top10.png
116 ms
frontimage2.jpg
198 ms
header_101.png
227 ms
frontimage1.jpg
196 ms
heritage.gif
196 ms
x.png
208 ms
__utm.gif
17 ms
collect
28 ms
perennials.com 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.
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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
perennials.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
perennials.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Perennials.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 Perennials.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.
perennials.com
Open Graph description is not detected on the main page of Perennials. 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: