Website review, no card needed
homeal.co.jp website review
Visit site (opens in a new tab)Reviewed 7 November 202647 issues · 89 checks
This review found 47 issues worth fixing on homeal.co.jp, 16 of them high impact, across 89 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
73C- #93,228 of 126,442 reviewed websitesbeats 23%
- #57,597 of 70,471 online storesbeats 15%
- #53,802 of 63,972 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.9 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 136 ms |
| May 23, 2026 | 135 ms |
| May 30, 2026 | 134 ms |
| Jun 6, 2026 | 132 ms |
| Jun 13, 2026 | 134 ms |
| Jun 20, 2026 | 126 ms |
| Jun 27, 2026 | 128 ms |
| Jul 4, 2026 | 124 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 118 ms |
| Jul 25, 2026 | 117 ms |
| Aug 1, 2026 | 116 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 111 ms |
| Aug 22, 2026 | 108 ms |
| Aug 29, 2026 | 107 ms |
| Sep 5, 2026 | 106 ms |
| Sep 12, 2026 | 113 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 125 ms |
| Oct 10, 2026 | 117 ms |
| Oct 17, 2026 | 117 ms |
| Oct 24, 2026 | 121 ms |
| Oct 31, 2026 | 118 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
Speed
Reduce unused JavaScript
4.5 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.
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.
Main-thread work: 5.2 s
A phone's processor spends 5.2 s on main-thread work while loading, 1.9 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 (cloudfront.net, channel.io and firebaseapp.com and others), adding 2.1 MB and 1.5 s of main-thread time.
Improve image delivery
600 ms · 731 KiB29 images could be 731 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Render-blocking requests
900 ms10 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Reduce unused CSS
600 ms · 107 KiBAbout 107 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Use efficient cache lifetimes
500 ms · 146 KiB34 files are served with short cache lifetimes, so returning visitors download them again (146 KiB).
cloudfront.net adds 513 ms
513 mscloudfront.net costs a phone 513 ms of main-thread work and 701 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.
channel.io adds 436 ms
436 mschannel.io costs a phone 436 ms of main-thread work and 329 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
350 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 268 ms. During a long task the page ignores taps.
Shopify adds 114 ms
114 msShopify costs a phone 114 ms of main-thread work and 367 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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: 10 ms
10 msYour server sent the HTML in 10 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: 20.7 s
20.7 sYour largest element takes 20.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “家族向け冷凍宅配サービス”.
Time to Interactive: 24.1 s
24.1 sThe page becomes fully interactive after 24.1 s. Good is under 3.8 s.
Total Blocking Time: 959 ms
959 msScripts block taps and scrolling for 959 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
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.8 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 93 ms
93 msReal visitors wait 93 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user TTFB: 308 ms
308 msReal visitors wait 308 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 136 ms to 118 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 286 requests
4.9 MBYour homepage downloads 4.9 MB in 286 requests on a phone: scripts 2.3 MB (110), images 1.5 MB (51) and other files 767 KiB (103). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
89 KiB1 image is downloaded at several times the size a phone draws it, for example menu-diagnosis-image_1920x.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 89 KiB.
1 image below the first screen load straight away
1 image further down the page (142 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.39 g of CO₂e: 166.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
ARIA attributes must conform to valid values (2 elements)
ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
29 text elements with low contrast
29 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
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 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Alternative text of images should not be repeated as text (8 elements)
Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.
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 60 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 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
48 internal links, 10 external
The homepage links to 48 pages on homeal.co.jp and 10 external pages.
7 checks passed
Meta description: 98 characters
Your meta description is 98 characters: “離乳食後の1歳頃から大人まで。管理栄養士監修、保存料・合成着色料不使用の冷凍ごはんをご自宅へ。常時80種類以上、レンジ3分で完成。初回1,000円OFF+3回まで送料無料で総額3,850円おトク。”.
One H1 headline
Your main headline reads: “てのひらごはん ホーミール”.
Title: 64 characters
Your title is a healthy 64 characters: “幼児食の冷凍宅配 homeal(ホーミール)公式|1歳頃から家族みんなで – homeal ホーミール 家族向け冷凍宅配サービス”.
Canonical URL set
The canonical URL is https://homeal.co.jp/.
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://homeal.co.jp/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
2 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.
llms.txt published
The site publishes https://homeal.co.jp/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://homeal.co.jp/fb and https://homeal.co.jp/tw, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages without a meta description
https://homeal.co.jp/pages/menu-diagnosis and https://homeal.co.jp/blogs/magazine have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://homeal.co.jp/pages/custom-menu and https://homeal.co.jp/pages/menu-diagnosis have no <h1> headline, so visitors and search engines get no clear main topic.
10 pages with very little text
https://homeal.co.jp/collections/set-product-lineup, https://homeal.co.jp/blogs/magazine/vegetable-snack-from-age-1, https://homeal.co.jp/pages/customer-reviews, https://homeal.co.jp/products/gungun-udon-1set, https://homeal.co.jp/products/meatballs-with-liver-in-tomato-sauce-mini and https://homeal.co.jp/products/keema-curry-with-shredded-vegetables-mini and 4 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.
4 pages slow to respond
https://homeal.co.jp/pages/customer-reviews, https://homeal.co.jp/products/meatballs-with-liver-in-tomato-sauce-mini, https://homeal.co.jp/products/hokkaido-pumpkin-and-carrot-stew-mini and https://homeal.co.jp/products/croissant-3 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.
4 checks passed
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 13 pages that loaded have a <title>.
Best practices
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.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “isActive is not defined”.
2 checks passed
Tap targets are thumb-sized
13 of 16 tappable elements near the top are at least 24 px.
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
Only about 90 words
The homepage has only about 90 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag (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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
37 other companies contacted
Loading the homepage contacts 37 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 homeal.co.jp, 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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Anygift · Pagefly Ai Page Builder · Commchathomeal · Judge Me Reviews · Revenuehunt · Subscription Test · covet.pics · channel.io · mixlogue.jp · firebaseapp.com · letters.co.jp · omnisnippet1.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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on homeal.co.jp, including 21 speed issues, 1 SEO issue and 5 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.