Website review, no card needed

wellmotto.com logo

wellmotto.com website review

Visit site (opens in a new tab)Reviewed 10 November 202635 issues · 77 checks

This review found 35 issues worth fixing on wellmotto.com, 14 of them high impact, across 77 checks. The most urgent: render-blocking requests. 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
2.1 s1.3 sMay 23Nov 71.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.7 s
Jun 13, 20262.0 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.6 s
Aug 29, 20261.8 s
Sep 5, 20261.5 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.5 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.5 s
Oct 31, 20261.6 s
Nov 7, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
114 ms79 msMay 23Sep 1995 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202687 ms
May 30, 202690 ms
Jun 6, 2026101 ms
Jun 13, 2026110 ms
Jun 20, 2026103 ms
Jun 27, 2026105 ms
Jul 4, 202698 ms
Jul 11, 202687 ms
Jul 18, 202690 ms
Jul 25, 202683 ms
Aug 8, 202684 ms
Aug 29, 202697 ms
Sep 19, 202695 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 wellmotto.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wellmotto.com at 0.6 s0.6 s
  2. wellmotto.com at 1.2 s1.2 s
  3. wellmotto.com at 1.8 s1.8 s
  4. wellmotto.com at 2.4 s2.4 s
  5. wellmotto.com at 3.0 s3.0 s
  6. wellmotto.com at 3.7 s3.7 s
  7. wellmotto.com at 4.3 s4.3 s
  8. wellmotto.com at 4.9 s4.9 s

Speed

9 to fix60
  • Render-blocking requests

    1.5 s

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

  • Improve image delivery

    800 ms · 5.0 MB

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

  • Mobile performance score: 60

    60/100

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

  • Reduce unused JavaScript

    590 ms · 75 KiB

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

  • Reduce unused CSS

    440 ms · 40 KiB

    About 40 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 440 ms faster on a phone.

  • Minify JavaScript

    300 ms · 38 KiB

    38 KiB could be saved by minifying JavaScript.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Cloudflare CDN, Shopify and jQuery CDN and others), adding 1.4 MB and 83 ms of main-thread time.

  • Google Fonts adds 1 ms

    1 ms

    Google Fonts costs a phone 1 ms of main-thread work and 779 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 22 ms

    22 ms

    Shopify costs a phone 22 ms of main-thread work and 428 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.

  • Minify CSS

    150 ms · 9 KiB

    9 KiB could be saved by minifying CSS.

  • 1 long task on the main thread

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

  • Use efficient cache lifetimes

    8 KiB

    5 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.4 s

    A phone's processor spends 1.4 s on main-thread work while loading, 298 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: 51.4 s

    51.4 s

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

  • Speed Index: 17.3 s

    17.3 s

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

  • Time to Interactive: 52.8 s

    52.8 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • 27 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

6 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.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.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 48 ms

    48 ms

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

Images and page weight

5 to fix18
  • Page weight: 12.9 MB in 246 requests

    12.9 MB

    Your homepage downloads 12.9 MB in 246 requests on a phone: images 6.2 MB (51), fonts 5.5 MB (35) and other files 717 KiB (73). Under 2 MB keeps phones on slow connections fast.

  • 27 images far larger than shown

    5.0 MB

    27 images are downloaded at several times the size a phone draws them, for example 2024.11.15bist_hyoshi1.jpg at 1,099 px wide, shown at 78 px. Resized copies would save about 5.0 MB.

  • 1 image over 500 KB

    2024.11.15bist_hyoshi1.jpg weighs 564 KiB. On a phone connection a single image that size takes seconds.

  • 34 images below the first screen load straight away

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

  • 3 images in older formats

    3 images (608 KiB) 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 3.7 g of CO₂ per visit

    3.66 g

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

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

  • 22 images without alt text

    22 images have no alt text, which hurts accessibility and image search.

  • 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 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 45 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: 45 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9290
  • Meta description is long (179 characters)

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

  • One H1 headline

    Your <h1> is empty.

  • 61 internal links, 6 external

    The homepage links to 61 pages on wellmotto.com and 6 external pages.

6 checks passed
  • Title: 31 characters

    Your title is a healthy 31 characters: “ウェルモット製薬 公式ストア – ウェルモット製薬 公式サイト”.

  • Canonical URL set

    The canonical URL is https://wellmotto.com/.

  • 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://wellmotto.com/sitemap.xml.

AI search readiness

100
3 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • llms.txt published

    The site publishes https://wellmotto.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 7 pages without a meta description

    https://wellmotto.com/collections/online-store, https://wellmotto.com/pages/brand-story, https://wellmotto.com/pages/company, https://wellmotto.com/pages/achievements, https://wellmotto.com/pages/faq-c and https://wellmotto.com/pages/faq-b and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://wellmotto.com/pages/brand-story has no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://wellmotto.com/collections/online-store, https://wellmotto.com/pages/brand-story, https://wellmotto.com/pages/company, https://wellmotto.com/pages/faq-c, https://wellmotto.com/pages/faq-b and https://wellmotto.com/pages/recruitment 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 30 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    7 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 7 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix36
  • 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 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 67 words

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

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

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 Meta Pixel (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.

  • 12 cookies set on arrival

    12

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

  • 21 other companies contacted

    Loading the homepage contacts 21 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 wellmotto.com, 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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

cloudfront.net

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 35 issues on wellmotto.com, including 14 speed issues, 2 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