Сравнить домены
Сравнивайте ценность сайта, трафик, SEO и хостинг бок о бок.
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.
doubleclick.net 3
github.io 1
doubleclick.net leads in :lane
doubleclick.net wins this lane with stronger combined signals than :other.
Business:
github.io
Reach:
doubleclick.net
SEO:
doubleclick.net
Performance:
Balanced
Trust:
doubleclick.net
Business
github.io
doubleclick.net
2
github.io
3
Value gap $11,910,882
Income gap $9,206
Reach
doubleclick.net
doubleclick.net
3
github.io
0
Visitors gap 468,101
Pageviews gap 4,634,197
SEO
doubleclick.net
doubleclick.net
4
github.io
0
Seo gap 10
Onpage gap 25
Performance
Balanced
doubleclick.net
2
github.io
2
Performance gap 10
Mobile speed gap 8.0
Trust
doubleclick.net
doubleclick.net
1
github.io
0
Ssl gap 1 SSL
Next Best Moves
The clearest actions to close the gap and improve this domain fastest.
doubleclick.net
Priority is based on the current gap, likely impact and available audit evidence.
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.
github.io
Priority is based on the current gap, likely impact and available audit evidence.
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
10 points to match
Why: doubleclick.net 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.
Strengthen on-page relevance
On-page
25 points behind
Why: doubleclick.net 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.
Lift technical performance
Performance
10 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.
SEO Audit Snapshot
A compact technical SEO check so users can compare on-page readiness at a glance.
93/100
Pass 10
Warn 1
Fail 0
IDX 100
ONP 93
PERF 100
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
76
Warn
Description Length
138
Pass
HTML lang
en
Pass
Viewport Meta
Present
Pass
Image Alt Coverage
0/12
Pass
83/100
Pass 8
Warn 3
Fail 0
IDX 100
ONP 68
PERF 90
TRUST 65
HTTP Status
200
Pass
Indexability
Indexable
Pass
robots.txt
Found
Pass
sitemap.xml
Found
Pass
Canonical URL
Present
Pass
H1 Count
3
Warn
Title Length
139
Warn
Description Length
124
Pass
HTML lang
en
Pass
Viewport Meta
Missing
Warn
Image Alt Coverage
0/13
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 PageSpeed performance
MEDIUM
Impact 6
Effort M
Confidence 88%
Focus area Both
A: 6 | B: 6
Why it matters: Low performance can reduce rankings, engagement, and conversion.
Recommended fix: Optimize render-blocking resources, image delivery, caching, and script payload size.
Improve First Contentful Paint
MEDIUM
Impact 5
Effort M
Confidence 82%
Focus area github.io
A: 0 | B: 5
Why it matters: Slow first paint delays visible feedback for users.
Recommended fix: Reduce critical CSS/JS, inline essential styles, and improve server/cache latency.
Reduce to a single primary H1
MEDIUM
Impact 5
Effort S
Confidence 82%
Focus area github.io
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.
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.
Следующие пути исследования
Используйте сравниваемые сигналы, чтобы перейти к более широким хабам и наборам ценных SEO-возможностей.
Недавно сравнивались
Обновлено 15 seconds ago
Обновлено 19 seconds ago
Обновлено 26 seconds ago
Обновлено 29 seconds ago
Обновлено 40 seconds ago
Обновлено 48 seconds ago
Обновлено 1 minute ago
Обновлено 1 minute ago