Website review, no card needed

epson.jp logo

epson.jp website review

Visit site (opens in a new tab)Reviewed 18 November 202661 issues · 99 checks

This review found 61 issues worth fixing on epson.jp, 25 of them high impact, across 99 checks. The most urgent: google Tag Manager adds 3.4 s. 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.7 s1.5 sMay 30Nov 141.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.5 s
Oct 31, 20261.5 s
Nov 7, 20261.5 s
Nov 14, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
448 ms376 msMay 30Nov 14437 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026388 ms
Jun 6, 2026384 ms
Jun 13, 2026386 ms
Jun 20, 2026389 ms
Jun 27, 2026393 ms
Jul 4, 2026399 ms
Jul 11, 2026398 ms
Jul 18, 2026395 ms
Jul 25, 2026392 ms
Aug 1, 2026388 ms
Aug 8, 2026395 ms
Aug 15, 2026405 ms
Aug 22, 2026416 ms
Aug 29, 2026426 ms
Sep 5, 2026428 ms
Sep 12, 2026427 ms
Sep 19, 2026430 ms
Sep 26, 2026428 ms
Oct 3, 2026431 ms
Oct 10, 2026434 ms
Oct 17, 2026435 ms
Oct 24, 2026439 ms
Oct 31, 2026438 ms
Nov 7, 2026440 ms
Nov 14, 2026437 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 epson.jp (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. epson.jp at 1.8 s1.8 s
  2. epson.jp at 3.6 s3.6 s
  3. epson.jp at 5.4 s5.4 s
  4. epson.jp at 7.2 s7.2 s
  5. epson.jp at 9.0 s9.0 s
  6. epson.jp at 10.8 s10.8 s
  7. epson.jp at 12.6 s12.6 s
  8. epson.jp at 14.4 s14.4 s

Speed

15 to fix8
  • Google Tag Manager adds 3.4 s

    3.4 s

    Google Tag Manager costs a phone 3.4 s of main-thread work and 3.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused JavaScript

    1.1 s · 1.9 MB

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

  • Render-blocking requests

    2.8 s

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

  • Mobile performance score: 8

    8/100

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

  • Main-thread work: 7.1 s

    A phone's processor spends 7.1 s on main-thread work while loading, 4.1 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 (Google Tag Manager, Facebook and TikTok and others), adding 4.6 MB and 4.3 s of main-thread time.

  • Use efficient cache lifetimes

    550 ms · 3.4 MB

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

  • Improve image delivery

    960 KiB

    23 images could be 960 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Document request latency

    550 ms · 165 KiB

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

  • Reduce initial server response time

    536 ms

    Reduce initial server response time. Google estimates savings of 536 ms on a phone.

  • Facebook adds 484 ms

    484 ms

    Facebook costs a phone 484 ms of main-thread work and 458 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.

  • Reduce unused CSS

    300 ms · 80 KiB

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

  • 20 long tasks on the main thread

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

  • 2,227 HTML elements

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

  • Server response: 636 ms

    636 ms

    Your server takes 636 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Font display

    150 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

  • Legacy JavaScript

    44 KiB

    Polyfills for old browsers add 44 KiB JavaScript that modern phones do not need.

  • Minify CSS

    25 KiB

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

Core Web Vitals

10 to fix33
  • 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.

  • Real-user CLS: 0.49

    0.49

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

  • Largest Contentful Paint: 12.9 s

    12.9 s

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

  • Speed Index: 18.9 s

    18.9 s

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

  • Time to Interactive: 49.5 s

    49.5 s

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

  • Total Blocking Time: 2.3 s

    2.3 s

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

  • Cumulative Layout Shift: 0.531

    0.531

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Real-user INP: 329 ms

    329 ms

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

  • 23 images without width and height

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

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

    +14%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

3 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 310 ms

    310 ms

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

Images and page weight

4 to fix35
  • Page weight: 8.8 MB in 276 requests

    8.8 MB

    Your homepage downloads 8.8 MB in 276 requests on a phone: scripts 4.8 MB (73), images 3.5 MB (104) and HTML 254 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1,021 KiB together. On a phone connection a single image that size takes seconds.

  • 14 images in older formats

    14 images (3.0 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.

  • 2 images far larger than shown

    19 KiB

    2 images are downloaded at several times the size a phone draws them, for example ico_sns_06.svg at 150 px wide, shown at 46 px. Resized copies would save about 19 KiB.

  • 4 images below the first screen load straight away

    4 images further down the page (249 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.5 g of CO₂ per visit

    2.50 g

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

Accessibility

12 to fixGoogle 8683
  • 33 tap targets too small

    33 tap targets are too small or too close together to hit reliably with a finger.

  • Malformed lists

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (1 element)

    <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 1 element on the page fails this check, rated serious by axe-core.

  • Orphan list items

    Some list items are not inside a list.

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

    All page content should be contained by landmarks: 17 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 44 form fields without a label

    44 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (9 elements)

    Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 240 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 10064
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (11 characters)

    Your title is only 11 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 (46 characters)

    Your meta description is only 46 characters: “日本国内のエプソン製品に関する公式サイトです。製品情報やサポート、企業情報を提供しています。”. 70 to 160 characters is enough to sell the click.

  • No XML sitemap

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

  • No robots.txt

    There is no robots.txt at epson.jp/robots.txt, the first file search crawlers ask for.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 322 internal links, 170 external

    The homepage links to 322 pages on epson.jp and 170 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://www.epson.jp/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

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 https://www.epson.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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

100
  • 14 pages with very little text

    https://www.epson.jp/contact, https://www.epson.jp/ec, https://www.epson.jp/products, https://www.epson.jp/b_solution, https://www.epson.jp/katsuyou and https://www.epson.jp/support 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

    https://www.epson.jp/b_solution took over 3 s to send its HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 149 found) and read each the way a search engine does.

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

6 to fixGoogle 4668
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=343059676&tm=gtm002&Ver=2&mid=a961a7f1-030c-491d-b4ca-93b3df1db3a7&bo=1&sid=5222cbe0e38211f19f14652e5fb4d0cd&vid=5222e5c0e38211f1b8eaddd7b6252c71&vids=1&msclkid=N&pi=9.

  • 27 small tap targets

    27 of 103 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.”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://c.marsflag.com/lib/fonts/font-awesome/4.6.3/css/font-awesome.css' from origin 'htt…”.

  • 7 distorted images

    7 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage has only about 52 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
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 22 cookies set on arrival

    22

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

  • 36 other companies contacted

    Loading the homepage contacts 36 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 epson.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 Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 61 issues on epson.jp, including 25 speed issues, 7 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