Website review, no card needed
strama-mps.de website review
Visit site (opens in a new tab)Reviewed 27 October 202626 issues · 70 checks
This review found 26 issues worth fixing on strama-mps.de, 5 of them high impact, across 70 checks. The most urgent: page weight: 5.4 MB in 68 requests. 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
87BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 902 ms |
| May 16, 2026 | 1.0 s |
| May 23, 2026 | 930 ms |
| May 30, 2026 | 925 ms |
| Jun 6, 2026 | 923 ms |
| Jun 13, 2026 | 840 ms |
| Jun 20, 2026 | 944 ms |
| Jun 27, 2026 | 944 ms |
| Jul 4, 2026 | 862 ms |
| Jul 11, 2026 | 862 ms |
| Jul 18, 2026 | 786 ms |
| Jul 25, 2026 | 759 ms |
| Aug 1, 2026 | 780 ms |
| Aug 8, 2026 | 793 ms |
| Aug 15, 2026 | 789 ms |
| Aug 22, 2026 | 883 ms |
| Aug 29, 2026 | 887 ms |
| Sep 5, 2026 | 887 ms |
| Sep 12, 2026 | 916 ms |
| Sep 19, 2026 | 867 ms |
| Sep 26, 2026 | 952 ms |
| Oct 3, 2026 | 922 ms |
| Oct 10, 2026 | 952 ms |
| Oct 17, 2026 | 995 ms |
| Oct 24, 2026 | 970 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 88 ms |
| May 16, 2026 | 84 ms |
| May 23, 2026 | 91 ms |
| May 30, 2026 | 91 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 101 ms |
| Jun 27, 2026 | 99 ms |
| Jul 4, 2026 | 90 ms |
| Jul 11, 2026 | 90 ms |
| Jul 18, 2026 | 87 ms |
| Jul 25, 2026 | 87 ms |
| Aug 1, 2026 | 89 ms |
| Aug 8, 2026 | 93 ms |
| Aug 15, 2026 | 100 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 104 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 105 ms |
| Sep 19, 2026 | 100 ms |
| Sep 26, 2026 | 108 ms |
| Oct 3, 2026 | 103 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 109 ms |
| Oct 24, 2026 | 101 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
Improve image delivery
450 ms · 568 KiB5 images could be 568 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Mobile performance score: 80
80/100Your mobile performance score is 80 (desktop: 98). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
600 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Reduce unused JavaScript
300 ms · 49 KiBAbout 49 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.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
Reduce unused CSS
280 ms · 52 KiBAbout 52 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 120 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.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 399 ms of it running JavaScript. That is comfortably low.
Server response: 41 ms
41 msYour server sent the HTML in 41 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.6 s
4.6 sYour largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 88 ms to 101 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 4.6 s
4.6 sVisually, the page fills in at 4.6 s (Speed Index). Good is under 3.4 s.
25 images without width and height
25 images have no width and height attributes, so the layout jumps as each one loads.
Time to Interactive: 4.6 s
4.6 sThe page becomes fully interactive after 4.6 s. Good is under 3.8 s.
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s 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: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 111 ms
111 msReal visitors wait 111 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 104 ms
104 msScripts block the page for only 104 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.4 MB in 68 requests
5.4 MBYour homepage downloads 5.4 MB in 68 requests on a phone: media 3.8 MB (1), images 1.3 MB (53) and scripts 117 KiB (6). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
9 KiB1 image is downloaded at several times the size a phone draws it, for example Weltkarte-STRAMA.png at 1,071 px wide, shown at 342 px. Resized copies would save about 9 KiB.
4 images in older formats
4 images (327 KiB) 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.
About 1.5 g of CO₂ per visit
1.53 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.53 g of CO₂e: 183.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 48 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 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 0 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
168 internal links, 11 external
The homepage links to 168 pages on strama-mps.de and 11 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Menschen. Maschinen. Partnerschaften.”.
Title: 37 characters
Your title is a healthy 37 characters: “Strama MPS: Strama-MPS - Strama Group”.
Canonical URL set
The canonical URL is https://www.strama-mps.de/.
Structured data in place
Structured data found: BreadcrumbList 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.strama-mps.de/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 https://www.strama-mps.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 (620 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.strama-mps.de/aktuelles is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
8 pages without a meta description
https://www.strama-mps.de/covid-19, https://www.strama-mps.de/loesungen, https://www.strama-mps.de/loesungen/karosserierohbauanlagen, https://www.strama-mps.de/unternehmen, https://www.strama-mps.de/aktuelles and https://www.strama-mps.de/unternehmen/unternehmensgruppe and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.strama-mps.de/aktuelles has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 82 found) and read each the way a search engine does.
4 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.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 14 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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 455 words of copy
The homepage carries about 455 words of visible text.
3 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 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.
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 strama-mps.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
- Analytics
- Google Tag Manager
- Hosting
- Mittwald CM Service GmbH und Co. KG
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on strama-mps.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.