Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →A page can finish loading with a successful HTTP response and still display nothing. The browser may receive HTML but fail to run JavaScript, load a stylesheet or script, call an API, or insert the application into the DOM. Local cookies, extensions, DNS, VPNs, security software, server errors, database failures and stale CDN caches can all create the same white screen.
Use the workflow below to identify whether the fault is limited to your browser, device, network, the website’s front end, or its server. If you own the site, the owner checklist covers the additional checks needed to distinguish an empty application from a genuine page.
First, establish how wide the problem is
- Verify the address. Check the spelling, protocol (
httpversushttps), path and any query string. Reload once. - Test another site. If several unrelated sites fail, start with your connection, router, DNS, VPN or security software. If only one site is blank, continue with site-specific tests.
- Record the scope. Note the browser and version, operating system, device, network, exact URL and time. This information makes later support much faster.
A blank result on one device is usually a profile, extension, network or security-layer issue. A blank result on multiple devices and networks is more likely to be a site, hosting, CDN or application problem.
Fixes for visitors, in the order to try them
1. Open a private window
Open the same URL in an Incognito window in Chrome or a private window in another browser. Private browsing uses a separate profile and normally prevents installed extensions from modifying the page. If the site works there, return to the normal window and disable extensions one at a time, starting with ad blockers, script blockers, password managers and privacy tools. Remove only that site’s cookies and cached files rather than wiping every saved login.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →2. Perform a hard reload
A normal reload can reuse a damaged JavaScript bundle or stylesheet. In Chrome, open Developer Tools, hold the reload button, and choose Empty Cache and Hard Reload. This is useful after a site deployment, but it will not repair a server that is returning empty HTML.
3. Try another browser, device and network
Test the URL in Firefox or Edge, then on a phone or another computer. Switch from Wi-Fi to cellular data or a different trusted network. A result that changes with the network points toward DNS, VPN, firewall, antivirus or router filtering; a result that is blank everywhere points toward the website or its hosting.
4. Check the system clock and security software
An incorrect date or time can make certificate validation fail even when the address is correct. Set the device clock to automatic time and timezone, then retry. Temporarily pause a third-party antivirus web shield or firewall only long enough to test, and restore it immediately afterward. If the page works only when protection is disabled, add a narrowly scoped exception or ask the security vendor for guidance.
5. Inspect the Console
In Chrome, press Ctrl+Shift+I (Windows/Linux) or Cmd+Option+I (macOS), select Console, reload, and look for red errors. An uncaught exception can stop a single-page application before it renders. Messages about an undefined variable, a failed module, Content Security Policy (CSP), CORS, or a blocked script identify different fixes; copy the complete message and the file and line number.
Free tools Windows power users keep installed
One-click scans. No signup required.
6. Inspect Network requests
In Developer Tools, select Network, enable Preserve log, reload, and filter by JS, CSS and Fetch/XHR. Look for requests that are red, stuck, redirected unexpectedly or returning an HTML error page instead of the expected JavaScript or JSON. Check the status, response headers, response body, request URL and timing. A missing bundle, a 403 caused by permissions, a 404 caused by an incorrect build path, a certificate failure, or an API request blocked by CORS can each leave the screen empty.
7. Check DNS and connection errors
ERR_NAME_NOT_RESOLVED means the hostname could not be resolved, so investigate DNS, the router, VPN or the domain’s records. Connection timeouts and resets can be caused by an unstable network, filtering software, an overloaded origin or a service outage. Compare the result on another network before changing DNS settings; changing them blindly can hide the real fault.
8. Escalate with usable evidence
When contacting the site’s operator, send the exact URL, UTC timestamp, browser and version, device and network, a screenshot, the Console output and a saved Network HAR file. In Chrome’s Network panel, right-click the request list and choose Save all as HAR with content. Include whether private browsing, another browser, another device or another network changed the result.
What a blank page means for site owners
Start by separating transport from rendering. A 200 response proves that an HTTP request completed; it does not prove that the intended content was generated or displayed.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsConfirm the origin response
- Request the origin directly and record the status, redirects, response body, content type, content length and cache headers.
- Open the returned HTML as text. Confirm that the expected root element, server-rendered content, script tags and stylesheet links are present.
- Compare the origin response with the public CDN URL. If the origin is correct but the public response is old or empty, investigate cache keys, invalidation and edge rules.
A command-line capture helps preserve evidence:
curl -i -L https://example.com/Replace the example URL with the affected address. Keep the output with the timestamp; it shows redirects and headers that a screenshot cannot.
Read application and server logs
Check web-server access and error logs, application logs, deployment output and process health at the time of the failure. Look for template or server-side-include errors, missing environment variables, permission failures, out-of-memory events and database connection errors. A CMS can emit an almost empty document when a theme, plugin, query or database connection fails.
Verify every front-end dependency
- Check that script, stylesheet, font and image paths match the deployed directory and capitalization. A path that works on a case-insensitive development machine can fail on a case-sensitive server.
- Confirm JavaScript and CSS files are served with the correct MIME types and are not being replaced by an HTML login or error page.
- Review CSP headers, SRI hashes, CORS response headers and authorization requirements. A policy that blocks the main bundle can produce a white screen without a server error.
- Check API base URLs, authentication, DNS names and TLS certificates used by browser-side requests.
- Confirm that the build output actually contains the entry module and that the server fallback does not rewrite asset requests to the application shell.
Reproduce the rendered page
Use the browser Console and Network panels with a clean profile, then inspect the DOM after scripts run. Google Search Console’s URL Inspection and Rich Results Test can reveal loaded resources, rendering exceptions and the HTML that a crawler receives. A page that looks fine in source but is empty in the rendered DOM has a client-side failure; a page that is empty in both places has a server, template or deployment problem.
Rule out a soft 404
Google describes a soft 404 as a URL that tells users the page does not exist while returning HTTP 200. An empty application shell, generic error message or missing route can therefore be excluded from search even though monitoring reports success. Return a real 404 for missing content, or return complete content with 200 for a valid route. Test both the status and the rendered result.
Recommended Free Tools
Diagnose by layer
| Layer | Clues | Next action |
|---|---|---|
| Browser profile | Works in a private window or another browser | Remove the site’s data and disable extensions individually; update the browser. |
| Device or network | Fails on one machine or connection; DNS, timeout or certificate errors | Check DNS, VPN, firewall, antivirus, router and system time. |
| JavaScript or assets | Console exceptions; failed script, stylesheet or API requests | Correct build paths, runtime errors, CSP, CORS, MIME types and dependencies. |
| Server or application | Empty HTML, 5xx responses, template, database or include errors | Inspect logs, CMS output, database health and server configuration. |
| CDN or cache | Origin works but the public URL is blank or stale | Compare headers and bodies, purge the affected key and correct cache rules. |
Common symptoms and targeted fixes
White screen with no visible error
Look at the first Console error, not the last one. A missing runtime dependency or exception during application startup often causes every later message. Restore the failing bundle, fix the first exception and reload without the old cache.
HTML arrives but styles and scripts are 404
Inspect the generated URLs and deployment base path. Correct relative-versus-absolute paths, filename capitalization and CDN asset prefixes. Purge stale HTML only after the new assets are available; otherwise users can receive a shell that references files that do not exist.
API calls fail while the shell loads
Check the request’s status, CORS headers, credentials and response body. A frontend that assumes a successful JSON response may render nothing when it receives a 401, 403, HTML error page or malformed payload. Handle that state explicitly and show a visible error.
Only search crawlers see an empty page
Compare the rendered DOM and resource access for the crawler and a normal browser. Check robots rules, authentication gates, user-agent handling, JavaScript compatibility and server-side rendering. Use URL Inspection to see what Google could load.
Only the CDN URL is blank
Fetch the origin and edge responses at the same time. Compare Age, ETag, cache-status headers, redirects and response bodies. Purge the specific object, then verify that the edge can reach the origin and that an error response was not cached as a successful page.
Performance, reliability and evidence practices
- Keep a minimal static fallback or server-rendered error state so a failed JavaScript bundle does not become an entirely white screen.
- Deploy HTML and its referenced assets atomically, or use versioned filenames so an old shell never points to removed files.
- Monitor a real rendered check in addition to HTTP status. A 200-only probe cannot detect an empty DOM or a JavaScript crash.
- Capture Console logs, HAR files, response headers and rendered HTML for a failing request. These artifacts let support teams distinguish browser, edge and origin faults without guesswork.
- When changing DNS, CDN rules or security policies, test from a second network and keep rollback information available.
Or skip the browser setup
If you need a repeatable screenshot while investigating a blank page, ScreenshotNeo can capture the URL through one request. It accepts consent banners before capture and removes more than 60 known consent platforms, newsletter popups and chat widgets; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and the response identifies the result with X-Page-Verdict and X-Billed headers. Its MCP server provides take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients.
See the parameter details in the ScreenshotNeo documentation. Replace the URL with the page you are diagnosing:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);The free plan includes 1,000 screenshots a month with no card. Paid plans start at $5 for 3,000 screenshots; every feature is included on every plan. Create a free ScreenshotNeo account to capture the failing page without configuring a local browser.
Frequently Asked Questions
Can a blank page be caused by an ad blocker even when the site is trusted?
Yes. Blockers can match a script, API hostname or stylesheet by pattern. Testing a private window or a clean browser profile isolates that possibility without disabling protection system-wide.
Should I clear all browser data to fix a white screen?
Usually no. Remove the affected site’s cookies and storage first. Clearing all data signs you out everywhere and can destroy useful diagnostic state.
What should I send a hosting provider first?
Send the exact URL, UTC time, browser and network, whether the origin differs from the public URL, and the Console, HAR and response-header evidence. That lets the provider route the issue to DNS, edge, application or origin support.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
