You open a page you visit all the time and something is off. The layout has collapsed into a stack of plain text, a video shows a spinning wheel that never resolves, or the checkout button just sits there doing nothing when you click it. Your first thought is that the site is down, but it loads perfectly on your phone or a friend’s laptop. The site is fine. A setting in your browser is quietly filtering out the parts that make it work.
When a website looks broken in your browser, the cause is usually a privacy or display setting doing its job a little too well, not a bug on the site. Strict tracking protection, blocked cookies, and aggressive extensions are the modern culprits, and the fix is almost always a small, reversible change for that one site. Here are eight settings to check, and exactly how to undo each without lowering your guard everywhere else.
The 8 Settings to Check
- Strict tracking protection: blocks scripts a page needs.
- Blocked third-party cookies: break logins and embeds.
- An aggressive content blocker: hides page elements.
- JavaScript turned off: leaves pages blank or static.
- Forced dark mode: inverts colors and images.
- HTTPS-Only mode: blocks mixed content on older sites.
- Data saver mode: skips images and heavy scripts.
- A stuck zoom level: overlaps and overflows text.
First, Rule Out the Basics
Before you touch privacy settings, do the ten-second checks. Try the page in a private or incognito window, which loads without your extensions and with fresh cookies, and try it in a second browser. If it works in either, the problem is a setting or an add-on, not the site.
A hard refresh, pressing Ctrl and F5, or Command, Shift, and R on a Mac, also clears a stale cached version that can render oddly. If none of that helps, work down the list below, and change one setting at a time so you know which one was the culprit.
1. Strict Tracking Protection
Modern browsers ship with tracker blocking, and the strict level can be overzealous. Firefox’s Enhanced Tracking Protection on Strict, Brave’s Shields, and Edge’s strict tracking prevention block third-party scripts, and some sites use those very scripts for logins, videos, comments, and embedded content, so the page arrives half-built.
The fix is per-site, not global. Click the shield or lock icon in the address bar and turn protection down or off for that one site, then reload. On Firefox’s Enhanced Tracking Protection you can switch a single site to Standard while leaving everything else locked down.
2. Blocked Third-Party Cookies
Blocking third-party cookies is great for privacy and rough on some features. Embedded logins, cross-site single sign-on, shopping carts loaded from another domain, and some payment widgets rely on third-party cookies, so with them blocked a page can fail to log you in or show an empty embedded box.
Rather than allowing third-party cookies everywhere, add an exception for the specific site. Both Chrome and Firefox let you list sites that are allowed to use third-party cookies, so you keep the protection on by default and open a narrow, removable hole only where a site genuinely needs it.
3. An Aggressive Content Blocker
Ad and content blockers are the most common single cause of a mangled page. An extension like a broad filter list can hide more than ads, removing layout elements, breaking image galleries, or stopping scripts the page needs to render, which leaves gaps and misaligned blocks.
Click the extension’s icon and pause it or add the site to its allowlist, then reload. If the page comes back to life, the blocker was the culprit, and you can keep it on elsewhere. Custom or outdated filter rules are especially likely to break sites, so review those if breakage is frequent.
4. JavaScript Turned Off
Some privacy setups disable JavaScript, and most modern sites simply will not work without it. If you or an extension like a script blocker turned JavaScript off, interactive pages load as a blank frame, a static shell, or a message asking you to enable scripts.
Open your browser’s site settings for that page and confirm JavaScript is allowed, or re-enable the site in your script-blocking extension. Because so much of the web depends on it, a globally disabled JavaScript setting is one of the most disruptive, so allow it per site where you trust the page.
5. Forced Dark Mode
Dark mode is easy on the eyes until a browser forces it onto sites that were not built for it. Chrome has an experimental flag that auto-darkens web contents, and when it guesses wrong you get unreadable text, inverted images, and controls that vanish into the background.
If pages look strangely inverted or washed out, open the browser’s experimental flags page and turn off the auto dark mode option, then restart the browser. Experimental flags in general can cause odd rendering, so resetting them to default is worth trying when a site looks visually wrong rather than missing pieces.
6. HTTPS-Only Mode
Forcing secure connections is smart, but it trips up older sites. HTTPS-Only mode blocks content loaded over plain HTTP, so on a site that still serves some images or scripts insecurely, those pieces are blocked and the page renders with holes or missing media.
When a page shows a security warning or loads partway, the browser usually offers a “continue to site” or “allow insecure content” option for that page. Use it only on sites you trust, and keep HTTPS-Only mode on generally, since most of the modern web supports it without issue.
7. Data Saver Mode
Data saver and lite modes trade quality for bandwidth, and it shows. To cut data use, these settings can skip images, downscale media, or block heavier scripts, so a page arrives with blank spaces where pictures should be or features that never load.
If images are missing or the site feels stripped down on a phone especially, look for a data saver, lite, or reduce-data setting and turn it off, then reload. It is a helpful mode on a tight mobile plan, but it is a frequent reason a site looks incomplete rather than truly broken.
8. A Stuck Zoom Level
Sometimes the page is fine and the zoom is fighting it. A zoom level cranked well above or below 100 percent, or a high minimum font size, can push a responsive layout into its narrow mobile view on a wide screen, overlap text, or cut off buttons at the edges.
Reset it fast by pressing Ctrl and 0, or Command and 0 on a Mac, which returns the page to 100 percent. If text still looks oversized and overlapping everywhere, check for a minimum font size setting in the browser’s appearance options and set it back to default.
Menu names and the exact location of these settings vary by browser and version, and they move between updates. Use these as a map rather than exact clicks, and search your specific browser’s help if a setting is not where described. Change one thing at a time so you can undo it cleanly.
Frequently Asked Questions
Why does a website look broken in my browser but fine on my phone?
Because a setting or extension on that browser is filtering the page. Strict tracking protection, blocked third-party cookies, an ad blocker, or disabled JavaScript can remove parts a site needs, while your phone lacks those. Test the page in a private window, which disables extensions, and in a second browser to confirm it is a setting rather than the site.
How do I fix a website that shows only plain text with no formatting?
Unstyled plain text usually means the page’s stylesheet or scripts were blocked or failed to load. Do a hard refresh with Ctrl and F5, then try a private window. If it renders there, an extension or strict tracking protection is blocking the CSS or JavaScript, so pause your content blocker for that site or lower tracking protection for it and reload.
Does blocking third-party cookies break websites?
It can. Blocking third-party cookies protects your privacy but can break embedded logins, cross-site sign-on, and some carts and payment widgets that rely on them. Instead of allowing them everywhere, add the specific site to your browser’s list of sites allowed to use third-party cookies, keeping the block on by default and opening a narrow exception only where needed.
Ad blocker vs tracking protection: which breaks sites more?
Both can, in different ways. An ad blocker extension often breaks layout and hides elements because its filter lists remove more than ads. Strict tracking protection built into the browser tends to break logins, videos, and embeds by blocking third-party scripts. Disable each one at a time for the affected site to see which is responsible, then re-enable it elsewhere.
How do I check if my browser is the reason a site is broken?
Open the page in a private or incognito window, which runs without extensions and with fresh cookies. If it works there, an extension or a setting is the cause. Then try a different browser to rule out a browser-specific setting. From there, disable content blockers and lower privacy settings for that one site until it renders correctly.
The Bottom Line
When a familiar site suddenly looks broken, your browser is usually the one that changed, not the site. Confirm it with a private window and a second browser, then work down the list, from tracking protection and cookies to content blockers, dark mode, and zoom, changing one setting at a time. The goal is a surgical per-site exception, not switching off your privacy protections across the board. For more on taming settings that quietly break things, browse YouGottaRead’s Tech section, including our guide to app permissions that break after an update and the privacy toggles worth checking on a smart TV.
