Website review, no card needed
yuhuanpo.com website review
Visit site (opens in a new tab)Reviewed 16 November 202631 issues · 74 checks
This review found 31 issues worth fixing on yuhuanpo.com, 10 of them high impact, across 74 checks. The most urgent: use efficient cache lifetimes. 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
One score from every part of this review. How it works
How it loaded on a phone
1.9 s
3.9 s
5.8 s
7.7 s
9.7 s
11.6 s
13.5 s
15.5 s
Speed
Use efficient cache lifetimes
4.3 s · 1.7 MB69 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Improve image delivery
3.0 s · 752 KiB7 images could be 752 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Main-thread work: 11.1 s
A phone's processor spends 11.1 s on main-thread work while loading, 5.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
8 third-party services on the page
8 third-party services load with your homepage (Clarity, reamaze.com and Attentive and others), adding 1.7 MB and 1.3 s of main-thread time.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 641 KiBAbout 641 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Clarity adds 759 ms
759 msClarity costs a phone 759 ms of main-thread work and 30 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 · 101 KiBAbout 101 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.
Font display
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
2,462 HTML elements
The page has 2,462 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
reamaze.com adds 144 ms
144 msreamaze.com costs a phone 144 ms of main-thread work and 318 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.
Attentive adds 107 ms
107 msAttentive costs a phone 107 ms of main-thread work and 496 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.
rebuyengine.com adds 97 ms
97 msrebuyengine.com costs a phone 97 ms of main-thread work and 331 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.
Legacy JavaScript
47 KiBPolyfills for old browsers add 47 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.
1 checks passed
Server response: 241 ms
241 msYour server sent the HTML in 241 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 21.7 s
21.7 sThe page becomes fully interactive after 21.7 s. Good is under 3.8 s.
Largest Contentful Paint: 8.3 s
8.3 sYour largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A split promotional banner: on the left, a smiling couple t…”.
Speed Index: 8.9 s
8.9 sVisually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 196 ms
196 msScripts block the page for only 196 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.7 MB in 332 requests
4.7 MBYour homepage downloads 4.7 MB in 332 requests on a phone: scripts 1.8 MB (103), images 1.3 MB (50) and other files 1.1 MB (148). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (256 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.
2 images below the first screen load straight away
2 images further down the page (183 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.33 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.33 g of CO₂e: 160.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 44 images in the HTML carry an alt attribute.
17 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 17 WCAG 2.2 A/AA and best-practice rules on the phone render: 17 passed and 0 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (BreadcrumbList, Organization and WebSite) but with 2 problems, for example “WebSite: potentialAction.target is not an absolute URL ("https://yuhuanpo.com/search?q={search_term_string}")”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
272 internal links, 5 external
The homepage links to 272 pages on yuhuanpo.com and 5 external pages.
7 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Heading out? Don’t forget your hat! Sunday Afternoons has been making hats for over 25 years for everyone and everythin…”.
One H1 headline
Your main headline reads: “Sunday Afternoons”.
Title: 46 characters
Your title is a healthy 46 characters: “Sun Protection Hat Experts | Sunday Afternoons”.
Canonical URL set
The canonical URL is https://yuhuanpo.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://yuhuanpo.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (926 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://yuhuanpo.com/llms.txt (4 KiB, 5 links), a plain-text guide to the site for AI tools.
Other pages
11 pages share a title
https://yuhuanpo.com/collections/womens-hats, https://yuhuanpo.com/collections/womens-wide-brim-hats, https://yuhuanpo.com/collections/womens-bucket-hats, https://yuhuanpo.com/collections/womens-sun-visors, https://yuhuanpo.com/collections/womens-caps and https://yuhuanpo.com/collections/womens-trucker-hats and 5 others all use the title “Verifying your connection...”. Search engines can't tell which page to show for a search, so each competes with the others.
11 pages without a meta description
https://yuhuanpo.com/collections/womens-hats, https://yuhuanpo.com/collections/womens-wide-brim-hats, https://yuhuanpo.com/collections/womens-bucket-hats, https://yuhuanpo.com/collections/womens-sun-visors, https://yuhuanpo.com/collections/womens-caps and https://yuhuanpo.com/collections/womens-trucker-hats and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages with very little text
https://yuhuanpo.com/collections/womens-hats, https://yuhuanpo.com/collections/womens-wide-brim-hats, https://yuhuanpo.com/collections/womens-bucket-hats, https://yuhuanpo.com/collections/womens-sun-visors, https://yuhuanpo.com/collections/womens-caps and https://yuhuanpo.com/collections/womens-trucker-hats and 5 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 97 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.
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 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=26355503&Ver=2&mid=ffa677c6-7179-42f2-956f-fd0d429964ad&bo=1&sid=eb92d5d0e21211f1aed1cfcfb8db3570&vid=eb931120e21211f1bed907f8f4530815&vids=1&msclkid=N&pi=918639831&lg.
19 small tap targets
19 of 41 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to find a valid digest in the 'integrity' attribute for resource 'https://yuhuanpo.com/cdn/shopifycloud/storefro…”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 9 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
About 526 words of copy
The homepage carries about 526 words of visible text.
4 checks passed
24 calls to action
The homepage has 24 calls to action, for example “Shop All Styles”, “Shop All Weather” and “Shop All Activities”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity and Cloudflare Web Analytics.
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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Klaviyo, Microsoft Ads and Microsoft Clarity (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.
20 cookies set on arrival
20Opening the homepage sets 20 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.
38 other companies contacted
Loading the homepage contacts 38 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 yuhuanpo.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · Attentive · Revenue Flare · Klaviyo Email Marketing Sms · Simprosys Google Shopping Feed · Judge Me Reviews · Reamaze Live Chat Helpdesk · Region Restrictions · attn.tv · trafficmanager.net · bazaarvoice.com · rebuyengine.com · shgcdn3.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
- Microsoft Clarity
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on yuhuanpo.com, including 18 speed issues, 2 SEO issues and 3 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.