Website review, no card needed
lewa.com website review
Visit site (opens in a new tab)Reviewed 29 October 202628 issues · 83 checks
This review found 28 issues worth fixing on lewa.com, 10 of them high impact, across 83 checks. The most urgent: fails Core Web Vitals for real visitors. 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 9, 2026 | 3.7 s |
| May 16, 2026 | 3.8 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 3.9 s |
| Jun 13, 2026 | 4.0 s |
| Jun 20, 2026 | 4.1 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.3 s |
| Jul 18, 2026 | 4.3 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.4 s |
| Aug 8, 2026 | 4.4 s |
| Aug 15, 2026 | 4.6 s |
| Aug 22, 2026 | 4.5 s |
| Aug 29, 2026 | 4.5 s |
| Sep 5, 2026 | 4.6 s |
| Sep 12, 2026 | 4.6 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.8 s |
| Oct 3, 2026 | 4.5 s |
| Oct 10, 2026 | 4.4 s |
| Oct 17, 2026 | 4.3 s |
| Oct 24, 2026 | 4.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 139 ms |
| May 16, 2026 | 139 ms |
| May 23, 2026 | 143 ms |
| May 30, 2026 | 146 ms |
| Jun 6, 2026 | 149 ms |
| Jun 13, 2026 | 151 ms |
| Jun 20, 2026 | 150 ms |
| Jun 27, 2026 | 149 ms |
| Jul 4, 2026 | 150 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 147 ms |
| Aug 1, 2026 | 151 ms |
| Aug 8, 2026 | 156 ms |
| Aug 15, 2026 | 155 ms |
| Aug 22, 2026 | 150 ms |
| Aug 29, 2026 | 148 ms |
| Sep 5, 2026 | 150 ms |
| Sep 12, 2026 | 153 ms |
| Sep 19, 2026 | 157 ms |
| Sep 26, 2026 | 149 ms |
| Oct 3, 2026 | 143 ms |
| Oct 10, 2026 | 139 ms |
| Oct 17, 2026 | 138 ms |
| Oct 24, 2026 | 140 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
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 270 KiBAbout 270 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Render-blocking requests
500 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
1,541 HTML elements
The page has 1,541 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
250 ms · 48 KiBAbout 48 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 250 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (consentmanager.net, Google Tag Manager and industrialflowglobal.com and others), adding 595 KiB and 237 ms of main-thread time.
Use efficient cache lifetimes
157 KiB8 files are served with short cache lifetimes, so returning visitors download them again (157 KiB).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 72 ms. During a long task the page ignores taps.
Improve image delivery
28 KiB2 images could be 28 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 372 ms of it running JavaScript. That is comfortably low.
Server response: 117 ms
117 msYour server sent the HTML in 117 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.
Real-user LCP: 4.2 s
4.2 sReal visitors wait 4.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.5 s
3.5 sReal visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 4.7 s
4.7 sYour largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 8.8 s
8.8 sThe page becomes fully interactive after 8.8 s. Good is under 3.8 s.
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.
Real-user CLS: 0.11
0.11For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.
Speed Index: 4.9 s
4.9 sVisually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 s.
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) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 139 ms to 140 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.7 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 144 ms
144 msReal visitors wait 144 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0.095
0.095The layout barely moves while loading (CLS 0.095, good is under 0.1).
Total Blocking Time: 23 ms
23 msScripts block the page for only 23 ms while loading. Good is under 200 ms.
Images and page weight
About 0.4 g of CO₂ per visit
0.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.35 g of CO₂e: 42.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.2 MB in 68 requests
1.2 MBYour homepage downloads 1.2 MB in 68 requests on a phone: scripts 759 KiB (20), fonts 320 KiB (9) and images 111 KiB (26). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
Unlabelled dropdowns
2 dropdowns have no label.
15 tap targets too small
15 tap targets are too small or too close together to hit reliably with a finger.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 36 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
191 internal links, 13 external
The homepage links to 191 pages on lewa.com and 13 external pages.
7 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “LEWA, leading manufacturer of industrial pumps and dosing systems for liquid dosing: 60 years of experience in consulti…”.
One H1 headline
Your main headline reads: “LEWA - pumps and systems from the leading manufacturer”.
Title: 54 characters
Your title is a healthy 54 characters: “LEWA, Pump Manufacturer Germany: Dosing systems | LEWA”.
Canonical URL set
The canonical URL is https://www.lewa.com/en-US/.
Structured data in place
Structured data found: Organization and WebSite.
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.lewa.com/en/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.lewa.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.
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.
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 (1,509 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.lewa.com/en-US/lewa-in-usa is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.lewa.com/en-US/pumps, whose canonical is https://www.lewa.com/en-US/pumps?gad_campaignid=640002440&gad_source=1&gbraid=0AAAAADivlwRJBLFw_ORPeOdyjbWPje58D&cHash=69445b2f3a6d68fe5399b529ecbf8feb. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page slow to respond
https://www.lewa.com/en-US/representatives-finder took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 95 found) and read each the way a search engine does.
5 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
Every page has a meta description
All 13 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.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Connecting to 'https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,600&subset=latin,vietnamese' violates the fo…”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
37 of 46 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
A 11-field form
Your longest form asks for 11 fields (10 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 970 words of copy
The homepage carries about 970 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: “Learn more!”.
10 calls to action
The homepage has 10 calls to action, for example “Contact”, “Whitepaper Download Form” and “Whitepaper Download Confirmation”.
Analytics in place
Analytics detected: Google Tag Manager and Matomo.
Direct contact links
Visitors can reach you directly: 1 phone link and 4 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.
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: consentmanager
A consent management tool (consentmanager) 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 lewa.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- TYPO3 CMS
- Framework
- jQuery
- Analytics
- Google Tag Manager | Matomo
- Hosting
- Hetzner
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on lewa.com, including 14 speed issues, 2 SEO issues and 3 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.