Website review, no card needed

lmbs.co.jp logo

lmbs.co.jp website review

Visit site (opens in a new tab)Reviewed 16 November 202640 issues · 78 checks

This review found 40 issues worth fixing on lmbs.co.jp, 20 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. 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

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

How it loaded on a phone

  1. lmbs.co.jp at 0.4 s0.4 s
  2. lmbs.co.jp at 0.9 s0.9 s
  3. lmbs.co.jp at 1.3 s1.3 s
  4. lmbs.co.jp at 1.8 s1.8 s
  5. lmbs.co.jp at 2.2 s2.2 s
  6. lmbs.co.jp at 2.7 s2.7 s
  7. lmbs.co.jp at 3.1 s3.1 s
  8. lmbs.co.jp at 3.6 s3.6 s

Speed

9 to fix33
  • Use efficient cache lifetimes

    4.7 s · 12.2 MB

    76 files are served with short cache lifetimes, so returning visitors download them again (12.2 MB).

  • Improve image delivery

    1.8 s · 10.4 MB

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

  • Reduce unused JavaScript

    2.8 s · 632 KiB

    About 632 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.8 s faster on a phone.

  • Render-blocking requests

    1.2 s

    12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

  • Mobile performance score: 33

    33/100

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

  • 3,157 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, cloudfront.net and Google Analytics and others), adding 13.1 MB and 720 ms of main-thread time.

  • cloudfront.net adds 27 ms

    27 ms

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

    610 ms

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

  • 8 long tasks on the main thread

    8 long tasks block the main thread while loading, the longest for 160 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    50 KiB

    About 50 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    14 KiB

    14 KiB could be saved by minifying JavaScript.

  • Minify CSS

    9 KiB

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

2 checks passed
  • Main-thread work: 1.8 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

7 to fix29
  • Largest Contentful Paint: 40.0 s

    40.0 s

    Your largest element takes 40.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “赤ちゃんとママの 未来の肌のために”.

  • Time to Interactive: 43.0 s

    43.0 s

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

  • Cumulative Layout Shift: 1

    1

    The layout shifts by 1 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • Speed Index: 6.6 s

    6.6 s

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

  • 72 images without width and height

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

  • Total Blocking Time: 238 ms

    238 ms

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

5 to fix18
  • Page weight: 13.3 MB in 125 requests

    13.3 MB

    Your homepage downloads 13.3 MB in 125 requests on a phone: images 11.9 MB (61), scripts 1.4 MB (24) and stylesheets 82 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 24 images far larger than shown

    4.0 MB

    24 images are downloaded at several times the size a phone draws them, for example top_products_item11.png at 1,000 px wide, shown at 257 px. Resized copies would save about 4.0 MB.

  • 5 images over 500 KB

    5 images weigh 3.3 MB together. On a phone connection a single image that size takes seconds.

  • 27 images in older formats

    27 images (10.5 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.

  • 25 images below the first screen load straight away

    25 images further down the page (10.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.8 g of CO₂ per visit

    3.78 g

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

Accessibility

5 to fixGoogle 8991
  • 4 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Headings skip levels

    Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 115 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

5 to fixGoogle 10076
  • Title is short (25 characters)

    Your title is only 25 characters: “LIQUEST MAMA & BABY STORE”. 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.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No XML sitemap

    No XML sitemap at https://lmbs.co.jp/sitemap.xml, so Google discovers your pages only by following links.

  • One H1 headline

    Your <h1> is empty.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 238 internal links, 3 external

    The homepage links to 238 pages on lmbs.co.jp and 3 external pages.

2 checks passed
  • Meta description: 77 characters

    Your meta description is 77 characters: “生まれたばかりの赤ちゃんから、家族みんなで安心して使える育肌に寄り添うケアシリーズをお届け。ボディケアから頭皮のケアまで、全身くまなくお使いいただけます。”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://lmbs.co.jp/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (316 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix48
  • 1 linked page is broken

    Your homepage links to https://lmbs.co.jp/shop/product_categories/deodorizeseries, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 page without a title

    https://lmbs.co.jp/shop/pages/series04 has no <title>, so Google invents the link text in results.

  • 2 pages share a title

    / and https://lmbs.co.jp/shop all use the title “LIQUEST MAMA & BABY STORE”. 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://lmbs.co.jp/shop/pages/series04 has no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages with very little text

    https://lmbs.co.jp/shop/pages/concept, https://lmbs.co.jp/shop/pages/series04, https://lmbs.co.jp/shop/product_categories/skincare, https://lmbs.co.jp/shop/product_categories/set, https://lmbs.co.jp/shop/product_categories/haircare and https://lmbs.co.jp/shop/product_categories/trial and 5 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 67 found) and read each the way a search engine does.

3 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

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

Best practices

1 to fixGoogle 9693
  • 7 small tap targets

    7 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 264 words of copy

    The homepage carries about 264 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “店舗一覧 Shop list” and “会員登録 / ログイン Sign up / Login”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “店舗一覧Shop list”, “会員登録 / ログインSign up / Login” and “店舗一覧 Shop list”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 14 cookies set on arrival

    14

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 lmbs.co.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
Analytics
Google Analytics
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on lmbs.co.jp, including 16 speed issues, 5 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

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