Website review, no card needed
aleksejdebus.de website review
Visit site (opens in a new tab)Reviewed 11 November 202635 issues · 71 checks
This review found 35 issues worth fixing on aleksejdebus.de, 14 of them high impact, across 71 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
73CClosest 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.4 s
0.9 s
1.3 s
1.7 s
2.1 s
2.6 s
3.0 s
3.4 s
Speed
Improve image delivery
60.9 s · 10.5 MB6 images could be 10.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 60.9 s faster on a phone.
Use efficient cache lifetimes
42.2 s · 8.6 MB30 files are served with short cache lifetimes, so returning visitors download them again (8.6 MB).
6 third-party services on the page
6 third-party services load with your homepage (Google CDN, senja.io and lindoai.com and others), adding 13.7 MB and 215 ms of main-thread time.
lindoai.com adds 47 ms
47 mslindoai.com costs a phone 47 ms of main-thread work and 12.5 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.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
300 ms · 38 KiBAbout 38 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.
JSDelivr CDN adds 21 ms
21 msJSDelivr CDN costs a phone 21 ms of main-thread work and 789 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.
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.
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.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 331 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 62.9 s
62.9 sYour largest element takes 62.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Hi! Ich bin Aleksej UI / UX Designer”.
Time to Interactive: 62.9 s
62.9 sThe page becomes fully interactive after 62.9 s. Good is under 3.8 s.
Speed Index: 11.4 s
11.4 sVisually, the page fills in at 11.4 s (Speed Index). Good is under 3.4 s.
17 images without width and height
17 images have no width and height attributes, so the layout jumps as each one loads.
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.
3 checks passed
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, 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: 13.7 MB in 122 requests
13.7 MBYour homepage downloads 13.7 MB in 122 requests on a phone: images 12.5 MB (23), fonts 847 KiB (3) and scripts 251 KiB (50). Under 2 MB keeps phones on slow connections fast.
7 images over 500 KB
7 images weigh 12.3 MB together. On a phone connection a single image that size takes seconds.
8 images far larger than shown
11.1 MB8 images are downloaded at several times the size a phone draws them, for example 76177201.png at 4,000 px wide, shown at 171 px. Resized copies would save about 11.1 MB.
10 images in older formats
10 images (12.5 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.
2 images below the first screen load straight away
2 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
logo-full-256x.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 3.9 g of CO₂ per visit
3.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.87 g of CO₂e: 464.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
2 checks passed
Every image has alt text
All 22 images in the HTML carry an alt attribute.
32 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: 32 passed and 4 failed. 2 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 canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (269 characters)
Your meta description is 269 characters; Google truncates after about 160, so the end of your pitch is cut.
7 internal links, 0 external
The homepage links to 7 pages on aleksejdebus.de and 0 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Steigern Sie jetzt ihre Conversion”.
Title: 54 characters
Your title is a healthy 54 characters: “Aleksejdebus - Conversion-optimiertes Portfolio-Design”.
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.aleksejdebus.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.aleksejdebus.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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 (366 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.aleksejdebus.de/%C3%9Cber%20mich, which answers with an error. Visitors hit a dead end and search engines drop it.
2 pages share a title
/ and https://www.aleksejdebus.de/impressum all use the title “Aleksejdebus - Conversion-optimiertes Portfolio-Design”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without an H1
https://www.aleksejdebus.de/services, https://www.aleksejdebus.de/about, https://www.aleksejdebus.de/datenschutz and https://www.aleksejdebus.de/impressum have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.aleksejdebus.de/impressum has 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.
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 4 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 177 words
The homepage has only about 177 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
1 checks passed
Analytics in place
Analytics detected: Cloudflare Web Analytics.
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.
9 other companies contacted
Loading the homepage contacts 9 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 aleksejdebus.de, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on aleksejdebus.de, including 11 speed issues, 3 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.