11.3 sec in total
1.9 sec
8.8 sec
626 ms
Click here to check amazing Plantplots content. Otherwise, check out these important facts you probably never knew about plantplots.com
Brilliantly simple garden design advice for beginners. Specialist in small garden design, garden consultation service and easy planting ideas.
Visit plantplots.comWe analyzed Plantplots.com page load time and found that the first response time was 1.9 sec and then it took 9.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
plantplots.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value0
0/100
25%
Value14.8 s
1/100
10%
Value3,040 ms
2/100
30%
Value0
100/100
15%
Value16.7 s
5/100
10%
1933 ms
157 ms
313 ms
401 ms
236 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 86% of them (111 requests) were addressed to the original Plantplots.com, 2% (3 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Plantplots.com.
Page size can be reduced by 1.9 MB (10%)
20.1 MB
18.2 MB
In fact, the total size of Plantplots.com main page is 20.1 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. 85% 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. Images take 18.9 MB which makes up the majority of the site volume.
Potential reduce by 188.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. 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 188.4 kB or 82% of the original size.
Potential reduce by 1.6 MB
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. Plantplots images are well optimized though.
Potential reduce by 93.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 93.9 kB or 13% of the original size.
Potential reduce by 55.0 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. Plantplots.com needs all CSS files to be minified and compressed as it can save up to 55.0 kB or 20% of the original size.
Number of requests can be reduced by 96 (79%)
122
26
The browser has sent 122 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plantplots. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 72 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
plantplots.com
1933 ms
vtprd-front-end-min.css
157 ms
bootstrap.min.css
313 ms
style.css
401 ms
style.css
236 ms
extendify-utilities.css
240 ms
styles.css
243 ms
kd_vc_front.css
413 ms
style.css
242 ms
woo-social-discounts-public.css
246 ms
dashicons.min.css
335 ms
form-themes.css
316 ms
field_social_profiles_frontend.css
317 ms
js_composer.min.css
498 ms
style.css
394 ms
woocommerce.css
401 ms
font-awesome.min.css
409 ms
v4-shims.css
414 ms
wp-polyfill-inert.min.js
416 ms
regenerator-runtime.min.js
473 ms
wp-polyfill.min.js
489 ms
hooks.min.js
488 ms
w.js
31 ms
jquery.min.js
512 ms
jquery-migrate.min.js
513 ms
devtools-detect.js
552 ms
owl.carousel.min.js
569 ms
kd_addon_script.js
570 ms
headerScript.min.js'%20async='async
2183 ms
jquery.blockUI.min.js
577 ms
js.cookie.min.js
579 ms
woocommerce.min.js
630 ms
woocommerce-keydesign.js
648 ms
js
67 ms
js
128 ms
css
42 ms
animate.min.css
647 ms
css
53 ms
iconsmind-Video-Class.css
656 ms
iconsmind-Nature.css
659 ms
photoswipe.css
706 ms
api.js
48 ms
index.js
723 ms
index.js
655 ms
frontend.min.js
588 ms
sourcebuster.min.js
582 ms
order-attribution.min.js
627 ms
react.min.js
571 ms
deprecated.min.js
573 ms
genericons.css
583 ms
dom.min.js
517 ms
react-dom.min.js
640 ms
escape-html.min.js
558 ms
element.min.js
558 ms
is-shallow-equal.min.js
565 ms
i18n.min.js
521 ms
keycodes.min.js
565 ms
priority-queue.min.js
561 ms
compose.min.js
579 ms
private-apis.min.js
580 ms
redux-routine.min.js
563 ms
data.min.js
565 ms
lodash.min.js
567 ms
wc-blocks-registry.js
566 ms
url.min.js
565 ms
api-fetch.min.js
601 ms
wc-settings.js
581 ms
data-controls.min.js
567 ms
html-entities.min.js
590 ms
notices.min.js
581 ms
wc-blocks-middleware.js
613 ms
wc-blocks-data.js
587 ms
dom-ready.min.js
566 ms
a11y.min.js
590 ms
primitives.min.js
581 ms
warning.min.js
608 ms
blocks-components.js
589 ms
blocks-checkout.js
581 ms
order-attribution-blocks.min.js
591 ms
mailchimp-woocommerce-public.min.js
581 ms
bootstrap.min.js
607 ms
scripts.js
589 ms
scripts.js
583 ms
index.js
644 ms
genericons.css
581 ms
js_composer_front.min.js
627 ms
vc-waypoints.min.js
570 ms
photoswipe.min.js
583 ms
imagesloaded.pkgd.min.js
584 ms
underscore.min.js
579 ms
vc_grid.min.js
558 ms
masonry.pkgd.min.js
569 ms
g.gif
22 ms
fbevents.js
135 ms
gtm.js
130 ms
logo.png
221 ms
garden-design-hp-header.jpg
675 ms
garden-border-plantin-plans-home-pg.png
932 ms
garden-design-gallery.png
933 ms
Design-an-amazing-garden.png
1239 ms
best-for-beginners.png
3754 ms
style-sheets-home-1.png
934 ms
Before-and-after-images-for-home-page-AA-2022.png
1030 ms
Before-and-after-images-for-home-page-SD-2021.png
1031 ms
Before-and-after-images-for-home-page-SH-2018.png
1033 ms
garden-design-before-after-hp1.jpg
1031 ms
Before-and-after-images-for-home-page-AO-2020.png
1149 ms
portfolio-image-LC-formal-garden-layout.png
1179 ms
plant-plots-amazon-book-350x350.png
1087 ms
Design-service-page-image.png
1180 ms
trustpilot-logo-black-small-plus-text.png
1178 ms
US_UK_Apple_Podcasts_Listen_Badge_RGB.svg
1235 ms
analytics.js
111 ms
font
249 ms
sway-font.woff
1103 ms
core.js
242 ms
fbevents.js
81 ms
collect
53 ms
9cfd5e8f54ce65e7f23ea4dd6.js
337 ms
collect
151 ms
recaptcha__en.js
143 ms
font
99 ms
Video-Class.woff
691 ms
Nature.woff
692 ms
admin-ajax.php
2155 ms
admin.css
80 ms
Cool-Stuff-we-just-like-bp-fi.jpg
238 ms
landscape-design-advice.png
403 ms
how-to-avoid-garden-design-mistakes.png
396 ms
plantplots.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
plantplots.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
plantplots.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
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 Plantplots.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 Plantplots.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.
plantplots.com
Open Graph data is detected on the main page of Plantplots. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: