2.3 sec in total
143 ms
1.6 sec
503 ms
Visit parkgreenhouse.net now to see the best up-to-date Parkgreenhouse content and also check out these interesting facts you probably never knew about parkgreenhouse.net
Garden Center
Visit parkgreenhouse.netWe analyzed Parkgreenhouse.net page load time and found that the first response time was 143 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 45% of websites can load faster.
parkgreenhouse.net performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value4.6 s
35/100
25%
Value3.2 s
91/100
10%
Value90 ms
99/100
30%
Value0.058
98/100
15%
Value4.6 s
81/100
10%
143 ms
59 ms
72 ms
70 ms
87 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Parkgreenhouse.net, 29% (22 requests) were made to Static.websimages.com and 13% (10 requests) were made to Mediaprocessor.websimages.com. The less responsive or slowest element that took the longest time to load (811 ms) relates to the external source Members.webs.com.
Page size can be reduced by 316.5 kB (13%)
2.5 MB
2.2 MB
In fact, the total size of Parkgreenhouse.net main page is 2.5 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. 65% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 95.1 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 95.1 kB or 78% of the original size.
Potential reduce by 0 B
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. Parkgreenhouse images are well optimized though.
Potential reduce by 69.3 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 69.3 kB or 40% of the original size.
Potential reduce by 152.1 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. Parkgreenhouse.net needs all CSS files to be minified and compressed as it can save up to 152.1 kB or 88% of the original size.
Number of requests can be reduced by 45 (64%)
70
25
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Parkgreenhouse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
parkgreenhouse-net.webs.com
143 ms
css
59 ms
css
72 ms
modernizr-old.js
70 ms
require.js
87 ms
jquery.min.js
55 ms
bootstrap.js
124 ms
.theme.css
68 ms
sitebase.css
164 ms
api.js
55 ms
view.app.js
175 ms
collector.js
119 ms
subheader-bg.png
591 ms
IK2C7ik.jpg
591 ms
ModuleClassLoader.js
48 ms
base.js
47 ms
log.js
56 ms
webs.modules.js
46 ms
sitebase.js
54 ms
css_browser_selector.js
251 ms
tylffFQ.jpg
470 ms
dark-1-sprite.png
450 ms
ga.js
395 ms
analytics.js
429 ms
style03.png
794 ms
style01.png
811 ms
ZTujREd.jpg
778 ms
pHuzFAT.jpg
571 ms
HSDtJRC.jpg
575 ms
mcdYcLq.jpg
437 ms
KJx08yD.jpg
532 ms
rSEbhnz.jpg
776 ms
0Lmi5Qa.jpg
576 ms
dbUA5W7.jpg
776 ms
XwT3UN4.jpg
780 ms
main-header-wrapper-bg.jpg
438 ms
nav_small.png
437 ms
nav_small_edges.png
437 ms
nav_large.png
438 ms
star.png
436 ms
menu-primary-item-border.png
552 ms
btn-previous-1.png
566 ms
homepage-slider-control-bg-sprite.png
724 ms
homepage-slider-control-item-ico.png
548 ms
btn-next-1.png
723 ms
main-body-bg.jpg
792 ms
title_bg.png
788 ms
stitch-ends.png
787 ms
ico-bullet-5.png
772 ms
footer-tile.jpg
803 ms
recaptcha__en.js
546 ms
spine.min.js
316 ms
tooltip.js
313 ms
nodeDataTooltip.js
312 ms
creativeCommons.js
312 ms
3XFuErgg3YsZ5fqUU-2LkHHhZfw.ttf
339 ms
3XFpErgg3YsZ5fqUU-UIt2E.ttf
512 ms
k3kUo8kEI-tA1RRcTZGmTlHGCaI.ttf
591 ms
KtkuALODe433f0j1zMnFHdU.ttf
592 ms
KtkpALODe433f0j1zMF-OMWl42Q.ttf
591 ms
link.js
100 ms
underscore.js
100 ms
translate.js
98 ms
collect
294 ms
tooltip.css
273 ms
localize.js
218 ms
locale.js
217 ms
57 ms
collect
122 ms
header_editor_view.js
36 ms
carousel_view.js
31 ms
text_image_view.js
27 ms
horizontal_rule_view.js
30 ms
title_view.js
29 ms
image_view.js
27 ms
social-links_view.js
30 ms
parkgreenhouse.net 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
Image elements do not have [alt] attributes
Links do not have a discernible name
parkgreenhouse.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
parkgreenhouse.net 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
Image elements do not have [alt] attributes
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Parkgreenhouse.net 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 Parkgreenhouse.net 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.
parkgreenhouse.net
Open Graph data is detected on the main page of Parkgreenhouse. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: