Website review, no card needed
epson.eu website review
Visit site (opens in a new tab)Reviewed 27 October 202640 issues · 83 checks
This review found 40 issues worth fixing on epson.eu, 9 of them high impact, across 83 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.2 s |
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.0 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 156 ms |
| May 16, 2026 | 155 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 157 ms |
| Jun 6, 2026 | 157 ms |
| Jun 13, 2026 | 162 ms |
| Jun 20, 2026 | 165 ms |
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 163 ms |
| Jul 11, 2026 | 161 ms |
| Jul 18, 2026 | 161 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 163 ms |
| Aug 15, 2026 | 163 ms |
| Aug 22, 2026 | 163 ms |
| Aug 29, 2026 | 161 ms |
| Sep 5, 2026 | 158 ms |
| Sep 12, 2026 | 155 ms |
| Sep 19, 2026 | 154 ms |
| Sep 26, 2026 | 158 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 163 ms |
| Oct 17, 2026 | 163 ms |
| Oct 24, 2026 | 161 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
Speed
Render-blocking requests
2.0 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
Use efficient cache lifetimes
1.2 s · 674 KiB45 files are served with short cache lifetimes, so returning visitors download them again (674 KiB).
Reduce unused JavaScript
750 ms · 603 KiBAbout 603 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Mobile performance score: 64
64/100Your mobile performance score is 64 (desktop: 94). Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Google CDN, Adobe Tag Manager and Optanon and others), adding 1.4 MB and 743 ms of main-thread time.
Reduce unused CSS
450 ms · 176 KiBAbout 176 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google CDN adds 393 ms
393 msGoogle CDN costs a phone 393 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.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,546 HTML elements
The page has 1,546 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 15 KiBPolyfills for old browsers add 15 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 139 ms. During a long task the page ignores taps.
Phones get a much slower page than desktops
Desktop scores 94 but mobile only 64. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 119 ms
119 msYour server sent the HTML in 119 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 12.5 s
12.5 sThe page becomes fully interactive after 12.5 s. Good is under 3.8 s.
Largest Contentful Paint: 5.2 s
5.2 sYour largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FIND OUT MORE ABOUT EPSON”.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 331 ms
331 msScripts block taps and scrolling for 331 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 156 ms to 161 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-24, real Chrome visitors' largest content (lcp) went from 3.2 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 170 ms
170 msReal visitors wait 170 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.1 MB in 72 requests
2.1 MBYour homepage downloads 2.1 MB in 72 requests on a phone: scripts 1.2 MB (40), other files 410 KiB (9) and images 223 KiB (14). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (74 KiB) is 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 0.6 g of CO₂ per visit
0.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.60 g of CO₂e: 71.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 3 images in the HTML carry an alt attribute.
44 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: 44 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Meta description is short (8 characters)
Your meta description is only 8 characters: “Epson EU”. 70 to 160 characters is enough to sell the click.
Structured data has 1 problem
Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token ']', ..." ] } " is not valid J)”.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
250 internal links, 81 external
The homepage links to 250 pages on epson.eu and 81 external pages.
5 checks passed
Title: 31 characters
Your title is a healthy 31 characters: “Country Selector | Epson Europe”.
Canonical URL set
The canonical URL is https://www.epson.eu/en_EU/country-selector.
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://www.epson.eu/sitemap.xml.
AI search readiness
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.eu/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 (986 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.epson.eu/c/consumer and https://www.epson.eu/products/printers/inkjet/consumer/c/consumer all use the title “Consumer | Inkjet Printers | Printers | Products | Epson Europe”. 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://www.epson.eu/en_EU has no meta description, so Google writes the search snippet from whatever text it finds.
14 links to non-canonical URLs
Your homepage links to 14 pages by a URL that isn't their canonical one, for example https://www.epson.eu/for-home, whose canonical is https://www.epson.eu/en_EU/for-home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages share a meta description
https://www.epson.eu/c/consumer and https://www.epson.eu/products/printers/inkjet/consumer/c/consumer use the same meta description. A description written for each page earns more clicks.
1 page slow to respond
https://www.epson.eu/c/consumer took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 164 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
21 small tap targets
21 of 94 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “ReferenceError: paragraphData is not defined”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 245 words
The homepage has only about 245 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
4 calls to action
The homepage has 4 calls to action, for example “Why buy genuine Ink?”, “Book a Virtual Tour” and “Contact us”.
4 short forms
4 short forms (2 fields at most) are right on the homepage.
Privacy and tracking
7 cookies set on arrival
7Opening the homepage sets 7 cookies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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.eu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Imperva
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 epson.eu, including 19 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.