Website review, no card needed
durst-group.com website review
Visit site (opens in a new tab)Reviewed 26 October 202632 issues · 81 checks
This review found 32 issues worth fixing on durst-group.com, 8 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.8 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 110 ms |
| May 9, 2026 | 114 ms |
| May 16, 2026 | 111 ms |
| May 23, 2026 | 108 ms |
| May 30, 2026 | 110 ms |
| Jun 6, 2026 | 108 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 114 ms |
| Jun 27, 2026 | 116 ms |
| Jul 4, 2026 | 117 ms |
| Jul 11, 2026 | 117 ms |
| Jul 18, 2026 | 116 ms |
| Jul 25, 2026 | 114 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 115 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 130 ms |
| Aug 29, 2026 | 134 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 143 ms |
| Sep 19, 2026 | 141 ms |
| Sep 26, 2026 | 144 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 139 ms |
| Oct 17, 2026 | 137 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
Reduce unused JavaScript
2.4 s · 660 KiBAbout 660 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
5,489 HTML elements
The page has 5,489 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
900 ms · 793 KiB16 files are served with short cache lifetimes, so returning visitors download them again (793 KiB).
Mobile performance score: 66
66/100Your mobile performance score is 66 (desktop: 86). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Facebook and Cookiebot and others), adding 1.4 MB and 729 ms of main-thread time.
Google CDN adds 306 ms
306 msGoogle CDN costs a phone 306 ms of main-thread work and 734 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
150 ms · 198 KiBAbout 198 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
150 ms · 168 KiB5 images could be 168 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 115 ms. During a long task the page ignores taps.
Minify JavaScript
26 KiB26 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 410 ms
410 msYour server sent the HTML in 410 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.3 s
11.3 sYour largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 18.1 s
18.1 sThe page becomes fully interactive after 18.1 s. Good is under 3.8 s.
Speed Index: 5.9 s
5.9 sVisually, the page fills in at 5.9 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 110 ms to 137 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
9 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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 141 ms
141 msReal visitors wait 141 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 731 ms
731 msReal visitors wait 731 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 139 ms
139 msScripts block the page for only 139 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 3.1 MB in 67 requests
3.1 MBYour homepage downloads 3.1 MB in 67 requests on a phone: scripts 1.6 MB (25), images 716 KiB (20) and other files 358 KiB (12). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (261 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 0.9 g of CO₂ per visit
0.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.88 g of CO₂e: 105.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
All page content should be contained by landmarks (81 elements)
All page content should be contained by landmarks: 81 elements on the page fail this check, rated moderate by axe-core.
8 form fields without a label
8 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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
Title is short (11 characters)
Your title is only 11 characters: “Durst Group”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
339 internal links, 80 external
The homepage links to 339 pages on durst-group.com and 80 external pages.
6 checks passed
Meta description: 88 characters
Your meta description is 88 characters: “Durst Group - world-leading manufacturer of digital printing and production technologies”.
One H1 headline
Your main headline reads: “Durst Group celebrates 90 years of innovation with the Durst NEXT Technology Festival in Brixen”.
Canonical URL set
The canonical URL is https://www.durst-group.com/.
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.durst-group.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 (2,258 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.durst-group.com/llms.txt (12 KiB, 74 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.durst-group.com/en/career has no <title>, so Google invents the link text in results.
6 pages share a title
/, https://www.durst-group.com/en, https://www.durst-group.com/de, https://www.durst-group.com/it, https://www.durst-group.com/es and https://www.durst-group.com/fr all use the title “Durst Group”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.durst-group.com/en/career has no meta description, so Google writes the search snippet from whatever text it finds.
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.durst-group.com/durst90, whose canonical is https://www.durst-group.com/en/durst90. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://www.durst-group.com/durst90, https://www.durst-group.com/en/printing-systems, https://www.durst-group.com/en/applications, https://www.durst-group.com/en/inks, https://www.durst-group.com/en/software-solutions and https://www.durst-group.com/en/support and 9 others have 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 108 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
6 broken images
6 images failed to load on a phone, for example https://www.durst-group.com/#.
114 small tap targets
114 of 134 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “UPDATE_FILTER_VIEWS is not defined”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
A 14-field form
Your longest form asks for 14 fields (0 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 1,102 words of copy
The homepage carries about 1,102 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 >”.
3 calls to action
The homepage has 3 calls to action, for example “Learn more >”, “Contact” and “Subscribe”.
Analytics in place
Analytics detected: Google Tag Manager, Matomo and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Tag Manager, Hotjar, LinkedIn Insight and Meta Pixel (measured from a US location before any click). A consent tool (Cookiebot) 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).
21 other companies contacted
Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 durst-group.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager | Matomo
Company
- Founded
- 1936
- Headquarters
- Brixen
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on durst-group.com, including 13 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.