Website review, no card needed
hansohome.com website review
Visit site (opens in a new tab)Reviewed 8 November 202637 issues · 88 checks
This review found 37 issues worth fixing on hansohome.com, 14 of them high impact, across 88 checks. The most urgent: youTube adds 8.5 s. 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
75C- #81,115 of 123,879 reviewed websitesbeats 30%
- #51,498 of 69,702 online storesbeats 22%
- #48,603 of 63,410 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 4.1 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 995 ms |
| Jul 4, 2026 | 783 ms |
| Jul 11, 2026 | 654 ms |
| Jul 18, 2026 | 688 ms |
| Jul 25, 2026 | 772 ms |
| Aug 1, 2026 | 816 ms |
| Aug 8, 2026 | 857 ms |
| Aug 15, 2026 | 890 ms |
| Aug 22, 2026 | 877 ms |
| Aug 29, 2026 | 860 ms |
| Sep 5, 2026 | 854 ms |
| Sep 12, 2026 | 821 ms |
| Sep 19, 2026 | 849 ms |
| Sep 26, 2026 | 880 ms |
| Oct 3, 2026 | 892 ms |
| Oct 10, 2026 | 919 ms |
| Oct 17, 2026 | 927 ms |
| Oct 24, 2026 | 922 ms |
| Oct 31, 2026 | 943 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
2.9 s
5.8 s
8.7 s
11.6 s
14.4 s
17.3 s
20.2 s
23.1 s
Speed
YouTube adds 8.5 s
8.5 sYouTube costs a phone 8.5 s of main-thread work and 16.3 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 28.3 s
A phone's processor spends 28.3 s on main-thread work while loading, 13.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
1.6 s · 443 KiB11 images could be 443 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Mobile performance score: 25
25/100Your mobile performance score is 25. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and CallRail and others), adding 18.8 MB and 10.5 s of main-thread time.
Reduce unused JavaScript
300 ms · 9.4 MBAbout 9.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
100 ms · 753 KiB56 files are served with short cache lifetimes, so returning visitors download them again (753 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 852 ms. During a long task the page ignores taps.
Google Tag Manager adds 709 ms
709 msGoogle Tag Manager costs a phone 709 ms of main-thread work and 877 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.
Reduce unused CSS
300 ms · 187 KiBAbout 187 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
CallRail adds 379 ms
379 msCallRail costs a phone 379 ms of main-thread work and 21 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.
2,686 HTML elements
The page has 2,686 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 194 ms
194 msKlaviyo costs a phone 194 ms of main-thread work and 324 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.
Other Google APIs/SDKs adds 176 ms
176 msOther Google APIs/SDKs costs a phone 176 ms of main-thread work and 433 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
49 KiBPolyfills for old browsers add 49 KiB JavaScript that modern phones do not need.
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 JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 24 ms
24 msYour server sent the HTML in 24 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: 24.4 s
24.4 sYour largest element takes 24.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “#1 America's Most Popular Pergola Brand.”.
Speed Index: 50.5 s
50.5 sVisually, the page fills in at 50.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 5.1 s
5.1 sScripts block taps and scrolling for 5.1 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 139.1 s
139.1 sThe page becomes fully interactive after 139.1 s. Good is under 3.8 s.
First Contentful Paint: 6.3 s
6.3 sThe first text or image appears after 6.3 s on a phone. Good is under 1.8 s.
Real-user INP: 497 ms
497 msReal visitors wait 497 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 711 ms
711 msReal visitors wait 711 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 1.1 s to 943 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 27.7 MB in 662 requests
27.7 MBYour homepage downloads 27.7 MB in 662 requests on a phone: scripts 17.5 MB (237), images 6.1 MB (116) and HTML 1.3 MB (21). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
find-best-grid1.webp weighs 1.8 MB. On a phone connection a single image that size takes seconds.
33 images in older formats
33 images (7.6 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.
1 image far larger than shown
117 KiB1 image is downloaded at several times the size a phone draws it, for example final-img-avatar.png at 1,024 px wide, shown at 14 px. Resized copies would save about 117 KiB.
1 image below the first screen load straight away
1 image further down the page (148 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 7.8 g of CO₂ per visit
7.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.84 g of CO₂e: 940.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
27 tap targets too small
27 tap targets are too small or too close together to hit reliably with a finger.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 204 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
139 internal links, 20 external
The homepage links to 139 pages on hansohome.com and 20 external pages.
8 checks passed
Meta description: 122 characters
Your meta description is 122 characters: “Get premium pergola kits for your backyard or patio. Built to last 30+ years, with a 10-year warranty and 100-day retur…”.
One H1 headline
Your main headline reads: “#1 America's Most Popular Pergola Brand.”.
Title: 53 characters
Your title is a healthy 53 characters: “Hansø: Modern Aluminum Pergolas & Retractable Awnings”.
Canonical URL set
The canonical URL is https://hansohome.com/.
Structured data in place
Structured data found: 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://hansohome.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, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (33,764 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://hansohome.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://hansohome.com/collections/hanso-early-birds-offers-2026 and https://hansohome.com/collections/all-accessories have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://hansohome.com/collections/hanso-early-birds-offers-2026, https://hansohome.com/collections/sale, https://hansohome.com/products/hanso-apex-pergola and https://hansohome.com/products/electric-retractable-awning 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 39 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
8 small tap targets
8 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are 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”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
About 31,854 words of copy
The homepage carries about 31,854 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Early Bird Offers”.
37 calls to action
The homepage has 37 calls to action, for example “Shop Now”, “Talk to a Specialist” and “Learn More About Pergolas”.
1 short form
A short form (0 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 285 testimonial or review blocks, 12 customer or partner logos, a star rating, 21 trust badges and “17,000+ Customers”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 5 phone links and 0 email links.
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
11 trackers load before any consent
11Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 6 mores (measured from a US location before any click). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
44 cookies set on arrival
44Opening the homepage sets 44 cookies, 4 of them by other companies (measured from a US location before any click).
71 other companies contacted
Loading the homepage contacts 71 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) loads with the page.
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 hansohome.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 19 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Cookiebot Cmp · Awin Affiliate Marketing · Judge Me Reviews · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Zigpoll Customer Surveys · Bm Country Blocker Ip Blocker · Cms Shopify · Boostymark Regionblock · Accessibly App · Intercom · Affirm · Countdown Timer · Freegifts · amazonaws.com · retention.com · archive-digger.com · cloudfront.net · bogos.io
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 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 37 issues on hansohome.com, including 21 speed issues and 2 SEO issues. 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.