Blank page on your site: a founder triage decision tree

What a “blank page” usually means

A “blank page” isn’t always a literal white screen. Sometimes you get a header with no content, a spinner that never finishes, or a dashboard where the layout loads but the cards stay empty.

The mistake most founders make is trying random fixes (refreshing repeatedly, clearing everything, tweaking code) before they know what kind of problem it is. A quick triage turns a scary symptom into one clear label: browser, account, or server/build.

Before you touch anything, spend two minutes gathering signals.

Have this ready:

• The exact page URL where it happens
• One incognito/private window
• A second browser (or the same browser on another device)
• One affected account login (and, ideally, a second account)
• A short note on what you see (white screen, spinner, half-loaded layout)

What you’re trying to learn:

• Works in incognito, fails in normal mode: cookies, cache, extensions, or local browser state
• Fails across browsers/devices: build, deploy, backend, or a client-side crash affecting everyone
• Fails only for one account: permissions, user data, role/feature flags, or a user-specific API response

Example: if one founder sees a blank dashboard after sign-in but a teammate can load it, you’re already leaning toward “account-specific,” not “site down.”

Capture the basics before you change anything

Good notes fix problems faster than frantic clicking.

Write down what you expected versus what you actually saw. “Dashboard should show my projects” is actionable. “It’s broken” isn’t.

The minimum details that save hours later:

• Exact URL (copy from the address bar)
• Time it happened (include time zone if you can)
• What you expected vs what happened
• Device and browser (Mac Chrome, iPhone Safari)
• Network (home Wi-Fi, office Wi-Fi, hotspot)

Take a screenshot even if it looks like “nothing.” A white screen, a stuck spinner, and a missing header usually point to different causes.

Refresh once, then stop. Rapid refresh loops can trigger rate limits, logouts, or flip the app into a different state.

Step 1: Try incognito mode

Incognito/private mode is the fastest way to separate “my browser is confused” from “the app is broken.” It starts with a clean session.

Do this:

• Open an incognito/private window
• Paste the exact same URL
• If the page requires login, sign in and repeat the action that leads to the blank screen
• Note what happens (loads, stays blank, flashes then goes blank)
• Copy any error message exactly

How to interpret the result:

• If it works in incognito, suspect cookies (bad session), cached files (old JavaScript), local storage values, or an extension interfering.
• If it’s still blank in incognito, don’t waste time clearing caches yet. You’ve learned it’s probably not just your existing cookies.

Step 2: Try another browser (and one more device if you can)

Next, test the same URL in a different browser. Some “blank page” issues are browser-specific even when the server is fine.

Keep the test clean: same connection, same steps, no extra changes.

A simple order that works:

• Open the page in a second browser you don’t normally use
• Try a private window in that second browser
• Check the page on your phone
• If possible, test your phone on mobile data (turn off Wi-Fi)

Patterns to watch:

• Fails in only one browser: extension, blocked storage, cached asset, or browser quirk
• Fails on all browsers on the same laptop: less likely a browser-specific quirk
• Works on mobile data but not on office Wi-Fi: VPN, DNS filtering, or corporate firewall/proxy
• Fails everywhere across devices and networks: deploy/build/backend or a frontend crash hitting everyone

Keep a one-line test log so you don’t loop: “Chrome Mac (Wi-Fi): blank. Safari Mac (Wi-Fi): loads. iPhone (mobile data): loads.”

Step 3: Check if only one account is affected

Now remove “my account” from the equation.

1. Log out and load any public page first (homepage, pricing, marketing page). If public pages work but the app area is blank after login, the issue often involves authentication, permissions, or a post-login API call.

2. Compare accounts. Ask a teammate to sign in and load the same page.

3. If you can, try a brand-new test account. New accounts usually have clean data, which helps reveal whether one user record is triggering the crash.

Quick read on the outcome:

• Works for other accounts, fails only for yours: session/cookies, bad user record, role/permission bug, or a page that can’t handle your specific data
• Fails for multiple accounts: shared backend/API failure, frontend crash on a common path, or a bad deploy
• Public pages load but app pages are blank: auth flow or a post-login request failing

Example: if the dashboard is blank only for an admin account, an admin-only widget might be making a failing API call and taking the whole page down.

If it works in incognito: cookies, cache, and extensions

If incognito works, your server is probably fine. Focus on what’s different in your normal browser: stored session data, cached files, extensions, or browser privacy settings.

Start small. Fix your domain only, not your entire browser.

Safe fixes, in order

Try one change at a time and retest after each:

• Clear site data for only your domain (cookies and local storage), then sign in again
• Hard refresh (reload without using cache)
• Disable extensions, then re-enable one by one to find the culprit (ad blockers and script blockers are common)
• Temporarily disable strict tracking protection for a quick test, then turn it back on
• Try a fresh browser profile (or guest mode) to confirm it’s tied to your usual profile

What to avoid:

• Don’t “clear all browsing data” as your first move. It wipes useful clues and signs you out everywhere.
• Don’t change app code if incognito works. You’re likely chasing the wrong category of problem.

Once you find the trigger (one extension, one cookie reset, one privacy setting), write it down. That detail is usually what prevents repeats.

If it fails everywhere: likely a server or build issue

If it’s blank in incognito, in another browser, and on another device, treat it as an app issue until proven otherwise.

First, rule out a network edge case by switching networks (phone hotspot instead of office Wi-Fi). If that fixes it, suspect firewall rules, DNS filtering, VPNs, or proxies.

Next, separate “can’t reach the site” from “site loads but app doesn’t render”:

• If the domain doesn’t resolve or you can’t load anything at all, think DNS, hosting, or certificate.
• If you can see the shell (header/layout) but the main area is empty, think frontend crash or API failure.

Then look for recent changes. Blank screens often start right after a deploy, an environment variable update, an auth provider change, or a rushed config edit.

If you have access to logs, focus on the exact time you reproduced it. Common clues:

• A spike in 500 errors
• “Failed to fetch” or CORS errors
• Token verification/auth failures
• Missing environment variables during build
• Database timeouts or connection errors

Common traps that waste time

Blank pages feel urgent, so people start doing everything at once. That’s how you lose the signal.

The biggest time sinks:

• Refresh loops that change nothing and teach you nothing
• Changing multiple variables at once (clear cache, log out, disable extensions, redeploy) so you can’t tell what mattered
• Testing only with your admin account and missing a role-specific or user-data-specific failure
• Forgetting the last real change (deploy, plugin, env var update, auth setting)

A useful rule: change one thing, observe, write it down.

5-minute checklist to narrow it down

Answer these in order and record each result:

• Incognito test: does it load in a private window after signing in again?
• Browser test: does it load in a different browser?
• Account test: does it load for a different user (or a fresh test user)?
• Device/network test: does it load on a second device or a different network (hotspot is fine)?
• Evidence: do you have the exact URL, timestamp, and a screenshot?

How to act on the pattern:

• Works in incognito only: something in your normal browser is interfering (cookies, cache, extension, local storage)
• Fails in two browsers and two networks: stop local fixes and investigate deploy/build/backend/frontend crash
• Fails only for one account: focus on user-specific data, roles/permissions, and edge-case records

When you escalate, send facts: the URL, the time, the tests you ran, what you expected, what you saw, and any console error text you can copy.

Example: blank dashboard for one user vs everyone

A common situation: marketing pages load, but the dashboard goes blank right after login.

Scenario A: only one account

You see a white screen. In incognito it works. In another browser it works.

That’s a local state issue (cookie/session/cached bundle/extension) or something tied to your account settings that your normal session is reading differently. Stop once you can reproduce the pattern consistently and escalate with the evidence.

Scenario B: most users

Incognito is blank. A second browser is blank. Another device or teammate sees the same thing.

That points to a deploy/build/backend failure or a frontend crash on a common route. Don’t send guesses. Send a short reproduction note:

• Exact URL and which screen is blank
• Which tests you ran (incognito, browser, device) and the outcomes
• Whether it’s one account or multiple
• When it started and what changed recently
• Screenshot and any console error text

Next steps: escalate with clarity (and when to bring in FixMyMess)

If the blank page shows up across browsers/devices, treat it like an outage. Aim for speed and clarity, not more experiments.

Escalate immediately if:

• New sign-ups can’t complete
• Login fails for many users
• Checkout/payments fail
• The app is blank on multiple devices and networks
• The issue started right after a deploy or environment variable change

Ask for three things: what is failing, why it started, and what will be changed to fix it (plus how the fix will be verified).

If the app was generated by tools like Lovable, Bolt, v0, Cursor, or Replit, blank screens are often caused by brittle auth flows, missing or exposed secrets (env vars), or build/deployment mismatches that only show up in production. In those cases, a fast outside diagnosis can be cheaper than guessing during an incident. FixMyMess (fixmymess.ai) runs a free code audit and focuses on turning broken AI-generated prototypes into production-ready software, including logic repair, security hardening, and deployment prep.