Website review, no card needed
mainka-bau.de website review
Visit site (opens in a new tab)Reviewed 23 October 202631 issues · 79 checks
This review found 31 issues worth fixing on mainka-bau.de, 11 of them high impact, across 79 checks. The most urgent: improve image delivery. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.4 s |
| May 9, 2026 | 1.5 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 82 ms |
| May 9, 2026 | 82 ms |
| May 16, 2026 | 86 ms |
| May 23, 2026 | 88 ms |
| May 30, 2026 | 89 ms |
| Jun 6, 2026 | 90 ms |
| Jun 13, 2026 | 94 ms |
| Jun 20, 2026 | 99 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 103 ms |
| Jul 18, 2026 | 102 ms |
| Jul 25, 2026 | 103 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 104 ms |
| Aug 15, 2026 | 101 ms |
| Aug 22, 2026 | 98 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 95 ms |
| Sep 12, 2026 | 95 ms |
| Sep 19, 2026 | 94 ms |
| Sep 26, 2026 | 88 ms |
| Oct 3, 2026 | 85 ms |
| Oct 10, 2026 | 87 ms |
| Oct 17, 2026 | 87 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.5 s
1.1 s
1.6 s
2.1 s
2.6 s
3.2 s
3.7 s
4.2 s
Speed
Improve image delivery
1.6 s · 772 KiB20 images could be 772 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Reduce unused CSS
1.1 s · 321 KiBAbout 321 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.4 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 65
65/100Your mobile performance score is 65 (desktop: 86). Pages that score under 90 lose visitors before the first paint.
1,526 HTML elements
The page has 1,526 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Reduce unused JavaScript
91 KiBAbout 91 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
50 ms · 18 KiB3 files are served with short cache lifetimes, so returning visitors download them again (18 KiB).
3 third-party services on the page
3 third-party services load with your homepage (FontAwesome CDN, elfsight.com and Adobe TypeKit), adding 222 KiB and 30 ms of main-thread time.
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: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 113 ms of it running JavaScript. That is comfortably low.
Server response: 54 ms
54 msYour server sent the HTML in 54 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.2 s
6.2 sYour largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Mainka realisiert Industriebau-Projekte in sicherheitskriti…”. Most of its time is element render delay (2.8 s).
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Time to Interactive: 6.2 s
6.2 sThe page becomes fully interactive after 6.2 s. Good is under 3.8 s.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 82 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 106 ms
106 msReal visitors wait 106 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.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 482 ms
482 msReal visitors wait 482 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.007
0.007The layout barely moves while loading (CLS 0.007, 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
Page weight: 2.4 MB in 58 requests
2.4 MBYour homepage downloads 2.4 MB in 58 requests on a phone: images 1.7 MB (28), stylesheets 244 KiB (9) and scripts 154 KiB (8). Under 2 MB keeps phones on slow connections fast.
24 images in older formats
24 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.
23 images below the first screen load straight away
23 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.67 g of CO₂e: 80.0 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
Unlabelled dropdowns
1 dropdown has no label.
2 text elements with low contrast
2 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 (3 elements)
All page content should be contained by landmarks: 3 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.
9 links without text
9 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.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 37 images in the HTML carry an alt attribute.
46 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: 46 passed and 7 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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.
No XML sitemap
No XML sitemap at https://www.mainka-bau.de/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
108 internal links, 10 external
The homepage links to 108 pages on mainka-bau.de and 10 external pages.
5 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “Mainka realisiert sichere Bauprojekte für Chemie, Energie und Logistik - mit Erfahrung, klaren Abläufen und hoher Arbei…”.
One H1 headline
Your main headline reads: “Wir bauen sicher – oder gar nicht.”.
Title: 58 characters
Your title is a healthy 58 characters: “Mainka Bau - Industriebau für Chemie, Energie und Logistik”.
Canonical URL set
The canonical URL is https://www.mainka-bau.de/.
robots.txt in place
robots.txt is in place.
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 https://www.mainka-bau.de/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 (993 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without a meta description
https://www.mainka-bau.de/leistungen/sonderleistungen, https://www.mainka-bau.de/kontakt, https://www.mainka-bau.de/en and https://www.mainka-bau.de/projekt/neubau-einer-statcom-umspannregelanlage have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.mainka-bau.de/en has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.mainka-bau.de/leistungen/sonderleistungen and https://www.mainka-bau.de/projekt/neubau-einer-statcom-umspannregelanlage took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
5 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
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 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 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 728 words of copy
The homepage carries about 728 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 2 email links.
Privacy and tracking
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.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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).
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 mainka-bau.de, 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
- Tailwind CSS
- 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 31 issues on mainka-bau.de, including 10 speed issues, 3 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.