Website review, no card needed
daylilyglobal.com website review
Visit site (opens in a new tab)Reviewed 20 November 202642 issues · 91 checks
This review found 42 issues worth fixing on daylilyglobal.com, 16 of them high impact, across 91 checks. The most urgent: avoid multiple page redirects. 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.8 s
3.7 s
5.5 s
7.3 s
9.2 s
11.0 s
12.9 s
14.7 s
Speed
Avoid multiple page redirects
3.8 sThe page goes through 2 redirects before it starts loading, costing about 3.8 s. Link and advertise the final URL directly.
Reduce unused JavaScript
1.5 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Main-thread work: 16.4 s
A phone's processor spends 16.4 s on main-thread work while loading, 6.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
1.3 s · 231 KiBAbout 231 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.3 s faster on a phone.
YouTube adds 1.2 s
1.2 sYouTube costs a phone 1.2 s of main-thread work and 1.0 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.
Render-blocking requests
1.3 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Mobile performance score: 32
32/100Your mobile performance score is 32. 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, daylily.com.tw and Google Tag Manager and others), adding 8.9 MB and 4.4 s of main-thread time.
daylily.com.tw adds 948 ms
948 msdaylily.com.tw costs a phone 948 ms of main-thread work and 1.6 MB 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.
Use efficient cache lifetimes
500 ms · 345 KiB25 files are served with short cache lifetimes, so returning visitors download them again (345 KiB).
Google Tag Manager adds 776 ms
776 msGoogle Tag Manager costs a phone 776 ms of main-thread work and 455 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.
Improve image delivery
450 ms · 164 KiB5 images could be 164 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 482 ms. During a long task the page ignores taps.
pages.dev adds 405 ms
405 mspages.dev costs a phone 405 ms of main-thread work and 363 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.
pop-convert.com adds 379 ms
379 mspop-convert.com costs a phone 379 ms of main-thread work and 162 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,621 HTML elements
The page has 2,621 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
120 ms · 6 KiB6 KiB could be saved by minifying CSS.
Legacy JavaScript
100 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Document request latency
100 msThe HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 27.7 s
27.7 sYour largest element takes 27.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 20.1 s
20.1 sVisually, the page fills in at 20.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 70.5 s
70.5 sThe page becomes fully interactive after 70.5 s. Good is under 3.8 s.
Total Blocking Time: 4.3 s
4.3 sScripts block taps and scrolling for 4.3 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
7 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: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 128 ms
128 msReal visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 527 ms
527 msReal visitors wait 527 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.049
0.049The layout barely moves while loading (CLS 0.049, good is under 0.1).
Images and page weight
Page weight: 12.3 MB in 343 requests
12.3 MBYour homepage downloads 12.3 MB in 343 requests on a phone: other files 5.7 MB (75), scripts 2.8 MB (104) and fonts 2.7 MB (75). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
42 KiB1 image is downloaded at several times the size a phone draws it, for example 9.png at 564 px wide, shown at 80 px. Resized copies would save about 42 KiB.
About 3.5 g of CO₂ per visit
3.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.49 g of CO₂e: 418.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 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
Title is short (24 characters)
Your title is only 24 characters: “DAYLILY – DAYLILY GLOBAL”. Between 30 and 65 characters leaves room to say what you do and for whom.
10 links crawlers can't follow
10 links have no real href, so search engines can't follow them.
One H1 headline
Your <h1> is empty.
26 internal links, 13 external
The homepage links to 26 pages on daylilyglobal.com and 13 external pages.
6 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Better health and wellness through "Kampo" - traditional herbal formulas. Kampo lifestyle brand finally lands on US Sho…”.
Canonical URL set
The canonical URL is https://daylilyglobal.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://daylilyglobal.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 (481 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://daylilyglobal.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://daylilyglobal.com/products/asian-non-caffeine-herbal-tea-set and https://daylilyglobal.com/products/asian-non-caffeine-healthy-tea-set all use the title “Asian Non-Caffeine Herbal Tea Set – DAYLILY GLOBAL”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://daylilyglobal.com/blogs/news has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://daylilyglobal.com/products/asian-non-caffeine-herbal-tea-set and https://daylilyglobal.com/products/asian-non-caffeine-healthy-tea-set use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://daylilyglobal.com/products/asian-non-caffeine-healthy-tea-set, whose canonical is https://daylilyglobal.com/products/asian-non-caffeine-herbal-tea-set. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages with very little text
https://daylilyglobal.com/pages/wholesale and https://daylilyglobal.com/pages/contact 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.
3 pages slow to respond
https://daylilyglobal.com/blogs/news, https://daylilyglobal.com/products/asian-non-caffeine-healthy-tea-set and https://daylilyglobal.com/pages/wholesale took over 3 s to send their HTML from our server.
10 internal pages checked
We fetched 10 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 10 pages we checked loaded without an error.
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 10 pages that loaded have a <title>.
Best practices
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
17 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
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.
About 287 words of copy
The homepage carries about 287 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP LIST 店舗リスト SHOP LIST”.
2 calls to action
The homepage has 2 calls to action, for example “Shop Now” and “Contact us”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 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.
33 cookies set on arrival
33Opening the homepage sets 33 cookies, 11 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.
44 other companies contacted
Loading the homepage contacts 44 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 daylilyglobal.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- Framework
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on daylilyglobal.com, including 22 speed issues, 3 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.