What Is DNS and Why It Decides How Fast Your Sites Load

DNS translates website names into the numeric addresses computers actually use, and how fast that translation happens shapes whether a page feels instant or sluggish.

September 1, 2026

What DNS actually does

When you type a website address into your browser, that name means nothing to your computer — sites on the internet aren't found by name, they're found by numeric IP addresses like 172.217.16.142. DNS (Domain Name System) is a massive distributed database that stores "website name → IP address" pairs and hands back the right answer in a fraction of a second.

The easiest comparison is a phone book. You remember a person's name, not their number — the book fills in the number for you. Your browser remembers the site's name, and DNS fills in the address of the server where that site actually lives.

Every time you open a new page, a DNS lookup happens behind the scenes:

• your browser asks a DNS server which IP address matches the domain;
• the server looks for the answer — either in its own cache, or by passing the request further down the chain;
• the answer comes back to the browser, and only then does the page itself start loading.

This whole exchange usually takes 20–120 milliseconds, but that tiny window is exactly what separates "the page opened instantly" from "something's lagging."

Why a slow DNS server drags down your whole browsing experience

A DNS lookup is the very first step before any page loads, and if it's slow, that delay gets tacked onto every link you click, every tab you open, every image or script pulled in from another domain. A single page can trigger dozens of these lookups.

There are three common reasons DNS ends up slow:

Your ISP's DNS server is overloaded. Many internet providers cut corners on infrastructure, so their DNS servers respond with extra lag during peak hours. This is one of the hidden reasons videos and sites tend to stall specifically in the evening, when the load on your provider's network peaks — we cover this in more detail in why video buffers only in the evening.

The server is physically far away. The greater the distance to the DNS server, the longer it takes for the signal to travel there and back.

Stale cache and hops along the chain. A DNS request sometimes passes through several servers in sequence, and one slow link in that chain drags down the whole lookup.

What public DNS servers are and why people switch to them

By default, most people's DNS is set automatically to their provider's server. You can swap it out for a public DNS server instead — an open service that answers DNS queries faster and more reliably, and sometimes adds filtering for unwanted content.

The best-known free options:

Switching DNS servers takes a couple of minutes in your network settings and often makes pages load noticeably faster, especially if your provider's own DNS is slow. But there's an important limitation to keep in mind: a DNS server sees which domains you visit, even if it can't see the actual content of your traffic. Who else knows what about your online activity is covered in what your ISP can actually see about you — DNS lookups get their own section there.

How to check and speed up your own DNS

To figure out whether DNS is really the bottleneck or something else is going on, run through this quick checklist:

• Open a site that usually loads slowly for you, and pay attention to the delay before the very first render.
• Switch to a public DNS server (instructions below) and reload the same site — ideally after restarting your router or device.
• Compare: if the page opens noticeably faster right at the start, DNS was the culprit.
• If you notice no difference, the issue is more likely your connection itself or your device's load.

How to change DNS manually:

• On Windows: Network settings → adapter properties → IPv4 protocol → enter DNS addresses manually.
• On macOS: Network settings → DNS → add the server addresses.
• On smartphones: in your Wi-Fi network settings — usually next to the IP address and gateway fields.
• On your router: under WAN or DHCP settings — this applies the new DNS to every device on your home network at once.

If updating each device separately sounds like a hassle, it's smarter to change it once at the router level, or use a single connection profile across all your gadgets — we cover a similar setup approach in securing your connection across every device, and the same principles overlap with DNS configuration.

When DNS isn't actually the problem

It's worth not blaming every slowdown on DNS. If a page takes a while to load its actual content — images, video, scripts — after the page itself has already opened, that's not a DNS issue: DNS finished its job in the first few milliseconds. That kind of delay usually comes down to your connection speed, load on the website's own server, or your provider's network being busy at that particular moment.

Public Wi-Fi in cafés and airports is its own case: a slow or misconfigured DNS there isn't just a speed problem — it can also be a security risk, since DNS requests are a convenient point for intercepting or spoofing traffic. What to check before connecting to networks like that is covered in staying safe on public Wi-Fi.

The takeaway

DNS is an invisible but mandatory step before any page can load: it translates a site's name into its real address. A slow DNS server adds a delay to every single connection you make, and switching to a public one is one of the simplest, free ways to speed up how fast sites open — no need to switch providers or upgrade your plan.