Website review, no card needed

epomaker.fr logo

epomaker.fr website review

Visit site (opens in a new tab)Reviewed 7 November 202639 issues · 85 checks

This review found 39 issues worth fixing on epomaker.fr, 11 of them high impact, across 85 checks. The most urgent: 10,647 HTML elements. 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.5 s1.0 sJun 13Oct 101.1 s
Show as table
DateReal-visitor load time (LCP)
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.3 s
Jul 4, 20261.3 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.4 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.5 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.3 s
Sep 26, 20261.2 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
180 ms100 msJun 20Sep 26124 ms
Show as table
DateReal-visitor tap response (INP)
Jun 20, 2026115 ms
Jun 27, 2026113 ms
Jul 4, 2026109 ms
Jul 11, 2026114 ms
Jul 18, 2026118 ms
Jul 25, 2026134 ms
Aug 1, 2026146 ms
Aug 8, 2026146 ms
Aug 15, 2026166 ms
Aug 22, 2026157 ms
Aug 29, 2026171 ms
Sep 5, 2026164 ms
Sep 12, 2026137 ms
Sep 19, 2026132 ms
Sep 26, 2026124 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 epomaker.fr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. epomaker.fr at 0.9 s0.9 s
  2. epomaker.fr at 1.7 s1.7 s
  3. epomaker.fr at 2.6 s2.6 s
  4. epomaker.fr at 3.4 s3.4 s
  5. epomaker.fr at 4.3 s4.3 s
  6. epomaker.fr at 5.2 s5.2 s
  7. epomaker.fr at 6.0 s6.0 s
  8. epomaker.fr at 6.9 s6.9 s

Speed

6 to fix60
  • 10,647 HTML elements

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

  • Main-thread work: 5.8 s

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

  • Mobile performance score: 60

    60/100

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

  • Render-blocking requests

    650 ms

    9 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

  • Improve image delivery

    363 KiB

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

  • Shopify adds 164 ms

    164 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Google Tag Manager and productessentials.app and others), adding 918 KiB and 376 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 239 KiB

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

  • 12 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 77 KiB

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

  • Use efficient cache lifetimes

    140 KiB

    6 files are served with short cache lifetimes, so returning visitors download them again (140 KiB).

  • Legacy JavaScript

    51 KiB

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

  • Minify CSS

    6 KiB

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

1 checks passed
  • Server response: 15 ms

    15 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 5.6 s

    5.6 s

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

  • Time to Interactive: 9.3 s

    9.3 s

    The page becomes fully interactive after 9.3 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: 520 ms

    520 ms

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

  • 1 image without width and height

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

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

    +12%

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

8 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.3 s

    1.3 s

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 0.7 s

    0.7 s

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

  • Real-user TTFB: 402 ms

    402 ms

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

  • Largest content (LCP) got 19% faster for real visitors

    -19%

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

3 to fix69
  • Page weight: 4.0 MB in 307 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 307 requests on a phone: images 1.5 MB (62), other files 1.1 MB (152) and scripts 806 KiB (66). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    shadow-x-tablet-min.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 10 images in older formats

    10 images (594 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 1.1 g of CO₂ per visit

    1.12 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

9 to fixGoogle 7188
  • 8 buttons without a name

    8 buttons have no accessible name, so screen readers announce just “button”.

  • 63 text elements with low contrast

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

  • 10 images without alt text

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

  • 159 form fields without a label

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 46 links without text

    46 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

5 to fixGoogle 8580
  • Title is short (8 characters)

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

  • Meta description is short (51 characters)

    Your meta description is only 51 characters: “The best mechanical keyboards and customer support.”. 70 to 160 characters is enough to sell the click.

  • 10 links crawlers can't follow

    10 links have no real href, so search engines can't follow them.

  • No favicon declared

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

  • One H1 headline

    Your <h1> is empty.

  • 174 internal links, 12 external

    The homepage links to 174 pages on epomaker.fr and 12 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://epomaker.fr/.

  • 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://epomaker.fr/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

7 to fix50
  • 1 page without a title

    https://epomaker.fr/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 4 pages point its canonical at the homepage

    https://epomaker.fr/products/epomaker-rt100, https://epomaker.fr/products/epomaker-feker-galaxy80, https://epomaker.fr/products/epomaker-shadow-x and https://epomaker.fr/products/th80pro-v2-via declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 1 linked page hidden from search

    https://epomaker.fr/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 5 pages share a title

    /, https://epomaker.fr/products/epomaker-rt100, https://epomaker.fr/products/epomaker-feker-galaxy80, https://epomaker.fr/products/epomaker-shadow-x and https://epomaker.fr/products/th80pro-v2-via all use the title “Epomaker”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://epomaker.fr/collections/all, https://epomaker.fr/pages/contact, https://epomaker.fr/customer_authentication/redirect, https://epomaker.fr/pages/wishlist and https://epomaker.fr/pages/compare-1 have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://epomaker.fr/products/epomaker-rt100, https://epomaker.fr/products/epomaker-feker-galaxy80, https://epomaker.fr/products/epomaker-shadow-x and https://epomaker.fr/products/th80pro-v2-via use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://epomaker.fr/collections/all, https://epomaker.fr/customer_authentication/redirect and https://epomaker.fr/products/epomaker-em3 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'childElementCount')”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

    Social proof on the homepage: 102 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 1,263 words of copy

    The homepage carries about 1,263 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “ORDER NOW”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Join Discord”, “Contact” and “Register”.

  • 33 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 9 cookies set on arrival

    9

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 epomaker.fr, 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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Buddha Mega Menu Navigation · Judge Me Reviews · Asklayer Dev · Discount Planner By Productessentials

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
Analytics
Google Analytics
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on epomaker.fr, including 11 speed issues, 5 SEO issues and 1 conversion gap. 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