Website review, no card needed

kuradashi.jp logo

kuradashi.jp website review

Visit site (opens in a new tab)Reviewed 4 November 202648 issues · 88 checks

This review found 48 issues worth fixing on kuradashi.jp, 15 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.6 s1.7 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.2 s
May 23, 20263.2 s
May 30, 20263.2 s
Jun 6, 20263.2 s
Jun 13, 20263.2 s
Jun 20, 20263.3 s
Jun 27, 20263.3 s
Jul 4, 20263.3 s
Jul 11, 20263.3 s
Jul 18, 20263.3 s
Jul 25, 20263.4 s
Aug 1, 20263.4 s
Aug 8, 20263.3 s
Aug 15, 20263.0 s
Aug 22, 20262.7 s
Aug 29, 20262.4 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
410 ms256 msMay 16Oct 31392 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026278 ms
May 23, 2026275 ms
May 30, 2026274 ms
Jun 6, 2026276 ms
Jun 13, 2026277 ms
Jun 20, 2026281 ms
Jun 27, 2026285 ms
Jul 4, 2026286 ms
Jul 11, 2026287 ms
Jul 18, 2026286 ms
Jul 25, 2026285 ms
Aug 1, 2026287 ms
Aug 8, 2026294 ms
Aug 15, 2026310 ms
Aug 22, 2026332 ms
Aug 29, 2026358 ms
Sep 5, 2026371 ms
Sep 12, 2026380 ms
Sep 19, 2026386 ms
Sep 26, 2026383 ms
Oct 3, 2026386 ms
Oct 10, 2026382 ms
Oct 17, 2026382 ms
Oct 24, 2026387 ms
Oct 31, 2026392 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

Full-page screenshot of kuradashi.jp (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kuradashi.jp at 1.3 s1.3 s
  2. kuradashi.jp at 2.6 s2.6 s
  3. kuradashi.jp at 3.9 s3.9 s
  4. kuradashi.jp at 5.1 s5.1 s
  5. kuradashi.jp at 6.4 s6.4 s
  6. kuradashi.jp at 7.7 s7.7 s
  7. kuradashi.jp at 9.0 s9.0 s
  8. kuradashi.jp at 10.3 s10.3 s

Speed

14 to fix37
  • Reduce unused JavaScript

    3.8 s · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.

  • Mobile performance score: 37

    37/100

    Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 9,305 HTML elements

    The page has 9,305 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Main-thread work: 9.3 s

    A phone's processor spends 9.3 s on main-thread work while loading, 4.2 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, Google Tag Manager and Clarity and others), adding 2.8 MB and 2.4 s of main-thread time.

  • Improve image delivery

    950 ms · 369 KiB

    8 images could be 369 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.

  • Use efficient cache lifetimes

    450 ms · 362 KiB

    25 files are served with short cache lifetimes, so returning visitors download them again (362 KiB).

  • Reduce unused CSS

    600 ms · 123 KiB

    About 123 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.

  • cloudfront.net adds 604 ms

    604 ms

    cloudfront.net costs a phone 604 ms of main-thread work and 1.1 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.

  • Google Tag Manager adds 553 ms

    553 ms

    Google Tag Manager costs a phone 553 ms of main-thread work and 537 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.

  • Clarity adds 411 ms

    411 ms

    Clarity costs a phone 411 ms of main-thread work and 28 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 322 ms

    322 ms

    channel.io costs a phone 322 ms of main-thread work and 312 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 303 ms. During a long task the page ignores taps.

  • Render-blocking requests

    300 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • Legacy JavaScript

    40 KiB

    Polyfills for old browsers add 40 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 CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 7 ms

    7 ms

    Your server sent the HTML in 7 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • 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: 26.3 s

    26.3 s

    Your largest element takes 26.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 21.7 s

    21.7 s

    Visually, the page fills in at 21.7 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 46.5 s

    46.5 s

    The page becomes fully interactive after 46.5 s. Good is under 3.8 s.

  • Total Blocking Time: 1.8 s

    1.8 s

    Scripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.

  • Real-user INP: 375 ms

    375 ms

    Real visitors wait 375 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 41% slower for real visitors

    +41%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 278 ms to 392 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

6 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

    Real visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 274 ms

    274 ms

    Real visitors wait 274 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 40% faster for real visitors

    -40%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.2 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.005

    0.005

    The layout barely moves while loading (CLS 0.005, good is under 0.1).

Images and page weight

2 to fix64
  • Page weight: 9.2 MB in 392 requests

    9.2 MB

    Your homepage downloads 9.2 MB in 392 requests on a phone: scripts 3.3 MB (119), images 2.6 MB (94) and fonts 2.2 MB (3). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    index_home-cooking-15off.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 2.6 g of CO₂ per visit

    2.60 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.60 g of CO₂e: 312.2 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

7 to fixGoogle 8192
  • 9 text elements with low contrast

    9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (14 elements)

    All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.

  • 11 links without text

    11 visible links have no text or label, so screen readers cannot say where they go.

  • Orphan list items

    Some list items are not inside a list.

  • button, link, and menuitem elements do not have accessible names.

    button, link, and menuitem elements do not have accessible names. (1 element).

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (110 elements).

2 checks passed
  • Every image has alt text

    All 57 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10090
  • Meta description is long (161 characters)

    Your meta description is 161 characters; Google truncates after about 160, so the end of your pitch is cut.

  • One H1 headline

    Your <h1> is empty.

  • 186 internal links, 16 external

    The homepage links to 186 pages on kuradashi.jp and 16 external pages.

6 checks passed
  • Title: 36 characters

    Your title is a healthy 36 characters: “おトクな買い物でフードロス・食品ロス削減|Kuradashi(クラダシ)”.

  • Canonical URL set

    The canonical URL is https://kuradashi.jp/.

  • 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://kuradashi.jp/sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, 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://kuradashi.jp/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix88
  • 6 pages without a meta description

    https://kuradashi.jp/pages/swym-wishlist, https://kuradashi.jp/pages/sweets-day, https://kuradashi.jp/pages/osake-wine-tokusenichi, https://kuradashi.jp/pages/food-drink-15off, https://kuradashi.jp/pages/howtouse and https://kuradashi.jp/pages/company have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://kuradashi.jp/collections/sweets, https://kuradashi.jp/collections/alcohol, https://kuradashi.jp/collections/drink, https://kuradashi.jp/collections/beauty, https://kuradashi.jp/collections/daily and https://kuradashi.jp/collections/all use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://kuradashi.jp/pages/sweets-day, https://kuradashi.jp/pages/osake-wine-tokusenichi, https://kuradashi.jp/pages/food-drink-15off, https://kuradashi.jp/pages/campaign-feature-index and https://kuradashi.jp/pages/about have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages with very little text

    https://kuradashi.jp/pages/swym-wishlist, https://kuradashi.jp/pages/sweets-day, https://kuradashi.jp/pages/osake-wine-tokusenichi, https://kuradashi.jp/pages/food-drink-15off, https://kuradashi.jp/collections/food and https://kuradashi.jp/collections/sweets and 9 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 87 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

4 to fixGoogle 7770
  • 3 broken images

    3 images failed to load on a phone, for example https://kuradashi.jp/.

  • 21 small tap targets

    21 of 54 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.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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.

  • Only about 27 words

    The homepage has only about 27 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
  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 8 trackers load before any consent

    8

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 3 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.

  • 30 cookies set on arrival

    30

    Opening the homepage sets 30 cookies (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.

  • 50 other companies contacted

    Loading the homepage contacts 50 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 kuradashi.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

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on kuradashi.jp, including 23 speed issues, 2 SEO issues 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25