2.3 sec in total
198 ms
1.7 sec
417 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 198 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 40% of websites can load faster.
parkgreenhouse.net performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value8.1 s
2/100
25%
Value10.1 s
9/100
10%
Value7,510 ms
0/100
30%
Value0
100/100
15%
Value26.9 s
0/100
10%
198 ms
337 ms
435 ms
413 ms
616 ms
Our browser made a total of 26 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Parkgreenhouse.net, 46% (12 requests) were made to Files.us.gositebuilder.com and 23% (6 requests) were made to 55b558c7-resources.us.gositebuilder.com. The less responsive or slowest element that took the longest time to load (821 ms) relates to the external source 55b558c7-resources.us.gositebuilder.com.
Page size can be reduced by 159.1 kB (2%)
6.4 MB
6.2 MB
In fact, the total size of Parkgreenhouse.net main page is 6.4 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. 45% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 133.7 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 133.7 kB or 87% of the original size.
Potential reduce by 25.2 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. Parkgreenhouse images are well optimized though.
Potential reduce by 66 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 211 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. Parkgreenhouse.net has all CSS files already compressed.
Number of requests can be reduced by 4 (22%)
18
14
The browser has sent 18 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 5 to 1 for JavaScripts and as a result speed up the page load time.
parkgreenhouse.net
198 ms
parkgreenhouse.net
337 ms
21125186-9f6b-4d66-b5b3-4af3870cd3f7.css
435 ms
translations.js
413 ms
published-v10-site-libs.js
616 ms
published-v8-site.js
821 ms
twig-widget-views-v2.js
424 ms
scroll-out.js
363 ms
css2
40 ms
33d7b776-771f-463e-9399-a03da15961a2.jpg
255 ms
764f3039-29e9-477b-a251-2149694f76a5.jpg
639 ms
b54d8ed7-f7b0-422f-a249-44ec1291fb29.jpg
535 ms
2e919bf5-aca5-478f-96b2-73c871d88042.jpg
465 ms
a792f2e5-8c31-45e1-9eb3-89618df1c003.jpg
542 ms
b02c0f7b-1709-4fbb-8ae4-9751788456e0.jpg
539 ms
10ba0e1c-be2d-4154-a8fe-fea63122a177.jpg
375 ms
4e7b23a6-af5c-4c11-9c8b-50a862119787.jpg
447 ms
970964bc-cefb-431f-a629-d44e769ec179.jpg
520 ms
48730594-a10c-4fc4-9dc3-e88ff68288d5.jpg
532 ms
88fffb6c-7518-43a9-a35a-6daa553d2414.jpg
586 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISWaA.ttf
18 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoUoOWaA.ttf
31 ms
FontAwesome.woff
64 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf
45 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf
44 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf
45 ms
parkgreenhouse.net accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
parkgreenhouse.net 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
parkgreenhouse.net SEO score
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 Parkgreenhouse.net 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 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: