Staying anonymous with Tor without killing your speed

Tor has a reputation. People hear about it and immediately picture sluggish page loads, websites that fail to render, and a browser that feels like it has been dragged back to 2003. Some of that reputation is deserved. Tor routes traffic through three random relays across the globe, applies several layers of encryption, and rebuilds circuits every ten minutes. None of that is free.

But "slow" is not the same as "unusable." For most of what you would actually do with Tor — reading articles, posting on forums, accessing censorship-resistant news, sending sensitive messages — there are ways to bring the experience close to a normal browsing session. The trick is knowing which knobs to turn and which habits actually help.

Australian users have a few extra wrinkles to think about. Tor exit relays are heavily concentrated in Europe and North America, and the further your packets travel, the longer each round trip takes. On an average NBN connection in suburban Melbourne or Perth, you are looking at an extra 200 to 400 milliseconds of latency just from the physics of light through undersea cables. Telstra, Optus, and TPG also engage in traffic shaping on some plans during peak hours, which can hit encrypted Tor traffic harder than ordinary HTTPS. None of this is a reason to avoid Tor. It is just the playing field you are working with.

Australia's metadata retention scheme, in force since 2017, requires carriers to keep records of who connected to which IP address and when, which makes Tor bridges especially relevant here. What follows is a practical walkthrough of where the speed goes, how to tune Tor properly, when bridges matter, the habits that drain performance, and how Tor sits alongside other privacy tools.

Understanding where the speed actually goes

Before you start tweaking anything, it helps to know what you are fighting. Tor traffic passes through three hops: a guard relay, a middle relay, and an exit relay. Each hop strips one layer of encryption, so by the time your request reaches the destination, no single relay knows both who you are and where you are going. That design is what makes Tor valuable. It is also what makes it slow, because each hop adds latency and the slowest relay in the chain sets the speed for everything you do.

Cryptography is the second cost. Tor negotiates a new session key for every circuit and rotates the entire circuit roughly every ten minutes. On a desktop browser the overhead is negligible. On a five-year-old Android phone with a budget processor, it is the difference between snappy and frustrating. Knowing which device you are on changes which optimisations actually matter.

Distance matters more than people realise, especially from Australia. A request through a guard in Sydney, a middle in Frankfurt, and an exit in New York covers roughly 25,000 kilometres of fibre. Even at the speed of light in glass, that is about 130 milliseconds each way before Tor adds its own processing. Multiplied by the dozen requests a typical webpage makes, you can see why pages feel heavy. For a fuller look at how Australia's metadata regime interacts with Tor exit nodes, the rest of Twenty of Time covers the policy angle well.

Tuning your Tor browser the right way

The Tor Browser is the only client most people should be using, and it ships with sane defaults. Resist the urge to start changing things at random. There are, however, three settings that meaningfully change the experience.

Security level lives in the shield icon and ranges from Standard to Safest. Standard allows every browser feature and gives the fastest experience. Safer disables features that have been used to attack Tor users in the past, including certain fonts and some maths operations. Safest turns off JavaScript entirely. For routine privacy on Australian networks, Safer is usually the right balance. You will barely notice the difference on most pages, and you close off several known fingerprinting vectors.

Tor Browser is preconfigured to use DuckDuckGo as the default search engine, both because of its no-logging policy and because the company is based in the United States, which means your searches do not pass through any jurisdiction tied to your real identity. If you would rather avoid US-based products, switching to a European engine such as Mojeek or a self-hosted Searx instance costs nothing in speed.

Finally, pay attention to the circuit display. When a particular site feels stuck, click "New Tor Circuit for this Site" in the toolbar. Tor will rebuild the path and you will often land on faster relays within a couple of seconds. It is the single most effective speed fix most users never try.

Bridges and pluggable transports for stubborn networks

Bridges are unlisted relays. Unlike public Tor relays, their addresses are not handed out by the directory authorities, which makes them useful in two situations: when you do not want your ISP to know you are using Tor, and when your network actively blocks connections to known Tor relays. Both situations come up in Australia, particularly on corporate networks and on some university campuses in Brisbane and Adelaide that have experimented with Tor blocking.

The pluggable transport question matters once you have a bridge address. Obfs4 is the standard choice and works well in most conditions. meek-azure routes traffic through Microsoft Azure domains and is meant for places that block Tor aggressively, but it is noticeably slower. snowflake turns your connection into a WebRTC call, which can be fast where it works and unreliable where it does not. Treat the choice like a fallback chain: start with obfs4, fall back to snowflake if that fails, and only use meek when nothing else connects.

Bridges will not magically make Tor faster. They can, however, avoid the moments where ordinary Tor traffic is dropped or throttled, and they prevent your provider from passively logging that you connect to the network in the first place. That second benefit is the main reason Australian privacy-conscious users bother with them, given the metadata retention obligations local carriers operate under.

Everyday habits that keep Tor responsive

Even on a perfectly tuned setup, certain behaviours will ruin your speed. Keep Tor Browser open for one purpose at a time. A single tab pointed at your bank would not play well with twelve other tabs streaming video through hidden services. Browser bloat hits Tor harder than regular browsing because every request you make queues behind the slowest relay in the circuit. If you need a video player, close Tor entirely first.

Extensions are another problem. Tor Browser comes with NoScript and HTTPS Everywhere preinstalled and configured. Adding anything else modifies the browser fingerprint in ways that break the design. Resist the temptation to install a custom ad blocker on top. If you want fewer ads when you are not using Tor, keep a separate browser for everyday use and reserve Tor for the things that genuinely need it. A useful comparison of best ad blockers tested for regular browsers will give you a sense of which tools make sense outside Tor.

Bookmark carefully. Search engines index very few onion addresses reliably, and you will end up relying on bookmarks anyway.

Combining Tor with other privacy tools

Tor is not the whole privacy stack. It is one tool, and there are jobs it is not built for. Streaming video over Tor wastes relay operator bandwidth and gets you nothing in return. If your goal is to hide your IP from a video service while still watching comfortably, a paid VPN sits between you and the service in a way Tor never will. Conversely, if your goal is to reach a whistleblowing platform without anyone knowing you did so, Tor is the only honest answer.

Many users combine the two. The typical pattern is VPN first, then Tor, which hides Tor use from your ISP and gives you a stable entry guard. The reverse pattern, Tor first then VPN, is for users paying for the VPN with cryptocurrency who want the VPN provider to see nothing. Both work; both have trade-offs. Avoid free "Tor over VPN" browser extensions, which mostly exist to harvest credentials.

Operational security is the layer people forget. Tor cannot help if you log into a personal Gmail account while reading onion-hosted journalism about a topic connected to your day job. Compartmentalisation sounds dramatic but in practice just means separate browser profiles, separate identities, separate email aliases. Long-running habits matter more than configuration tweaks in the Tor settings panel. If you find the technical detail is wearing you down, Mike Patt's blog is a reminder that getting outside, training, and sleeping properly are part of the same project as closing third-party trackers.

Ultimately, a sensible Tor setup is the one you actually use. Anything more elaborate than a daily driver and a separate Tor profile will be abandoned within a fortnight.

For something completely different to clear your head afterwards, The Former Fat Kid is a refreshing break from privacy rabbit holes and a reminder that the best offline habits sometimes outweigh the best online ones.

The single next step is straightforward: open Tor Browser tonight, click the shield icon, switch from Standard to Safer, and browse your usual news sites for ten minutes to see whether the experience is acceptable.