Website review, no card needed
hasegawa.jp website review
Visit site (opens in a new tab)Reviewed 4 November 202638 issues · 85 checks
This review found 38 issues worth fixing on hasegawa.jp, 11 of them high impact, across 85 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
77C- #70,016 of 126,458 reviewed websitesbeats 39%
- #44,943 of 70,479 online storesbeats 31%
- #42,696 of 63,977 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 148 ms |
| May 23, 2026 | 147 ms |
| May 30, 2026 | 148 ms |
| Jun 6, 2026 | 148 ms |
| Jun 13, 2026 | 148 ms |
| Jun 20, 2026 | 148 ms |
| Jun 27, 2026 | 148 ms |
| Jul 4, 2026 | 147 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 142 ms |
| Aug 1, 2026 | 140 ms |
| Aug 8, 2026 | 140 ms |
| Aug 15, 2026 | 132 ms |
| Aug 22, 2026 | 133 ms |
| Aug 29, 2026 | 135 ms |
| Sep 5, 2026 | 135 ms |
| Sep 12, 2026 | 155 ms |
| Sep 19, 2026 | 155 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 150 ms |
| Oct 10, 2026 | 149 ms |
| Oct 17, 2026 | 150 ms |
| Oct 24, 2026 | 150 ms |
| Oct 31, 2026 | 146 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
3.0 s
6.0 s
9.0 s
12.0 s
15.0 s
18.0 s
21.0 s
24.0 s
Speed
Reduce unused JavaScript
2.4 s · 2.1 MBAbout 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Mobile performance score: 35
35/100Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.2 s
A phone's processor spends 9.2 s on main-thread work while loading, 5.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
750 ms · 3.3 MB75 files are served with short cache lifetimes, so returning visitors download them again (3.3 MB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, cloudfront.net and landinghub.cloud and others), adding 3.2 MB and 2.7 s of main-thread time.
Google Tag Manager adds 906 ms
906 msGoogle Tag Manager costs a phone 906 ms of main-thread work and 728 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.
Render-blocking requests
950 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
cloudfront.net adds 650 ms
650 mscloudfront.net costs a phone 650 ms of main-thread work and 1,015 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 626 ms. During a long task the page ignores taps.
Improve image delivery
300 ms · 251 KiB14 images could be 251 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused CSS
450 ms · 84 KiBAbout 84 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
worldshopping.jp adds 263 ms
263 msworldshopping.jp costs a phone 263 ms of main-thread work and 518 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.
landinghub.cloud adds 273 ms
273 mslandinghub.cloud costs a phone 273 ms of main-thread work and 16 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 138 ms
138 msShopify costs a phone 138 ms of main-thread work and 461 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
250 ms · 131 KiBPolyfills for old browsers add 131 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
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: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.1 s
10.1 sYour largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Join your hands together and live a life of gratitude. From…”.
Speed Index: 19.5 s
19.5 sVisually, the page fills in at 19.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 37.4 s
37.4 sThe page becomes fully interactive after 37.4 s. Good is under 3.8 s.
Total Blocking Time: 2.3 s
2.3 sScripts block taps and scrolling for 2.3 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 148 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 171 ms
171 msReal visitors wait 171 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.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 371 ms
371 msReal visitors wait 371 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.03
0.03The layout barely moves while loading (CLS 0.03, good is under 0.1).
Images and page weight
Page weight: 10.2 MB in 382 requests
10.2 MBYour homepage downloads 10.2 MB in 382 requests on a phone: scripts 4.4 MB (111), media 4.0 MB (2) and other files 815 KiB (164). Under 2 MB keeps phones on slow connections fast.
3 images below the first screen load straight away
3 images further down the page (202 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.9 g of CO₂ per visit
2.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.90 g of CO₂e: 347.9 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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
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.
8 form fields without a label
8 form fields have no label, so screen readers announce an empty box and autofill guesses.
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 86 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 2 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: missing name”.
201 internal links, 14 external
The homepage links to 201 pages on hasegawa.jp and 14 external pages.
7 checks passed
Meta description: 120 characters
Your meta description is 120 characters: “仏壇・位牌を探すなら、「おててのしわとしわをあわせて しあわせな~む~」でおなじみの、お仏壇のはせがわにお任せください。業界最多の店舗数で、おしゃれな仏壇・コンパクトなお仏壇を始め、モダンな位牌などを心を込めて提案いたします。通販にも対応。”.
One H1 headline
Your main headline reads: “手を合わせ、感謝する生活を。 仏壇・仏具の通販、お墓相談から終活・相続まで、 これからの暮らしを支えるパートナーに”.
Title: 32 characters
Your title is a healthy 32 characters: “お仏壇のはせがわ公式サイト | 仏壇、仏具、位牌、お墓、店舗情報”.
Canonical URL set
The canonical URL is https://www.hasegawa.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://www.hasegawa.jp/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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://www.hasegawa.jp/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without an H1
https://www.hasegawa.jp/pages/company, https://www.hasegawa.jp/pages/help, https://www.hasegawa.jp/pages/butsudan, https://www.hasegawa.jp/collections/butsudan, https://www.hasegawa.jp/collections/butsugu and https://www.hasegawa.jp/collections/ihai and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://www.hasegawa.jp/collections/butsugu, https://www.hasegawa.jp/collections/ihai, https://www.hasegawa.jp/collections/sennkou and https://www.hasegawa.jp/collections/cyouchin took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 67 found) and read each the way a search engine does.
6 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 a meta description
All 15 pages that loaded have a meta description.
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
7 small tap targets
7 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “%cLandingHub color:#FFF;background-color:#E83828;padding:2px;border-radius: 2px Failed to process accelerator.”.
6 distorted images
6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
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
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.
Only about 26 words
The homepage has only about 26 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.
3 checks passed
4 short forms
4 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.
27 cookies set on arrival
27Opening the homepage sets 27 cookies, 2 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.
54 other companies contacted
Loading the homepage contacts 54 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 hasegawa.jp, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Founded
- 1966
- Headquarters
- Fukuoka Prefecture
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on hasegawa.jp, including 19 speed issues, 1 SEO issue and 4 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.