4.7 sec in total
302 ms
2.3 sec
2 sec
Visit plantingplanner.com now to see the best up-to-date Planting Planner content and also check out these interesting facts you probably never knew about plantingplanner.com
Stunning, bespoke planting plans, tailored for your garden's growing conditions, with your choice of colour and style. Intelligent generator, with flexible interactive tools to allow you to take ...
Visit plantingplanner.comWe analyzed Plantingplanner.com page load time and found that the first response time was 302 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
plantingplanner.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value4.2 s
44/100
25%
Value5.6 s
52/100
10%
Value130 ms
96/100
30%
Value0.067
97/100
15%
Value5.2 s
74/100
10%
302 ms
390 ms
488 ms
198 ms
47 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 90% of them (37 requests) were addressed to the original Plantingplanner.com, 5% (2 requests) were made to Cdnjs.cloudflare.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (860 ms) belongs to the original domain Plantingplanner.com.
Page size can be reduced by 40.0 kB (4%)
1.1 MB
1.1 MB
In fact, the total size of Plantingplanner.com main page is 1.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. 30% of websites need less resources to load. Images take 960.7 kB which makes up the majority of the site volume.
Potential reduce by 37.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 7.2 kB, which is 15% 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 37.5 kB or 81% of the original size.
Potential reduce by 2.5 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. Planting Planner images are well optimized though.
Potential reduce by 24 B
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 35 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. Plantingplanner.com has all CSS files already compressed.
We found no issues to fix!
36
36
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Planting Planner. According to our analytics all requests are already optimized.
plantingplanner.com
302 ms
plantingplanner.com
390 ms
www.plantingplanner.com
488 ms
app.css
198 ms
font-awesome.min.css
47 ms
gdpr-cookie-preload.js
285 ms
app.js
479 ms
css
33 ms
planting-planner-logo.jpg
99 ms
flower-border-clematis-viticella-purpurea.jpg
281 ms
garden-border-eryngium.jpg
240 ms
garden-border-nectaroscordum-siculum.jpg
376 ms
garden-border-veronica.jpg
470 ms
garden-border-cotinus-rubrifolius.jpg
469 ms
garden-border-acer-japonicum-vitifolium.jpg
383 ms
garden-border-centaurea-montana.jpg
295 ms
garden-border-astrantia.jpg
470 ms
garden-border-crocus.jpg
484 ms
garden-plant-erigeron-karvinskianus.jpg
567 ms
flower-border-astrantia-major-abbey-rd.jpg
479 ms
flower-border-campanula-lactiflora-loddon.jpg
567 ms
flower-border-verbena-bonariensis.jpg
567 ms
garden-border-aster-pyrenaeus-lutetia.jpg
568 ms
garden-border-japanese-anemone.jpg
577 ms
garden-border-anemone-blanda.jpg
581 ms
garden-border-acer-palmatum.jpg
666 ms
garden-border-aquilegia.jpg
664 ms
garden-border-lagurus-ovatus.jpg
664 ms
spring-garden-border-narcissus-hawera.jpg
664 ms
summer-border-echinops-bannaticus-taplow.jpg
676 ms
autumn-garden-border-amelanchier-canadensis.jpg
677 ms
winter-garden-border-holly-in-snow.jpg
769 ms
spring-crocuses.jpg
767 ms
rosa-falstaff.jpg
765 ms
elderberries.jpg
768 ms
hamamelis-x-intermedia-jelena.jpg
772 ms
echinops-bannaticus-taplow.jpg
775 ms
galium-&-ajuga.jpg
860 ms
garden-design-sprites.png
858 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
33 ms
fontawesome-webfont.woff
19 ms
plantingplanner.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.
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 IDs are not unique
plantingplanner.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
plantingplanner.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 Plantingplanner.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 Plantingplanner.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.
plantingplanner.com
Open Graph data is detected on the main page of Planting Planner. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: