Website review, no card needed
yourgreenhouses.com website review
Visit site (opens in a new tab)Reviewed 7 November 202641 issues · 94 checks
This review found 41 issues worth fixing on yourgreenhouses.com, 15 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
79C- #56,277 of 126,379 reviewed websitesbeats 50%
- #36,695 of 70,450 online storesbeats 42%
- #35,126 of 63,950 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 199 ms |
| May 23, 2026 | 227 ms |
| May 30, 2026 | 237 ms |
| Jun 6, 2026 | 246 ms |
| Jun 13, 2026 | 246 ms |
| Jun 20, 2026 | 229 ms |
| Jun 27, 2026 | 229 ms |
| Jul 4, 2026 | 220 ms |
| Jul 11, 2026 | 219 ms |
| Jul 18, 2026 | 213 ms |
| Jul 25, 2026 | 177 ms |
| Aug 1, 2026 | 161 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 130 ms |
| Aug 22, 2026 | 140 ms |
| Aug 29, 2026 | 146 ms |
| Sep 5, 2026 | 153 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 152 ms |
| Sep 26, 2026 | 146 ms |
| Oct 3, 2026 | 153 ms |
| Oct 10, 2026 | 164 ms |
| Oct 17, 2026 | 178 ms |
| Oct 24, 2026 | 188 ms |
| Oct 31, 2026 | 195 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.5 s
0.9 s
1.4 s
1.8 s
2.3 s
2.8 s
3.2 s
3.7 s
Speed
Reduce unused JavaScript
2.3 s · 841 KiBAbout 841 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, hsappstatic.net and Hubspot and others), adding 1.8 MB and 1.5 s of main-thread time.
Improve image delivery
700 ms · 924 KiB9 images could be 924 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
Use efficient cache lifetimes
750 ms · 318 KiB26 files are served with short cache lifetimes, so returning visitors download them again (318 KiB).
Reduce unused CSS
750 ms · 68 KiBAbout 68 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Google Tag Manager adds 563 ms
563 msGoogle Tag Manager costs a phone 563 ms of main-thread work and 735 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
450 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 436 ms. During a long task the page ignores taps.
hsappstatic.net adds 321 ms
321 mshsappstatic.net costs a phone 321 ms of main-thread work and 248 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Legacy JavaScript
150 ms · 63 KiBPolyfills for old browsers add 63 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Duplicated JavaScript
150 ms · 3 KiB3 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 22.5 s
22.5 sYour largest element takes 22.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A Nordwood greenhouse among hydrangeas, a family at the tab…”.
Time to Interactive: 26.9 s
26.9 sThe page becomes fully interactive after 26.9 s. Good is under 3.8 s.
Speed Index: 10.0 s
10.0 sVisually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 753 ms
753 msScripts block taps and scrolling for 753 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 751 ms
751 msReal visitors wait 751 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 199 ms to 195 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 39% faster for real visitors
-39%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.065
0.065The layout barely moves while loading (CLS 0.065, good is under 0.1).
Images and page weight
Page weight: 11.9 MB in 336 requests
11.9 MBYour homepage downloads 11.9 MB in 336 requests on a phone: media 6.3 MB (2), scripts 2.2 MB (119) and images 1.7 MB (35). Under 2 MB keeps phones on slow connections fast.
4 images far larger than shown
525 KiB4 images are downloaded at several times the size a phone draws them, for example new-nord-pdp-gallery-brown--1_e6712afb-d33b-4f17-9f12-8fa68a at 900 px wide, shown at 177 px. Resized copies would save about 525 KiB.
5 images in older formats
5 images (1.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 3.4 g of CO₂ per visit
3.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.36 g of CO₂e: 403.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
19 text elements with low contrast
19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (3 elements)
Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
25 links without text
25 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (7 elements)
Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 43 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“YourGreenhouses Inc - Reliable Greenhouse Manufac…” and “Black Friday Early Access: up to 50% off + limite…”). One clear main headline is easier for people and search engines.
Meta description is long (195 characters)
Your meta description is 195 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
79 internal links, 7 external
The homepage links to 79 pages on yourgreenhouses.com and 7 external pages.
5 checks passed
Title: 54 characters
Your title is a healthy 54 characters: “Yourgreenhouses.com - Reliable Greenhouse Manufacturer”.
Canonical URL set
The canonical URL is https://yourgreenhouses.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://yourgreenhouses.com/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (869 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://yourgreenhouses.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://yourgreenhouses.com/collections/garden-house has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://yourgreenhouses.com/products/nordwood-greenhouse, https://yourgreenhouses.com/products/nordwood-arrow-greenhouse and https://yourgreenhouses.com/products/nordwood-classic-greenhouse use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://yourgreenhouses.com/collections/greenhouse-accessories and https://yourgreenhouses.com/pages/review have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343225927&tm=gtm002&Ver=2&mid=1be7338a-05ad-43ab-9a50-75bf8762fc1c&bo=1&sid=638fd5a0dac511f18c4df3c4b95355ee&vid=638fd3a0dac511f1b1c0eb643ccd0426&vids=1&msclkid=N&pi=9.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
35 of 35 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Only about 164 words
The homepage has only about 164 words of visible text; thin pages give Google and first-time buyers little to go on.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP EARLY ACCESS”.
22 calls to action
The homepage has 22 calls to action, for example “Shop all”, “Contact” and “Shop”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks and 4 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
43 cookies set on arrival
43Opening the homepage sets 43 cookies, 2 of them by other companies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
53 other companies contacted
Loading the homepage contacts 53 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at yourgreenhouses.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Geo Pro Geolocation · Intelligems A B Testing · Klaviyo Email Marketing Sms · Aimerce First Party Pixel · Microsoft Clarity · Tagfly Tag Manager · Pc8b463l8 Opensend · Uppromote Affiliate · Easylocation · Applovin Shop Integration · Air Reviews · Affliate By Secomapp · avada.io · richpanel.com · cloudfront.net · hubapi.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on yourgreenhouses.com, including 17 speed issues, 4 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.