6.4 sec in total
1.4 sec
4.6 sec
435 ms
Click here to check amazing Plantnativ content for United States. Otherwise, check out these important facts you probably never knew about plantnativ.com
Replace the burnt out grass in your yard with a beautiful drought tolerant landscape for your San Diego home. Save both money and water.
Visit plantnativ.comWe analyzed Plantnativ.com page load time and found that the first response time was 1.4 sec and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
plantnativ.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value8.3 s
2/100
25%
Value6.6 s
37/100
10%
Value1,200 ms
20/100
30%
Value0.091
92/100
15%
Value11.9 s
17/100
10%
1352 ms
194 ms
139 ms
28 ms
39 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 45% of them (36 requests) were addressed to the original Plantnativ.com, 28% (22 requests) were made to Fonts.gstatic.com and 8% (6 requests) were made to Vcita.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Plantnativ.com.
Page size can be reduced by 105.8 kB (50%)
212.4 kB
106.6 kB
In fact, the total size of Plantnativ.com main page is 212.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 162.5 kB which makes up the majority of the site volume.
Potential reduce by 38.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 38.0 kB or 76% of the original size.
Potential reduce by 67.7 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 67.7 kB or 42% of the original size.
Number of requests can be reduced by 37 (69%)
54
17
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plantnativ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.plantnativ.com
1352 ms
wp-emoji-release.min.js
194 ms
styles.css
139 ms
css
28 ms
css
39 ms
css
58 ms
style.css
285 ms
shortcodes.css
217 ms
shortcodes_responsive.css
149 ms
magnific_popup.css
185 ms
jquery.js
404 ms
jquery-migrate.min.js
249 ms
gtm4wp-form-move-tracker.js
258 ms
jquery.min.js
33 ms
conversion.js
31 ms
frontend-builder-global-functions.js
232 ms
jquery.form.min.js
250 ms
scripts.js
269 ms
qppr_frontend_script.min.js
318 ms
jquery.mobile.custom.min.js
293 ms
custom.js
372 ms
jquery.fitvids.js
318 ms
waypoints.min.js
339 ms
jquery.magnific-popup.js
363 ms
frontend-builder-scripts.js
560 ms
wp-embed.min.js
336 ms
style.css
655 ms
loader.js
59 ms
loader
32 ms
livesite.js
111 ms
twitter.png
180 ms
logo-bott.png
446 ms
facebook1.png
182 ms
yelp_2.png
222 ms
instagram.png
182 ms
1509v04-plant-nativ-logo.png
190 ms
1508v04-plant-nativ-pace-loan-lp-image-ygrene-works.jpg
275 ms
gtm.js
90 ms
CJT9124-1.jpg
928 ms
CJT8829-1.jpg
972 ms
CJT1259.jpg
1097 ms
CJT9248.jpg
1095 ms
CJT1192.jpg
1027 ms
wt.pl
412 ms
IgZJs4-7SA1XX_edsoXWog.ttf
86 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
83 ms
DXI1ORHCpsQm3Vp6mXoaTS3USBnSvpkopQaUR-2r7iU.ttf
88 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
82 ms
MTP_ySUJH_bn48VBG8sNSi3USBnSvpkopQaUR-2r7iU.ttf
83 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
85 ms
k3k702ZOKiLJc3WVjuplzC3USBnSvpkopQaUR-2r7iU.ttf
84 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
87 ms
EInbV5DfGHOiMmvb1Xr-hi3USBnSvpkopQaUR-2r7iU.ttf
92 ms
EInbV5DfGHOiMmvb1Xr-htqQynqKV_9Plp7mupa0S4g.ttf
87 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
88 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
89 ms
O4NhV7_qs9r9seTo7fnsVKCWcynf_cDxXwCLxiixG1c.ttf
91 ms
xjAJXh38I15wypJXxuGMBl02b4v3fUxqf9CZJ1qUoIA.ttf
92 ms
PRmiXeptR36kaC0GEAetxi9-WlPSxbfiI49GsXo3q0g.ttf
91 ms
PRmiXeptR36kaC0GEAetxvqEJM-AK1nFUafhVdytxUY.ttf
115 ms
PRmiXeptR36kaC0GEAetxpZ7xm-Bj30Bj2KNdXDzSZg.ttf
116 ms
PRmiXeptR36kaC0GEAetxmYImPRL1w80NlYTQ8LOqf4.ttf
112 ms
PRmiXeptR36kaC0GEAetxne1Pd76Vl7zRpE7NLJQ7XU.ttf
109 ms
PRmiXeptR36kaC0GEAetxiBnJMIPt0VoltfALX9gDFQ.ttf
108 ms
PRmiXeptR36kaC0GEAetxg89PwPrYLaRFJ-HNCU9NbA.ttf
107 ms
PRmiXeptR36kaC0GEAetxk7Gbs5Oj9RrfpUUQRHsz5w.ttf
107 ms
ETmodules_v2_4.ttf
388 ms
livesite.css
58 ms
css
54 ms
hawthorne_avenue_431_15_10418_colored2.png
923 ms
analytics.js
22 ms
piwik.js
454 ms
linkid.js
5 ms
collect
6 ms
collect
216 ms
normal_s4hpa7j1iu301z9fpby2we4yiumrz0zq.png
262 ms
i
67 ms
rain.barrel.pipe_.jpg
820 ms
icomoon.woff
69 ms
33 ms
plantnativ.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-*] attributes do not have valid values
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
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
plantnativ.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
plantnativ.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Plantnativ.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 Plantnativ.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.
plantnativ.com
Open Graph data is detected on the main page of Plantnativ. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: