Website review, no card needed
rhinogreenhouses.com website review
Visit site (opens in a new tab)Reviewed 8 November 202642 issues · 97 checks
This review found 42 issues worth fixing on rhinogreenhouses.com, 19 of them high impact, across 97 checks. The most urgent: improve image delivery. 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
77C- #69,951 of 126,317 reviewed websitesbeats 39%
- #44,915 of 70,430 online storesbeats 31%
- #42,668 of 63,934 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.2 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.5 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 149 ms |
| May 23, 2026 | 146 ms |
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 161 ms |
| Jun 13, 2026 | 164 ms |
| Jun 20, 2026 | 171 ms |
| Jun 27, 2026 | 161 ms |
| Jul 4, 2026 | 142 ms |
| Jul 11, 2026 | 138 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 139 ms |
| Aug 1, 2026 | 145 ms |
| Aug 8, 2026 | 154 ms |
| Aug 15, 2026 | 161 ms |
| Aug 22, 2026 | 163 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 153 ms |
| Sep 26, 2026 | 158 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 164 ms |
| Oct 17, 2026 | 162 ms |
| Oct 24, 2026 | 161 ms |
| Oct 31, 2026 | 171 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.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.1 s
4.7 s
Speed
Improve image delivery
1.1 s · 1.3 MB11 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Reduce unused JavaScript
1.4 s · 944 KiBAbout 944 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Render-blocking requests
1.8 s25 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,998 HTML elements
The page has 5,998 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.9 s
A phone's processor spends 4.9 s on main-thread work while loading, 2.4 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, Hotjar and Shopify and others), adding 2.3 MB and 1.5 s of main-thread time.
Use efficient cache lifetimes
550 ms · 456 KiB51 files are served with short cache lifetimes, so returning visitors download them again (456 KiB).
Google Tag Manager adds 571 ms
571 msGoogle Tag Manager costs a phone 571 ms of main-thread work and 887 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.
Hotjar adds 375 ms
375 msHotjar costs a phone 375 ms of main-thread work and 65 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.
Shopify adds 184 ms
184 msShopify costs a phone 184 ms of main-thread work and 430 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.
Klaviyo adds 113 ms
113 msKlaviyo costs a phone 113 ms of main-thread work and 309 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.
Feefo.com adds 71 ms
71 msFeefo.com costs a phone 71 ms of main-thread work and 359 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 221 ms. During a long task the page ignores taps.
Legacy JavaScript
50 ms · 35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
38 KiBAbout 38 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
29 KiB29 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
15 KiB15 KiB JavaScript is shipped twice across bundles.
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.
1 checks passed
Server response: 73 ms
73 msYour server sent the HTML in 73 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 22.3 s
22.3 sYour largest element takes 22.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A rhino Greenhouse in a rural garden”.
Time to Interactive: 33.5 s
33.5 sThe page becomes fully interactive after 33.5 s. Good is under 3.8 s.
Speed Index: 11.0 s
11.0 sVisually, the page fills in at 11.0 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.9 s
2.9 sReal visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 823 ms
823 msReal visitors wait 823 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 488 ms
488 msScripts block taps and scrolling for 488 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 149 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 145 ms
145 msReal visitors wait 145 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.3 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 11.2 MB in 448 requests
11.2 MBYour homepage downloads 11.2 MB in 448 requests on a phone: media 3.8 MB (1), images 2.6 MB (31) and scripts 2.4 MB (168). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
61 KiB1 image is downloaded at several times the size a phone draws it, for example rhino-gh-logo.png at 1,657 px wide, shown at 100 px. Resized copies would save about 61 KiB.
5 images in older formats
5 images (394 KiB) 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.2 g of CO₂ per visit
3.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.18 g of CO₂e: 381.4 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
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Elements must only use permitted ARIA attributes (19 elements)
Elements must only use permitted ARIA attributes: 19 elements on the page fail this check, rated serious by axe-core.
17 tap targets too small
17 tap targets are too small or too close together to hit reliably with a finger.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
55 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 64 WCAG 2.2 A/AA and best-practice rules on the phone render: 55 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
186 internal links, 5 external
The homepage links to 186 pages on rhinogreenhouses.com and 5 external pages.
8 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Spacious, strong and beautiful greenhouses and greenhouse kits sale, ideal for any garden. Free delivery and up to a 25…”.
One H1 headline
Your main headline reads: “Rhino Greenhouses Now Available in The US”.
Title: 60 characters
Your title is a healthy 60 characters: “Greenhouses For Sale - Rhino Greenhouses Now Available In US”.
Canonical URL set
The canonical URL is https://www.rhinogreenhouses.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://www.rhinogreenhouses.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.rhinogreenhouses.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
3 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,215 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 58 found) and read each the way a search engine does.
7 checks passed
Linked pages load
5 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 5 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 5 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=5712486&tm=gtm002&Ver=2&mid=d42da188-3756-4f38-b2ea-4ef073e23304&bo=3&sid=d0d3d160db5b11f19cb6254460336e2b&vid=d0d40830db5b11f18aac81275e522569&vids=0&msclkid=N&pi=918.
14 small tap targets
14 of 38 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
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.
A 11-field form
Your longest form asks for 11 fields (7 required). Every extra field lowers completion.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 709 words of copy
The homepage carries about 709 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “shop our sale”.
19 calls to action
The homepage has 19 calls to action, for example “Request a Brochure”, “Where To Buy” and “download brochure”.
Social proof on the page
Social proof on the homepage: 6 testimonial or review blocks, 2 customer or partner logos, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Direct contact links
Visitors can reach you directly: 2 phone links 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.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo 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.
26 cookies set on arrival
26Opening the homepage sets 26 cookies, 1 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.
50 other companies contacted
Loading the homepage contacts 50 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 rhinogreenhouses.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on rhinogreenhouses.com, including 23 speed issues, 1 SEO issue 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.