ドメインを比較
サイト価値、トラフィック、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.
nginx.com 0
workers.dev 5
workers.dev leads in :lane
workers.dev wins this lane with stronger combined signals than :other.
Business:
workers.dev
Reach:
workers.dev
SEO:
workers.dev
Performance:
workers.dev
Trust:
workers.dev
Business
workers.dev
nginx.com
0
workers.dev
5
Value gap $11,077,861
Income gap $755
Reach
workers.dev
nginx.com
0
workers.dev
3
Visitors gap 23,957
Pageviews gap 83,849
SEO
workers.dev
nginx.com
0
workers.dev
5
Seo gap 87
Indexability gap 100
Performance
workers.dev
nginx.com
0
workers.dev
2
Performance gap 80
Trust
workers.dev
nginx.com
0
workers.dev
3
Trust gap 65
Ssl gap 1 SSL
Next Best Moves
The clearest actions to close the gap and improve this domain fastest.
nginx.com
Priority is based on the current gap, likely impact and available audit evidence.
Close the SEO score gap
SEO
87 points to match
Why: workers.dev 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 indexability signals
Indexability
100 points behind
Why: :domain is behind on crawlability or indexability checks that directly affect discoverability.
Do next: Fix robots, sitemap, canonical and index directives so the homepage is cleanly discoverable.
Strengthen on-page relevance
On-page
87 points behind
Why: workers.dev 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
80 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.
workers.dev
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.
SEO Audit Snapshot
A compact technical SEO check so users can compare on-page readiness at a glance.
0/100
Pass 2
Warn 5
Fail 4
IDX 0
ONP 0
PERF 0
TRUST 0
HTTP Status
-
Fail
Indexability
Indexable
Pass
robots.txt
Missing
Warn
sitemap.xml
Missing
Warn
Canonical URL
Missing
Warn
H1 Count
0
Fail
Title Length
0
Fail
Description Length
0
Fail
HTML lang
Missing
Warn
Viewport Meta
Missing
Warn
Image Alt Coverage
0/0
Pass
87/100
Pass 10
Warn 1
Fail 0
IDX 100
ONP 87
PERF 80
TRUST 65
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
57
Pass
Description Length
180
Pass
HTML lang
en
Pass
Viewport Meta
Present
Pass
Image Alt Coverage
0/3
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 workers.dev
A: 0 | 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 workers.dev
A: 0 | 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 workers.dev
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 workers.dev
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.
Reduce redirect chain length
MEDIUM
Impact 4
Effort M
Confidence 82%
Focus area workers.dev
A: 0 | B: 4
Why it matters: Extra redirects increase latency and can waste crawl budget.
Recommended fix: Point internal links directly to final canonical URL and keep redirects to one hop.
次の発見ルート
比較したシグナルをもとに、より広いハブページや価値の高いSEO機会セットへ進んでください。
関連ハブ