Website review, no card needed

baumkuchenexpo.jp logo

baumkuchenexpo.jp website review

Visit site (opens in a new tab)Reviewed 5 November 202638 issues · 77 checks

This review found 38 issues worth fixing on baumkuchenexpo.jp, 11 of them high impact, across 77 checks. The most urgent: improve image delivery. 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
1.1 s693 msMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.0 s
May 23, 2026976 ms
May 30, 2026931 ms
Jun 6, 2026899 ms
Jun 13, 2026881 ms
Jun 20, 2026906 ms
Jun 27, 2026901 ms
Jul 4, 2026919 ms
Jul 11, 2026963 ms
Jul 18, 2026969 ms
Jul 25, 2026978 ms
Aug 1, 20261.0 s
Aug 8, 2026957 ms
Aug 15, 2026847 ms
Aug 22, 2026846 ms
Aug 29, 2026810 ms
Sep 5, 2026790 ms
Sep 12, 2026788 ms
Sep 19, 2026740 ms
Sep 26, 2026741 ms
Oct 3, 2026744 ms
Oct 10, 2026743 ms
Oct 17, 2026805 ms
Oct 24, 20261.0 s
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
91 ms76 msMay 16Oct 3186 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202679 ms
May 23, 202683 ms
May 30, 202683 ms
Jun 6, 202680 ms
Jun 13, 202678 ms
Aug 15, 202686 ms
Aug 22, 202687 ms
Aug 29, 202684 ms
Sep 5, 202684 ms
Sep 12, 202687 ms
Sep 19, 202689 ms
Sep 26, 202688 ms
Oct 3, 202689 ms
Oct 10, 202688 ms
Oct 17, 202684 ms
Oct 24, 202684 ms
Oct 31, 202686 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 baumkuchenexpo.jp (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. baumkuchenexpo.jp at 0.6 s0.6 s
  2. baumkuchenexpo.jp at 1.2 s1.2 s
  3. baumkuchenexpo.jp at 1.8 s1.8 s
  4. baumkuchenexpo.jp at 2.4 s2.4 s
  5. baumkuchenexpo.jp at 3.1 s3.1 s
  6. baumkuchenexpo.jp at 3.7 s3.7 s
  7. baumkuchenexpo.jp at 4.3 s4.3 s
  8. baumkuchenexpo.jp at 4.9 s4.9 s

Speed

6 to fix63
  • Improve image delivery

    5.0 s · 4.4 MB

    33 images could be 4.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.0 s faster on a phone.

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    500 ms

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

  • Reduce unused JavaScript

    300 ms · 84 KiB

    About 84 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 73 KiB

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

  • Google Fonts adds 4 ms

    4 ms

    Google Fonts costs a phone 4 ms of main-thread work and 715 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (JSDelivr CDN, Shopify and amp-cdn.tokyo and others), adding 962 KiB and 96 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 93 ms. During a long task the page ignores taps.

  • Minify CSS

    29 KiB

    29 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    8 KiB

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

  • 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.

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 228 ms of it running JavaScript. That is comfortably low.

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 29.4 s

    29.4 s

    Your largest element takes 29.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “バウムクーヘン博覧会キービジュアル”.

  • Time to Interactive: 30.5 s

    30.5 s

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

  • Speed Index: 11.7 s

    11.7 s

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

  • 47 images without width and height

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.1 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: 1.1 s

    1.1 s

    Real visitors wait 1.1 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: 0.9 s

    0.9 s

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

  • Real-user TTFB: 436 ms

    436 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 43 ms

    43 ms

    Scripts block the page for only 43 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix25
  • 11 images over 500 KB

    11 images weigh 17.5 MB together. On a phone connection a single image that size takes seconds.

  • 11 images far larger than shown

    10.9 MB

    11 images are downloaded at several times the size a phone draws them, for example about-mini-baum2.webp at 10,234 px wide, shown at 799 px. Resized copies would save about 10.9 MB.

  • Page weight: 8.1 MB in 235 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 235 requests on a phone: images 5.7 MB (39), fonts 1.3 MB (52) and other files 671 KiB (72). Under 2 MB keeps phones on slow connections fast.

  • 13 images in older formats

    13 images (17.6 MB) 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.

  • About 2.3 g of CO₂ per visit

    2.30 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.30 g of CO₂e: 275.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 9695
  • 2 text elements with low contrast

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

2 checks passed
  • Every image has alt text

    All 101 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

4 to fixGoogle 10079
  • Title is short (10 characters)

    Your title is only 10 characters: “バウムクーヘン博覧会”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (47 characters)

    Your meta description is only 47 characters: “全国47都道府県のバウムクーヘンと その愛好家たちが集う 日本最大のバウムクーヘンの祭典です。”. 70 to 160 characters is enough to sell the click.

  • One H1 headline

    Your <h1> is empty.

  • 43 internal links, 10 external

    The homepage links to 43 pages on baumkuchenexpo.jp and 10 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://baumkuchenexpo.jp/en.

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

AI search readiness

1 to fix83
  • 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://baumkuchenexpo.jp/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

6 to fix55
  • 1 page without a title

    https://baumkuchenexpo.jp/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://baumkuchenexpo.jp/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    https://baumkuchenexpo.jp/pages/contact and https://baumkuchenexpo.jp/en/pages/contact all use the title “お問い合わせ – バウムクーヘン博覧会”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://baumkuchenexpo.jp/en/collections/all, https://baumkuchenexpo.jp/customer_authentication/redirect, https://baumkuchenexpo.jp/en/policies/shipping-policy, https://baumkuchenexpo.jp/pages/contact and https://baumkuchenexpo.jp/en/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 links to non-canonical URLs

    Your homepage links to 9 pages by a URL that isn't their canonical one, for example https://baumkuchenexpo.jp/pages/contact, whose canonical is https://baumkuchenexpo.jp/en/pages/contact. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://baumkuchenexpo.jp/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://baumkuchenexpo.jp/en/policies/shipping-policy, https://baumkuchenexpo.jp/pages/contact, https://baumkuchenexpo.jp/en/pages/contact, https://baumkuchenexpo.jp/pages/event, https://baumkuchenexpo.jp/pages/all-store and https://baumkuchenexpo.jp/pages/general-election-for-baumkuchen 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://baumkuchenexpo.jp/customer_authentication/redirect, https://baumkuchenexpo.jp/pages/contact and https://baumkuchenexpo.jp/pages/event took over 3 s to send their HTML from our server.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    14 of 14 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix43
  • 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: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 49 words

    The homepage has only about 49 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.

1 checks passed
  • 1 short form

    A short form (0 fields at most) is right on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 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.

  • 15 other companies contacted

    Loading the homepage contacts 15 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 baumkuchenexpo.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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Globo Product Options · amp-cdn.tokyo

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
Hosting
Shopify

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 baumkuchenexpo.jp, including 11 speed issues, 4 SEO issues and 6 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