2.6 sec in total
115 ms
1.5 sec
1 sec
Welcome to greenhouseemporium.com homepage info - get ready to check Greenhouse Emporium best content for United States right away, or after learning these important things about greenhouseemporium.com
Turning Your Green Dreams Into Living Greens -This is our goal at Greenhouse Emporium. We are here to create a thriving garden with you!
Visit greenhouseemporium.comWe analyzed Greenhouseemporium.com page load time and found that the first response time was 115 ms and then it took 2.5 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.
greenhouseemporium.com performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value20.2 s
0/100
25%
Value12.1 s
3/100
10%
Value2,270 ms
6/100
30%
Value0.003
100/100
15%
Value20.1 s
2/100
10%
115 ms
20 ms
33 ms
38 ms
52 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 85% of them (109 requests) were addressed to the original Greenhouseemporium.com, 2% (3 requests) were made to Google.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (615 ms) relates to the external source Shopperapproved.com.
Page size can be reduced by 735.8 kB (46%)
1.6 MB
866.3 kB
In fact, the total size of Greenhouseemporium.com main page is 1.6 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. 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. HTML takes 872.0 kB which makes up the majority of the site volume.
Potential reduce by 734.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 734.7 kB or 84% of the original size.
Potential reduce by 420 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. Greenhouse Emporium images are well optimized though.
Potential reduce by 750 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.
Number of requests can be reduced by 80 (87%)
92
12
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greenhouse Emporium. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 78 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
greenhouseemporium.com
115 ms
dashicons.min.css
20 ms
custom-frontend.min.css
33 ms
custom-pro-frontend.min.css
38 ms
google-fonts-1-mod-39v0h.css
52 ms
greenhouse-emporium.js
288 ms
jquery.min.js
37 ms
jquery-migrate.min.js
25 ms
jquery.blockUI.min.js
23 ms
js.cookie.min.js
66 ms
woocommerce.min.js
66 ms
gtm4wp-woocommerce-enhanced.js
67 ms
lazysizes.min.js
122 ms
core.min.js
142 ms
datepicker.min.js
123 ms
conditions.js
124 ms
select-box.js
122 ms
single-product.min.js
150 ms
accounting.min.js
147 ms
pewc.js
149 ms
front-end-pro.js
149 ms
sourcebuster.min.js
148 ms
order-attribution.min.js
153 ms
wp-polyfill-inert.min.js
155 ms
regenerator-runtime.min.js
154 ms
wp-polyfill.min.js
153 ms
react.min.js
172 ms
hooks.min.js
175 ms
deprecated.min.js
176 ms
dom.min.js
180 ms
react-dom.min.js
180 ms
escape-html.min.js
180 ms
element.min.js
179 ms
is-shallow-equal.min.js
182 ms
i18n.min.js
182 ms
keycodes.min.js
277 ms
priority-queue.min.js
277 ms
compose.min.js
277 ms
private-apis.min.js
270 ms
redux-routine.min.js
262 ms
data.min.js
262 ms
lodash.min.js
271 ms
wc-blocks-registry.js
268 ms
url.min.js
268 ms
api-fetch.min.js
239 ms
wc-settings.js
239 ms
gtm.js
250 ms
universal.js
324 ms
27887.js
615 ms
certificate.js
300 ms
data-controls.min.js
179 ms
html-entities.min.js
227 ms
notices.min.js
226 ms
wc-blocks-middleware.js
227 ms
wc-blocks-data.js
226 ms
dom-ready.min.js
225 ms
a11y.min.js
202 ms
primitives.min.js
241 ms
warning.min.js
239 ms
blocks-components.js
242 ms
blocks-checkout.js
240 ms
order-attribution-blocks.min.js
234 ms
frontend.js
235 ms
main.min.js
243 ms
search.min.js
224 ms
imagesloaded.min.js
222 ms
jquery.smartmenus.min.js
222 ms
webpack-pro.runtime.min.js
223 ms
webpack.runtime.min.js
224 ms
frontend-modules.min.js
224 ms
frontend.min.js
221 ms
waypoints.min.js
219 ms
frontend.min.js
220 ms
elements-handlers.min.js
224 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
270 ms
KFOmCnqEu92Fr1Mu7GxMKTU1Kvnz.woff
225 ms
KFOmCnqEu92Fr1Mu7WxMKTU1Kvnz.woff
132 ms
KFOmCnqEu92Fr1Mu4WxMKTU1Kvnz.woff
223 ms
KFOmCnqEu92Fr1Mu7mxMKTU1Kvnz.woff
177 ms
KFOmCnqEu92Fr1Mu5mxMKTU1Kvnz.woff
177 ms
KFOmCnqEu92Fr1Mu72xMKTU1Kvnz.woff
177 ms
KFOlCnqEu92Fr1MmSU5fBBc-AMP6lQ.woff
205 ms
KFOlCnqEu92Fr1MmSU5fChc-AMP6lbBP.woff
368 ms
KFOlCnqEu92Fr1MmSU5fCxc-AMP6lbBP.woff
366 ms
KFOlCnqEu92Fr1MmSU5fBxc-AMP6lbBP.woff
355 ms
KFOlCnqEu92Fr1MmSU5fCBc-AMP6lbBP.woff
355 ms
KFOlCnqEu92Fr1MmSU5fABc-AMP6lbBP.woff
381 ms
KFOlCnqEu92Fr1MmSU5fCRc-AMP6lbBP.woff
347 ms
fa-solid-900.woff
353 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5XpjLdSL57k.woff
351 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBA5XpjLdSL57k24Q.woff
350 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBB5XpjLdSL57k24Q.woff
485 ms
js
195 ms
290 ms
analytics.js
316 ms
loader.js
317 ms
bat.js
315 ms
fbevents.js
314 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBN5XpjLdSL57k24Q.woff
314 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBC5XpjLdSL57k24Q.woff
445 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBK5XpjLdSL57k24Q.woff
441 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBD5XpjLdSL57k24Q.woff
443 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5XpjLdSL57k.woff
419 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBA5XpjLdSL57k24Q.woff
439 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBB5XpjLdSL57k24Q.woff
482 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBN5XpjLdSL57k24Q.woff
480 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBC5XpjLdSL57k24Q.woff
554 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBK5XpjLdSL57k24Q.woff
479 ms
ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBD5XpjLdSL57k24Q.woff
553 ms
1Ptgg87LROyAm3Kz-CkCSKlv.woff
475 ms
1Ptgg87LROyAm3K9-CkCSKlvPfE.woff
477 ms
1Ptgg87LROyAm3K8-CkCSKlvPfE.woff
476 ms
eicons.woff
477 ms
fa-brands-400.woff
474 ms
GHE_logo-new-470.png
471 ms
GrowMax_super_grow_800_main-300x225.jpg
471 ms
Greenhouse_emporium_home_page-about.jpg
447 ms
Greenhouse_emporium_faq.jpg
431 ms
Greenhouse_emporium_reviews.jpg
431 ms
Greenhouse-emporium-home-page-4.jpg
533 ms
211 ms
collect
115 ms
call-tracking_7.js
113 ms
73005680.js
72 ms
collect
111 ms
73005680
87 ms
ga-audiences
14 ms
wcm
19 ms
greenhouseemporium.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.
greenhouseemporium.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
greenhouseemporium.com 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 Greenhouseemporium.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 Greenhouseemporium.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.
greenhouseemporium.com
Open Graph data is detected on the main page of Greenhouse Emporium. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: