7,595 domains analyzed · 20 categories · Free & instant reports

Compare Domains

Compare website value, traffic, SEO and hosting signals side by side.

Browse Rankings
Use this domain comparison to benchmark value, traffic, SEO quality, technical health and trust signals side by side.

Executive Summary

A fast head-to-head view of which domain leads in the areas that matter most.

device9.com 1 berlin.de 4
berlin.de leads in :lane
berlin.de wins this lane with stronger combined signals than :other.
Business: berlin.de Reach: berlin.de SEO: berlin.de Performance: berlin.de Trust: device9.com
Business
berlin.de
device9.com
0
berlin.de
5
Value gap $8,116
Income gap $17
Reach
berlin.de
device9.com
0
berlin.de
3
Visitors gap 533
Pageviews gap 1,865
SEO
berlin.de
device9.com
1
berlin.de
3
Seo gap 9.0
Onpage gap 20
Performance
berlin.de
device9.com
0
berlin.de
2
Performance gap 100
Trust
device9.com
device9.com
2
berlin.de
0
Trust gap 29

Next Best Moves

The clearest actions to close the gap and improve this domain fastest.

device9.com
Priority is based on the current gap, likely impact and available audit evidence.
4 priorities
Lift technical performance
Performance 100 points behind
Why: Speed or rendering signals lag behind the competing domain and may hold back SEO quality.
Do next: Improve Core Web Vitals, image delivery and frontend payload before the next refresh.
Resolve safety risk signals
Trust Gain about 24 priority points
Why: Negative safety classification can severely reduce trust and traffic.
Do next: Scan and clean malware/phishing indicators, harden CMS/plugins, and request re-evaluation.
Close the SEO score gap
SEO 9 points to match
Why: berlin.de trails the competing domain on overall SEO score and needs the fastest high-impact fixes first.
Do next: Prioritize the highest-severity audit fixes and refresh the crawl after each batch.
Improve internal linking depth
Architecture 9 internal links behind
Why: The competing domain exposes more internal links from the homepage and looks easier to crawl.
Do next: Expose more important pages through clearer internal links and navigation paths.
berlin.de
Priority is based on the current gap, likely impact and available audit evidence.
4 priorities
Resolve safety risk signals
Trust Gain about 24 priority points
Why: Negative safety classification can severely reduce trust and traffic.
Do next: Scan and clean malware/phishing indicators, harden CMS/plugins, and request re-evaluation.
Strengthen on-page relevance
On-page 20 points behind
Why: device9.com has weaker title, description, headings or content-depth signals than the competing domain.
Do next: Tighten title/description quality, heading structure and homepage content depth.
Raise trust and safety confidence
Trust 29 points behind
Why: device9.com looks weaker on trust-oriented checks such as HTTPS, SSL quality or safety signals.
Do next: Strengthen HTTPS, certificate quality and surface clearer trust signals across the site.
Expand structured data coverage
Structured data 1 schema blocks behind
Why: device9.com uses more structured data blocks, which can improve machine understanding and rich result coverage.
Do next: Add clean schema markup for the brand, organization and key page entities.
Metric device9.com Winner berlin.de
Estimated Value $62,693,663 berlin.de $62,701,779
Daily Visitors 4,057 berlin.de 4,590
Daily Pageviews 14,200 berlin.de 16,065
Daily Income $128 berlin.de $145
SEO Score 70 berlin.de 79
Indexability 100 — 100
OnPage 83 device9.com 63
Performance 0 berlin.de 100
Trust 65 device9.com 36
Coverage 90 device9.com 86
Confidence 91 device9.com 87
SEO Freshness (h) 663 device9.com 1,151
Country Ireland — Germany
TLD com — de
Category — — —
Registrar Mesh Digital Limited — —
Internal Links 95 berlin.de 104
Structured Data Blocks 1 device9.com 0
PageSpeed Mobile — — —
PageSpeed Desktop — — —
PageRank 0 berlin.de 4
Tranco Rank #6,516 berlin.de #5,183
SSL Grade A — A
Safety Status — — —

SEO Audit Snapshot

A compact technical SEO check so users can compare on-page readiness at a glance.

device9.com
70/100
Pass 9 Warn 2 Fail 0 IDX 100 ONP 83 PERF 0 TRUST 65
HTTP Status
200 Pass
Indexability
Indexable Pass
robots.txt
Found Pass
sitemap.xml
Found Pass
Canonical URL
Present Pass
H1 Count
1 Pass
Title Length
75 Warn
Description Length
170 Pass
HTML lang
en Pass
Viewport Meta
Present Pass
Image Alt Coverage
73/73 Warn
berlin.de
79/100
Pass 9 Warn 2 Fail 0 IDX 100 ONP 63 PERF 100 TRUST 36
HTTP Status
200 Pass
Indexability
Indexable Pass
robots.txt
Found Pass
sitemap.xml
Found Pass
Canonical URL
Present Pass
H1 Count
2 Warn
Title Length
72 Warn
Description Length
115 Pass
HTML lang
de Pass
Viewport Meta
Present Pass
Image Alt Coverage
0/23 Pass

Top Levers Across Both Domains

Shared high-impact improvements pulled from the latest recommendations and audits.

Resolve safety risk signals
CRITICAL Impact 24 Effort L Confidence 94% Focus area Both
A: 24 | B: 24
Why it matters: Negative safety classification can severely reduce trust and traffic.
Recommended fix: Scan and clean malware/phishing indicators, harden CMS/plugins, and request re-evaluation.
Improve image ALT coverage
HIGH Impact 8 Effort M Confidence 84% Focus area device9.com
A: 8 | B: 0
Why it matters: Missing ALT text reduces accessibility and image search context.
Recommended fix: Add concise descriptive ALT text for informative images and empty ALT for decorative assets.
Reduce to a single primary H1
MEDIUM Impact 5 Effort S Confidence 82% Focus area berlin.de
A: 0 | B: 5
Why it matters: Multiple H1 tags can blur content hierarchy.
Recommended fix: Keep one main H1 and move secondary section titles to H2/H3.
Add structured data
MEDIUM Impact 5 Effort M Confidence 80% Focus area berlin.de
A: 0 | B: 5
Why it matters: Structured data improves entity clarity and rich-result eligibility.
Recommended fix: Implement relevant JSON-LD schema types (Organization, WebSite, Product, Article, etc.).
Optimize title length
MEDIUM Impact 5 Effort S Confidence 88% Focus area Both
A: 5 | B: 5
Why it matters: Overly short or long titles can lower click-through and relevance quality.
Recommended fix: Target about 20-70 characters and front-load core keywords.