Website review, no card needed
ecom-ex.com website review
Visit site (opens in a new tab)Reviewed 25 October 202634 issues · 86 checks
This review found 34 issues worth fixing on ecom-ex.com, 14 of them high impact, across 86 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.1 s |
| May 9, 2026 | 4.1 s |
| May 16, 2026 | 4.3 s |
| May 23, 2026 | 4.3 s |
| May 30, 2026 | 4.3 s |
| Jun 6, 2026 | 4.3 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.3 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.4 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.4 s |
| Jul 25, 2026 | 4.4 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.4 s |
| Aug 15, 2026 | 4.5 s |
| Aug 22, 2026 | 4.4 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.1 s |
| Sep 12, 2026 | 4.0 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 184 ms |
| May 9, 2026 | 183 ms |
| May 16, 2026 | 195 ms |
| May 23, 2026 | 211 ms |
| May 30, 2026 | 209 ms |
| Jun 6, 2026 | 225 ms |
| Jun 13, 2026 | 244 ms |
| Jun 20, 2026 | 245 ms |
| Jun 27, 2026 | 249 ms |
| Jul 4, 2026 | 247 ms |
| Jul 11, 2026 | 231 ms |
| Jul 18, 2026 | 219 ms |
| Jul 25, 2026 | 201 ms |
| Aug 1, 2026 | 188 ms |
| Aug 8, 2026 | 191 ms |
| Aug 15, 2026 | 194 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 198 ms |
| Sep 5, 2026 | 191 ms |
| Sep 12, 2026 | 179 ms |
| Sep 19, 2026 | 178 ms |
| Sep 26, 2026 | 172 ms |
| Oct 3, 2026 | 166 ms |
| Oct 10, 2026 | 160 ms |
| Oct 17, 2026 | 153 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 51
51/100Your mobile performance score is 51 (desktop: 60). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
370 ms · 259 KiBAbout 259 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 370 ms faster on a phone.
Reduce unused CSS
370 ms · 78 KiBAbout 78 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 370 ms faster on a phone.
Improve image delivery
300 ms · 37 KiB3 images could be 37 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
1,776 HTML elements
The page has 1,776 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Optanon and Hotjar and others), adding 455 KiB and 332 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 92 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
70 KiB8 files are served with short cache lifetimes, so returning visitors download them again (70 KiB).
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need.
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.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 493 ms of it running JavaScript. That is comfortably low.
Server response: 101 ms
101 msYour server sent the HTML in 101 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.
Largest Contentful Paint: 6.3 s
6.3 sYour largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The innovative, lightweight, and wireless barcode reader an…”.
Cumulative Layout Shift: 0.551
0.551The layout shifts by 0.551 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 11.1 s
11.1 sThe page becomes fully interactive after 11.1 s. Good is under 3.8 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.
Speed Index: 5.4 s
5.4 sVisually, the page fills in at 5.4 s (Speed Index). Good is under 3.4 s.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.1 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 184 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 87 ms
87 msScripts block the page for only 87 ms while loading. Good is under 200 ms.
Images and page weight
3 images below the first screen load straight away
3 images further down the page (93 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.44 g of CO₂e: 53.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.6 MB in 49 requests
1.6 MBYour homepage downloads 1.6 MB in 49 requests on a phone: fonts 653 KiB (4), scripts 548 KiB (12) and images 259 KiB (17). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
27 text elements with low contrast
27 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
9 links inside paragraphs rely on colour alone to stand out.
Elements must only use permitted ARIA attributes (3 elements)
Elements must only use permitted ARIA attributes: 3 elements on the page fail this check, rated serious by axe-core.
Positive tabindex
3 elements have a tabindex above 0, which scrambles the keyboard order.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 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
robots.txt blocks all crawlers
Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
Invalid hreflang
Your hreflang tags are invalid, so Google may show the wrong language version.
9 links with vague text
9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
363 internal links, 39 external
The homepage links to 363 pages on ecom-ex.com and 39 external pages.
5 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “ecom has been a pioneer in the field of intrinsically safe products for 30 years and has acquired an outstanding expert…”.
One H1 headline
Your main headline reads: “Pepperl+Fuchs – Enterprise Mobility”.
Title: 57 characters
Your title is a healthy 57 characters: “ECOM Instruments GmbH - Intrinsically Safe Mobile Devices”.
Canonical URL set
The canonical URL is https://www.ecom-ex.com/index/.
XML sitemap found
Your XML sitemap is reachable at https://www.ecom-ex.com/sitemap.xml.
AI search readiness
robots.txt blocks 6 AI answer engine crawlers
6 of 6Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.
No llms.txt
There is no https://www.ecom-ex.com/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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.
2 checks passed
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,030 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages without a meta description
https://www.ecom-ex.com/tr/home, https://www.ecom-ex.com/zh/home, https://www.ecom-ex.com/ko/home, https://www.ecom-ex.com/vi/home, https://www.ecom-ex.com/th/home and https://www.ecom-ex.com/id/home and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 132 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.
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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=12000803&tm=gtm002&Ver=2&mid=c4f376e0-cb45-451b-9e1a-b29c95d1b6a3&bo=1&sid=626f6690d04511f18124c9c3f98664c1&vid=626f8150d04511f1a7821f9c9c1694d6&vids=1&msclkid=N&pi=91.
15 small tap targets
15 of 46 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
9 low-resolution images
9 images are served at too low a resolution for sharp phone screens.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
About 1,174 words of copy
The homepage carries about 1,174 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “REQUEST A CALLBACK” and “Learn More”.
21 calls to action
The homepage has 21 calls to action, for example “chat Contact”, “Inquire Now” and “Download brochure launch”.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Direct contact links
Visitors can reach you directly: 9 phone links and 0 email links.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Tag Manager, Hotjar, LinkedIn Insight and Microsoft Ads (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 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.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 ecom-ex.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on ecom-ex.com, including 14 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.