Website review, no card needed

ewellix.com logo

ewellix.com website review

Visit site (opens in a new tab)Reviewed 26 October 202652 issues · 82 checks

This review found 52 issues worth fixing on ewellix.com, 26 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. 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
8.2 s5.2 sMay 9Oct 245.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20267.6 s
May 16, 20267.3 s
May 23, 20267.5 s
May 30, 20267.9 s
Jun 6, 20267.8 s
Jun 13, 20267.8 s
Jun 20, 20267.5 s
Jun 27, 20267.4 s
Jul 4, 20267.4 s
Jul 11, 20267.3 s
Jul 18, 20267.3 s
Jul 25, 20267.2 s
Aug 1, 20266.8 s
Aug 8, 20266.5 s
Aug 15, 20266.1 s
Aug 22, 20265.8 s
Aug 29, 20265.7 s
Sep 5, 20265.6 s
Sep 12, 20265.8 s
Sep 19, 20265.8 s
Sep 26, 20265.9 s
Oct 3, 20265.9 s
Oct 10, 20265.8 s
Oct 17, 20265.9 s
Oct 24, 20265.8 s
Real-visitor tap response (INP)75th percentile, phones
409 ms299 msMay 9Oct 24391 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026396 ms
May 16, 2026359 ms
May 23, 2026362 ms
May 30, 2026368 ms
Jun 6, 2026376 ms
Jun 13, 2026376 ms
Jun 20, 2026373 ms
Jun 27, 2026371 ms
Jul 4, 2026349 ms
Jul 11, 2026344 ms
Jul 18, 2026315 ms
Jul 25, 2026318 ms
Aug 1, 2026312 ms
Aug 8, 2026322 ms
Aug 15, 2026323 ms
Aug 22, 2026323 ms
Aug 29, 2026337 ms
Sep 5, 2026325 ms
Sep 12, 2026351 ms
Sep 19, 2026346 ms
Sep 26, 2026351 ms
Oct 3, 2026372 ms
Oct 10, 2026364 ms
Oct 17, 2026388 ms
Oct 24, 2026391 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 ewellix.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ewellix.com at 1.1 s1.1 s
  2. ewellix.com at 2.3 s2.3 s
  3. ewellix.com at 3.4 s3.4 s
  4. ewellix.com at 4.5 s4.5 s
  5. ewellix.com at 5.7 s5.7 s
  6. ewellix.com at 6.8 s6.8 s
  7. ewellix.com at 7.9 s7.9 s
  8. ewellix.com at 9.1 s9.1 s

Speed

12 to fix25
  • Use efficient cache lifetimes

    8.6 s · 4.9 MB

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

  • Reduce unused JavaScript

    6.5 s · 4.0 MB

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

  • schaeffler-ecommerce.com adds 2.2 s

    2.2 s

    schaeffler-ecommerce.com costs a phone 2.2 s of main-thread work and 4.6 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.

  • Main-thread work: 10.9 s

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

  • Mobile performance score: 25

    25/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (schaeffler-ecommerce.com, Google Tag Manager and partcommunity.com and others), adding 9.6 MB and 3.9 s of main-thread time.

  • Improve image delivery

    1.5 MB

    14 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 20 long tasks on the main thread

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

  • Render-blocking requests

    900 ms

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

  • partcommunity.com adds 372 ms

    372 ms

    partcommunity.com costs a phone 372 ms of main-thread work and 4.1 MB 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.

  • Google Tag Manager adds 696 ms

    696 ms

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

  • 2,992 HTML elements

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

  • Reduce unused CSS

    146 KiB

    About 146 KiB of CSS is downloaded but never applied on this page.

  • Font display

    50 ms

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

  • Legacy JavaScript

    9 KiB

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

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

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

    1 ms

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

Core Web Vitals

11 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 LCP: 5.1 s

    5.1 s

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

  • Real-user FCP: 5.1 s

    5.1 s

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

  • First Contentful Paint: 10.2 s

    10.2 s

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

  • Largest Contentful Paint: 15.2 s

    15.2 s

    Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Schaeffler Linear Motion – Innovative Solutions for Automat…”. Most of its time is element render delay (6.6 s).

  • Total Blocking Time: 4.6 s

    4.6 s

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

  • Time to Interactive: 41.5 s

    41.5 s

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

  • Speed Index: 15.4 s

    15.4 s

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

  • Real-user INP: 458 ms

    458 ms

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • 7 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

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

    -21%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix33
  • Page weight: 10.5 MB in 139 requests

    10.5 MB

    Your homepage downloads 10.5 MB in 139 requests on a phone: scripts 6.3 MB (48), images 3.8 MB (57) and other files 240 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    1.1 MB

    6 images are downloaded at several times the size a phone draws them, for example High_performance_actuators_range.jpg at 1,920 px wide, shown at 356 px. Resized copies would save about 1.1 MB.

  • 8 images in older formats

    8 images (1.7 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.

  • 11 images below the first screen load straight away

    11 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.0 g of CO₂ per visit

    2.98 g

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

Accessibility

7 to fixGoogle 7789
  • Images must have alternative text (36 elements)

    Images must have alternative text: 36 elements on the page fail this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Interactive controls must not be nested (21 elements)

    Interactive controls must not be nested: 21 elements on the page fail this check, rated serious by axe-core.

  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 5 form fields without a label

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

  • 2 links without text

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

1 checks passed
  • 47 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: 47 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

9 to fixGoogle 6965
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • Invalid hreflang

    Your hreflang tags are invalid, so Google may show the wrong language version.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

3 checks passed
  • Title: 31 characters

    Your title is a healthy 31 characters: “Schaeffler eCommerce Industrial”.

  • 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://medias.schaeffler.us/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 1,594 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://medias.schaeffler.us/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.

Best practices

3 to fixGoogle 7385
  • 3 small tap targets

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

  • 2 third-party cookies

    2 third-party cookies are 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://cdn.schaeffler-ecommerce.com/ecom/6.6HF2/modern/main.css?v=10' from origin 'https:…”.

  • 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

4 to fix30
  • 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.

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

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 1 tracker load before any consent

    1

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

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies, 1 of them by other companies (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 ewellix.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on ewellix.com, including 23 speed issues, 9 SEO issues and 4 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