Website review, no card needed
markgraph.de website review
Visit site (opens in a new tab)Reviewed 21 October 202632 issues · 78 checks
This review found 32 issues worth fixing on markgraph.de, 9 of them high impact, across 78 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
80BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.5 s
3.1 s
3.8 s
4.4 s
5.0 s
Speed
Improve image delivery
9.4 s · 1.8 MB39 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.4 s faster on a phone.
Reduce unused JavaScript
7.8 s · 734 KiBAbout 734 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.8 s faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Vimeo, website-files.com and Cloudflare CDN and others), adding 21.8 MB and 506 ms of main-thread time.
Vimeo adds 188 ms
188 msVimeo costs a phone 188 ms of main-thread work and 19.2 MB 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.
Use efficient cache lifetimes
900 ms · 163 KiB14 files are served with short cache lifetimes, so returning visitors download them again (163 KiB).
Mobile performance score: 66
66/100Your mobile performance score is 66 (desktop: 75). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 75 KiBAbout 75 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Render-blocking requests
450 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
website-files.com adds 127 ms
127 mswebsite-files.com costs a phone 127 ms of main-thread work and 2.2 MB 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.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 70 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
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: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 25.3 s
25.3 sYour largest element takes 25.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Wir verwenden Cookies, um Inhalte und Anzeigen zu personali…”.
Time to Interactive: 25.4 s
25.4 sThe page becomes fully interactive after 25.4 s. Good is under 3.8 s.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 33 ms
33 msScripts block the page for only 33 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 21.9 MB in 128 requests
21.9 MBYour homepage downloads 21.9 MB in 128 requests on a phone: other files 18.0 MB (46), images 2.2 MB (49) and scripts 1.5 MB (23). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (30 KiB) 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.
4 images below the first screen load straight away
4 images further down the page (123 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.2 g of CO₂ per visit
6.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.20 g of CO₂e: 743.9 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
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 (23 elements)
All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.
20 links without text
20 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 58 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
38 internal links, 13 external
The homepage links to 38 pages on markgraph.de and 13 external pages.
7 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “1986 gegründet, gestaltet Atelier Markgraph analog-digitale Marken- und Kulturräume, die kommunizieren und zur Kommunik…”.
One H1 headline
Your main headline reads: “StepinsidetheStory”.
Title: 41 characters
Your title is a healthy 41 characters: “Atelier Markgraph – Step Inside The Story”.
Canonical URL set
The canonical URL is https://www.markgraph.de/.
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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.markgraph.de/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing name, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.markgraph.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 (324 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://www.markgraph.de/projekt/2025-mercedes-benz-auf-der-iaa-mobility---ein-markenauftritt-zwei-standorte has no <title>, so Google invents the link text in results.
2 pages share a title
/ and https://www.markgraph.de/en all use the title “Atelier Markgraph – Step Inside The Story”. 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.markgraph.de/projekt/2025-mercedes-benz-auf-der-iaa-mobility---ein-markenauftritt-zwei-standorte has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages with very little text
https://www.markgraph.de/4d-years and https://www.markgraph.de/quarterly have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 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.
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.
Best practices
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
12 of 12 tappable elements near the top are at least 24 px.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 367 words of copy
The homepage carries about 367 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “FRAME Book”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
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 (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, 2 of them by other companies (measured from a US location before any click).
15 other companies contacted
Loading the homepage contacts 15 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 markgraph.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
- Webflow
- Analytics
- Google Analytics | Google Tag Manager
Company
- Founded
- 1986
- Headquarters
- Frankfurt
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 markgraph.de, including 14 speed issues, 2 SEO issues and 5 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.