Website review, no card needed

mescius.com logo

mescius.com website review

Visit site (opens in a new tab)Reviewed 31 October 202627 issues · 76 checks

This review found 27 issues worth fixing on mescius.com, 7 of them high impact, across 76 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
1.1 s755 msMay 9Oct 24957 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026911 ms
May 16, 2026939 ms
May 23, 20261.0 s
May 30, 2026977 ms
Jun 6, 2026903 ms
Jun 13, 2026903 ms
Jun 20, 2026922 ms
Jun 27, 2026917 ms
Jul 4, 2026919 ms
Jul 11, 2026843 ms
Jul 18, 2026797 ms
Jul 25, 2026808 ms
Aug 1, 2026868 ms
Aug 8, 2026950 ms
Aug 15, 2026976 ms
Aug 22, 20261.0 s
Aug 29, 20261.0 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.0 s
Sep 26, 2026991 ms
Oct 3, 2026960 ms
Oct 10, 2026950 ms
Oct 17, 2026955 ms
Oct 24, 2026957 ms
Real-visitor tap response (INP)75th percentile, phones
289 ms66 msMay 9Oct 24121 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026219 ms
May 16, 2026235 ms
May 23, 2026238 ms
May 30, 2026260 ms
Jun 6, 2026263 ms
Jul 4, 2026154 ms
Jul 11, 2026154 ms
Jul 18, 2026118 ms
Jul 25, 2026101 ms
Aug 1, 2026110 ms
Aug 8, 2026104 ms
Aug 15, 202699 ms
Aug 22, 202692 ms
Aug 29, 2026132 ms
Sep 5, 2026182 ms
Sep 12, 2026189 ms
Sep 19, 2026212 ms
Sep 26, 2026119 ms
Oct 3, 2026115 ms
Oct 10, 2026141 ms
Oct 17, 2026141 ms
Oct 24, 2026121 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 mescius.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mescius.com at 1.0 s1.0 s
  2. mescius.com at 2.0 s2.0 s
  3. mescius.com at 3.0 s3.0 s
  4. mescius.com at 4.0 s4.0 s
  5. mescius.com at 5.0 s5.0 s
  6. mescius.com at 6.0 s6.0 s
  7. mescius.com at 7.0 s7.0 s
  8. mescius.com at 8.1 s8.1 s

Speed

8 to fix81
  • Render-blocking requests

    1.6 s

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

  • Use efficient cache lifetimes

    650 ms · 3.6 MB

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

  • Mobile performance score: 81

    81/100

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

  • Google Tag Manager adds 323 ms

    323 ms

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

  • Improve image delivery

    309 KiB

    1 image could be 309 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    292 KiB

    About 292 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 2.7 s

    A phone's processor spends 2.7 s on main-thread work while loading, 703 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Google Fonts adds 17 ms

    17 ms

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google Fonts and JSDelivr CDN and others), adding 930 KiB and 340 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 195 KiB

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

  • 9 long tasks on the main thread

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

  • Minify CSS

    32 KiB

    32 KiB could be saved by minifying CSS.

  • Document request latency

    14 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 164 ms

    164 ms

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

Core Web Vitals

3 to fix100
  • Time to Interactive: 11.0 s

    11.0 s

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

  • Speed Index: 6.5 s

    6.5 s

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

  • Total Blocking Time: 511 ms

    511 ms

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

10 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: 0.9 s

    0.9 s

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

  • Real-user INP: 116 ms

    116 ms

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

  • 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: 383 ms

    383 ms

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

  • Tap response (INP) got 42% faster for real visitors

    -42%

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Largest Contentful Paint: 1.2 s

    1.2 s

    Your largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “私たちの提供するソフトウェア製品やソリューションが、世界中のお客様の下で働くこと。 それが、お客様のビジネスの成功、そ…”.

Images and page weight

1 to fix70
  • Page weight: 4.5 MB in 55 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 55 requests on a phone: media 2.3 MB (2), images 792 KiB (7) and scripts 608 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 1.3 g of CO₂ per visit

    1.28 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

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

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

4 to fixGoogle 10080
  • Title is short (12 characters)

    Your title is only 12 characters: “MESCIUS inc.”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (69 characters)

    Your meta description is only 69 characters: “メシウス株式会社(MESCIUS inc.)の企業サイトです。「世界の、役に立つ。」当社の理念、企業情報、採用情報などをご紹介いたします。”. 70 to 160 characters is enough to sell the click.

  • 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://www.mescius.com/sitemap.xml, so Google discovers your pages only by following links.

  • 53 internal links, 0 external

    The homepage links to 53 pages on mescius.com and 0 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “世界の、役に立つ。”.

  • Structured data in place

    Structured data found: 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.

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.

  • No llms.txt

    There is no /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.

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

Other pages

1 to fix93
  • 2 pages share a title

    / and /en/default.html all use the title “MESCIUS inc.”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages with very little text

    /about/default.html, /about/overview.html, /about/philosophy.html, /about/greeting.html, /about/history.html and /about/sustainability.html and 8 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.

  • 1 page slow to respond

    /contact/default.html took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 25 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.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 11 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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 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 30 words

    The homepage has only about 30 words of visible text; thin pages give Google and first-time buyers little to go on.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 2 cookies set on arrival

    2

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 mescius.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

Analytics
Google Analytics
Hosting
SAKURA Internet Inc.

Company

Founded
1980
Headquarters
Sendai

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on mescius.com, including 11 speed issues, 4 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