Website review, no card needed
faun.com website review
Visit site (opens in a new tab)Reviewed 26 October 202633 issues · 96 checks
This review found 33 issues worth fixing on faun.com, 13 of them high impact, across 96 checks. The most urgent: 1 image over 500 KB. 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.4 s |
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.7 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 171 ms |
| May 9, 2026 | 178 ms |
| May 16, 2026 | 177 ms |
| May 23, 2026 | 179 ms |
| May 30, 2026 | 172 ms |
| Jun 6, 2026 | 178 ms |
| Jun 13, 2026 | 169 ms |
| Jun 20, 2026 | 165 ms |
| Jun 27, 2026 | 166 ms |
| Jul 4, 2026 | 160 ms |
| Jul 11, 2026 | 150 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 137 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 124 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 126 ms |
| Aug 29, 2026 | 126 ms |
| Sep 5, 2026 | 127 ms |
| Sep 12, 2026 | 125 ms |
| Sep 19, 2026 | 125 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 119 ms |
| Oct 10, 2026 | 114 ms |
| Oct 17, 2026 | 111 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
1.2 s
2.4 s
3.6 s
4.8 s
6.0 s
7.2 s
8.4 s
9.6 s
faun.com does not allow embedding, so this is Google's rendering of the page.
Speed
Render-blocking requests
2.5 s52 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Mobile performance score: 67
67/100Your mobile performance score is 67 (desktop: 83). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
450 ms · 309 KiB84 files are served with short cache lifetimes, so returning visitors download them again (309 KiB).
Font display
550 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).
Reduce unused CSS
300 ms · 47 KiBAbout 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
1,671 HTML elements
The page has 1,671 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
92 KiB5 images could be 92 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
86 KiBAbout 86 KiB of JavaScript is downloaded but never used on this page.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 60 ms. During a long task the page ignores taps.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 549 ms of it running JavaScript. That is comfortably low.
Server response: 126 ms
126 msYour server sent the HTML in 126 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: 6.5 s
6.5 sReal visitors wait 6.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.7 s
4.7 sReal visitors see the first content after 4.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 13.7 s
13.7 sVisually, the page fills in at 13.7 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.4 s
5.4 sYour largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FAUN Gruppe Website Header-ASF”. Most of its time is resource load delay (5.5 s).
Largest content (LCP) got 30% slower for real visitors
+30%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Time to Interactive: 5.4 s
5.4 sThe page becomes fully interactive after 5.4 s. Good is under 3.8 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user INP: 116 ms
116 msReal visitors wait 116 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Tap response (INP) got 36% faster for real visitors
-36%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 171 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.032
0.032The layout barely moves while loading (CLS 0.032, good is under 0.1).
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
1 image over 500 KB
AI-Cube-Website_4.gif weighs 26.4 MB. On a phone connection a single image that size takes seconds.
1 image in older formats
1 image (26.4 MB) is 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.
Page weight: 3.7 MB in 130 requests
3.7 MBYour homepage downloads 3.7 MB in 130 requests on a phone: images 2.8 MB (35), scripts 440 KiB (43) and fonts 257 KiB (3). Under 2 MB keeps phones on slow connections fast.
4 images below the first screen load straight away
4 images further down the page (217 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
1.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.05 g of CO₂e: 125.5 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
37 text elements with low contrast
37 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
32 links without text
32 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 32 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (121 characters)
Your title is 121 characters, so Google will cut it off around 60: “FAUN Group - Hersteller für Müllfahrzeuge und Kehrmaschinen - FAUN Group - Hersteller für…”.
99 internal links, 24 external
The homepage links to 99 pages on faun.com and 24 external pages.
6 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Abfallsammelfahrzeuge, Kehrmaschinen und Lifter von FAUN: innovativ, zuverlässig, für Kommunen und Entsorger. Jetzt Pro…”.
Canonical URL set
The canonical URL is https://www.faun.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage 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.
XML sitemap found
Your XML sitemap is reachable at https://www.faun.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.
No llms.txt
There is no /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.
2 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 (731 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
/fcs, /sps and /bin-wash-package have no meta description, so Google writes the search snippet from whatever text it finds.
7 links to non-canonical URLs
Your homepage links to 7 pages by a URL that isn't their canonical one, for example /variopress, whose canonical is /variopress-hecklader-der-variable-faun. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
7 pages slow to respond
/variopress, /variopress-urban-kompakter-hecklader-faun, /variopress-kompakt-wendiger-hecklader-faun, /city, /skylift and /skyliftx and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 65 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
13 small tap targets
13 of 54 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.
Security and trust
1 link through redirect chains
1 link go through two or more redirects, for example https://www.kirchhoff-group.com/de.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
8 checks passed
Served over HTTPS
The homepage is served over HTTPS (faun.com).
Valid certificate (40 days left)
The certificate from Let's Encrypt · YR1 verifies for faun.com and is valid for another 40 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
HSTS enabled
Strict-Transport-Security is set, so browsers always use https.
http:// redirects to https
http://faun.com redirects to the secure version.
HTTP/2
The server speaks HTTP/2, so browsers load many files over one connection.
All 57 links work
All 57 links checked from your homepage (40 internal, 17 external) answered without errors; 1 did not answer within 5 s.
Domain and trust
No CAA record
faun.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
faun.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
2 checks passed
Domain is 30 years old
30 yearsfaun.com was registered in Sep 1996 through InterNetX GmbH. An established domain carries more trust with email providers and search engines.
Registered until Sep 2027
faun.com is registered until Sep 2027.
Content and conversion
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 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 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 617 words of copy
The homepage carries about 617 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Get Your Job”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Email authentication
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be faun.com is still delivered. Reports are on, so moving to quarantine is the next step.
No DKIM key on the usual selectors
We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.
Email authentication score: 65/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
1 checks passed
SPF with a strict ending (-all)
An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 a:faun.com a:mail.faun.com a:mail1.zoeller-kipper.de a:mail2.zoeller-kipper.de a:webhost.faun.com include:spf.tm…”.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- CMS
- WordPress 7.1.3
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Company
- Founded
- 1995
- Headquarters
- Osterholz-Scharmbeck
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on faun.com, including 16 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.