Website review, no card needed
freudenberg-pm.com website review
Visit site (opens in a new tab)Reviewed 3 November 202618 issues · 70 checks
This review found 18 issues worth fixing on freudenberg-pm.com, 2 of them high impact, across 70 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
88BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.5 s |
| May 23, 2026 | 4.3 s |
| May 30, 2026 | 3.8 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.7 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 116 ms |
| May 23, 2026 | 117 ms |
| May 30, 2026 | 116 ms |
| Jun 6, 2026 | 118 ms |
| Jun 13, 2026 | 114 ms |
| Jun 20, 2026 | 112 ms |
| Jun 27, 2026 | 116 ms |
| Jul 4, 2026 | 108 ms |
| Jul 11, 2026 | 108 ms |
| Jul 18, 2026 | 112 ms |
| Jul 25, 2026 | 110 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 111 ms |
| Aug 15, 2026 | 110 ms |
| Aug 22, 2026 | 110 ms |
| Aug 29, 2026 | 110 ms |
| Sep 5, 2026 | 110 ms |
| Sep 12, 2026 | 112 ms |
| Sep 19, 2026 | 106 ms |
| Sep 26, 2026 | 103 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 99 ms |
| Oct 17, 2026 | 106 ms |
| Oct 24, 2026 | 105 ms |
| Oct 31, 2026 | 105 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
Mobile performance score: 86
86/100Your mobile performance score is 86. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
663 KiB18 files are served with short cache lifetimes, so returning visitors download them again (663 KiB).
Render-blocking requests
500 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Reduce unused JavaScript
300 ms · 138 KiBAbout 138 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
1,745 HTML elements
The page has 1,745 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
239 KiB7 images could be 239 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
3 third-party services on the page
3 third-party services load with your homepage (Usercentrics CMP, Azure Web Services and Google Tag Manager), adding 528 KiB and 86 ms of main-thread time.
Reduce unused CSS
53 KiBAbout 53 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 487 ms of it running JavaScript. That is comfortably low.
Server response: 93 ms
93 msYour server sent the HTML in 93 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: 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.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.8 s
3.8 sYour largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 4.6 s
4.6 sVisually, the page fills in at 4.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 3.9 s
3.9 sThe page becomes fully interactive after 3.9 s. Good is under 3.8 s.
7 checks passed
Real-user INP: 102 ms
102 msReal visitors wait 102 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.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 116 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 48% faster for real visitors
-48%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.5 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
About 0.5 g of CO₂ per visit
0.49 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.49 g of CO₂e: 58.4 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.7 MB in 81 requests
1.7 MBYour homepage downloads 1.7 MB in 81 requests on a phone: scripts 749 KiB (24), images 720 KiB (16) and fonts 233 KiB (3). 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
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 40 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 1 failed. 2 mores 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.
250 internal links, 16 external
The homepage links to 250 pages on freudenberg-pm.com and 16 external pages.
7 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Global leader in nonwovens, wovens, knitted fabrics, foams, microfilaments & composites for industrial and professional…”.
One H1 headline
Your main headline reads: “Pioneering technologies and innovative solutions for high-tech technical textiles”.
Title: 65 characters
Your title is a healthy 65 characters: “Innovative Technical Textiles – Freudenberg Performance Materials”.
Canonical URL set
The canonical URL is https://www.freudenberg-pm.com/en.
Structured data in place
Structured data found: WebPage.
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.freudenberg-pm.com/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.
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 (1,914 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.freudenberg-pm.com/llms.txt (7 KiB, 47 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
/ and https://www.freudenberg-pm.com/en all use the title “Innovative Technical Textiles – Freudenberg Performance Materials”. Search engines can't tell which page to show for a search, so each competes with the others.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 98 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
6 of 6 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 518 words of copy
The homepage carries about 518 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact”.
6 calls to action
The homepage has 6 calls to action, for example “Contact” and “Contact us”.
Analytics in place
Analytics detected: Google Tag Manager.
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 (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) 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 freudenberg-pm.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- Optimizely AB
Hiring
- Hiring
- 3 open roles
- Job board
- careers page
Company
- Employees
- 3,000
- Founded
- 2015
- Headquarters
- Weinheim
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 18 issues on freudenberg-pm.com, including 12 speed issues, 1 SEO issue and 2 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.