Website review, no card needed
dotsource.de website review
Visit site (opens in a new tab)Reviewed 31 October 202619 issues · 88 checks
This review found 19 issues worth fixing on dotsource.de, 6 of them high impact, across 88 checks. The most urgent: page weight: 6.9 MB in 73 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
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 956 ms |
| Sep 5, 2026 | 996 ms |
| Sep 12, 2026 | 930 ms |
| Sep 19, 2026 | 906 ms |
| Sep 26, 2026 | 848 ms |
| Oct 3, 2026 | 844 ms |
| Oct 10, 2026 | 853 ms |
| Oct 17, 2026 | 868 ms |
| Oct 24, 2026 | 926 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 172 ms |
| May 23, 2026 | 179 ms |
| May 30, 2026 | 178 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 192 ms |
| Jun 20, 2026 | 195 ms |
| Jun 27, 2026 | 204 ms |
| Jul 4, 2026 | 200 ms |
| Jul 11, 2026 | 204 ms |
| Jul 18, 2026 | 200 ms |
| Jul 25, 2026 | 194 ms |
| Aug 1, 2026 | 190 ms |
| Aug 8, 2026 | 180 ms |
| Aug 15, 2026 | 171 ms |
| Aug 22, 2026 | 174 ms |
| Aug 29, 2026 | 178 ms |
| Sep 5, 2026 | 189 ms |
| Sep 12, 2026 | 183 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 163 ms |
| Oct 3, 2026 | 161 ms |
| Oct 10, 2026 | 161 ms |
| Oct 17, 2026 | 167 ms |
| Oct 24, 2026 | 172 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.0 s
1.4 s
1.9 s
2.4 s
2.9 s
3.3 s
3.8 s
dotsource.de does not allow embedding, so this is Google's rendering of the page.
Speed
Mobile performance score: 77
77/100Your mobile performance score is 77. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Improve image delivery
584 KiB7 images could be 584 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
3 third-party services on the page
3 third-party services load with your homepage (Wistia, Sentry and Mux), adding 4.3 MB and 145 ms of main-thread time.
Wistia adds 140 ms
140 msWistia costs a phone 140 ms of main-thread work and 4.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.
Reduce unused CSS
150 ms · 29 KiBAbout 29 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.
Reduce unused JavaScript
95 KiBAbout 95 KiB of JavaScript is downloaded but never used on this page.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 89 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.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 506 ms of it running JavaScript. That is comfortably low.
Server response: 136 ms
136 msYour server sent the HTML in 136 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Cumulative Layout Shift: 0.361
0.361The layout shifts by 0.361 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 6.9 s
6.9 sThe page becomes fully interactive after 6.9 s. Good is under 3.8 s.
Speed Index: 4.6 s
4.6 sVisually, the page fills in at 4.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 2.6 s
2.6 sYour largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Digitalagentur dotSource Wir sind Ihr Spezialist für digita…”. Most of its time is resource load delay (1.0 s).
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 172 ms to 172 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: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 466 ms
466 msReal visitors wait 466 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.1 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 20 ms
20 msScripts block the page for only 20 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 6.9 MB in 73 requests
6.9 MBYour homepage downloads 6.9 MB in 73 requests on a phone: media 4.3 MB (1), images 1.2 MB (25) and other files 982 KiB (6). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (406 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
62 KiB1 image is downloaded at several times the size a phone draws it, for example KI_Assistenten_agentische_KI.jpg at 1,350 px wide, shown at 414 px. Resized copies would save about 62 KiB.
1 image in older formats
1 image (406 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.
About 2.0 g of CO₂ per visit
1.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.97 g of CO₂e: 235.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
19 text elements with low contrast
19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 23 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
138 internal links, 23 external
The homepage links to 138 pages on dotsource.de and 23 external pages.
8 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “technologieoffener Ansatz ✓ agiles Projektvorgehen ✓ Von Consulting bis Implementierung ✓ erfolgreich seit 2006 ✓ Jetzt…”.
One H1 headline
Your main headline reads: “Digitalagentur dotSource”.
Title: 59 characters
Your title is a healthy 59 characters: “dotSource: Digitalagentur für Business von Mensch zu Mensch”.
Canonical URL set
The canonical URL is https://www.dotsource.de/.
Structured data in place
Structured data found: Organization.
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.dotsource.de/sitemap.xml.
AI search readiness
4 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (953 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (9 KiB, 44 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 105 found) and read each the way a search engine does.
7 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
13 of 16 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
Short HSTS lifetime
HSTS is set, but max-age is 180 days; one year is the recommended minimum.
No X-Content-Type-Options
X-Content-Type-Options: nosniff is missing, so browsers may guess file types.
2 links through redirect chains
2 links go through two or more redirects, for example https://www.xing.com/companies/dotsourcegmbh.
Deprecated X-XSS-Protection
X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.
8 checks passed
Served over HTTPS
The homepage is served over HTTPS (dotsource.de).
Valid certificate (35 days left)
The certificate from Google Trust Services · WE1 verifies for dotsource.de and is valid for another 35 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
http:// redirects to https
http://dotsource.de redirects to the secure version.
HTTP/2
The server speaks HTTP/2, so browsers load many files over one connection.
All 60 links work
All 60 links checked from your homepage (40 internal, 20 external) answered without errors.
security.txt published
A security.txt file tells researchers how to report a problem with your site.
Domain and trust
No CAA record
dotsource.de has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
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.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 646 words of copy
The homepage carries about 646 words of visible text.
4 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 1 customer or partner logo and 6 trust badges.
Direct contact links
Visitors can reach you directly: 5 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Email authentication
No DMARC policy
dotsource.de has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.
Email authentication score: 45/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
2 checks passed
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 a:mail.dotsource.de a:mail2.dotsource.de include:spf.protection.outlook.com include:spf.emailsignatures365.com i…”.
DKIM signing found
A DKIM key is published (selector “selector2”), so receivers can verify mail really came from you.
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 other company contacted
Loading the homepage contacts 1 host 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).
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- CMS
- TYPO3 CMS
- Framework
- jQuery
- Hosting
- Strato Strato Ag
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 19 issues on dotsource.de, including 10 speed issues and 4 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.