Optimize .onion Service Performance and Speed

Start with optimizing the Tor daemon itself. These torrc settings can improve circuit establishment and descriptor availability:

# /etc/tor/torrc — Performance optimizations
HiddenServiceDir /var/lib/tor/my_service/
HiddenServicePort 80 127.0.0.1:8080
HiddenServiceVersion 3

# Increase number of introduction points (default 3, max 20)
HiddenServiceNumIntroductionPoints 6

# Enable single-hop rendezvous if server identity is public
# (reduces latency by ~40% but reveals server location)
# HiddenServiceSingleHopMode 1
# HiddenServiceNonAnonymousMode 1

# Connection padding — reduces latency fingerprinting
ConnectionPadding 1

# Optimize circuit creation
CircuitBuildTimeout 30
LearnCircuitBuildTimeout 1

Increasing HiddenServiceNumIntroductionPoints from the default 3 to 6 provides more paths for clients to reach your service, reducing the chance of hitting an overloaded or distant introduction point. This is especially effective for services with global audiences.

The single-hop mode (HiddenServiceSingleHopMode) cuts latency significantly but reveals your server's IP to the Tor network. Only use this if your server identity is already public and you care more about speed than anonymity.

Every additional HTTP request adds a full Tor circuit round-trip. Minimize requests by combining and inlining assets:

# Nginx performance configuration for Tor
server {
    listen 127.0.0.1:8080;

    # Enable gzip compression
    gzip on;
    gzip_vary on;
    gzip_comp_level 6;
    gzip_types text/plain text/css application/json application/javascript
               text/xml application/xml image/svg+xml;

    # Enable Brotli if available (better compression)
    # brotli on;
    # brotli_comp_level 6;

    # Aggressive caching for static assets
    location ~* \.(js|css|png|jpg|gif|ico|woff2|svg)$ {
        expires 1y;
        add_header Cache-Control "public, immutable";
        add_header Vary "Accept-Encoding";
    }

    # Enable keepalive connections
    keepalive_timeout 65;
    keepalive_requests 100;

    # Send small files in one TCP packet
    tcp_nopush on;
    tcp_nodelay on;
    sendfile on;
}

Compression is especially important for Tor — every byte saved reduces transfer time across the high-latency Tor circuit. At gzip level 6, text-based assets are typically compressed by 70-80%, which translates directly to faster page loads.

Design your application with Tor's high latency in mind. Each HTTP request adds 2-6 seconds of round-trip time, so minimizing requests is the single most impactful optimization:

• Inline critical CSS and JavaScript — Embed the styles and scripts needed for initial render directly in the HTML. This eliminates extra round trips for above-the-fold content.
• Lazy load below-fold content — Only load images and scripts when the user scrolls to them. This reduces initial page weight and time to interactive.
• Use HTTP/2 server push — If you have an SSL certificate for your .onion, HTTP/2 push can preemptively send critical assets alongside the initial HTML response.
• Implement application-level caching — Use Redis or in-memory caches to serve dynamic content without hitting the database on every request.
• Paginate heavily — Serve smaller pages with fewer resources. A page with 5 images loads much faster over Tor than one with 50.

Measure performance from the user's perspective by testing with Tor Browser. Use the browser's network inspector to identify the slowest resources and prioritize those for optimization. Target under 10 seconds for initial page load, which is achievable for well-optimized .onion sites.

AnubizHost deploys Tor hidden services on NVMe SSD storage with multi-core processors and generous RAM, ensuring the server-side component of your .onion site is never the bottleneck. Our pre-configured Nginx includes gzip compression, connection pooling, and aggressive caching out of the box.

Our offshore servers in Iceland, Romania, and Finland offer low-latency connectivity to major Tor relays. Pay with Bitcoin, Monero, or other cryptocurrencies — no KYC, no identity verification. Our team optimizes Tor configuration for your specific workload, ensuring your .onion site delivers the best possible performance within Tor's constraints.