Broken website: clear cache or cookies?
Use the symptom to choose cached files or site data, understand the sign-out consequence and avoid clearing every browser record for one website.
In brief
For stale images or an old layout, start with a reload that bypasses cache or a targeted cache cleanup. For a stuck sign-in session, clearing that site’s cookies and data may help, but it can sign you out and remove local site state.
Cache stores resources such as images and scripts. Cookies and site storage can hold session and preference data. Clearing both without a reason makes it harder to know which solved the problem.
This guide uses the linked product documentation. Worked scenarios explain how to check your own result; they are not measurements of your device.
Match the cleanup to the symptom
An outdated logo after a site update is a different symptom from a login loop. For the first, compare a reload without cached resources. For the second, confirm the account and password route before considering session-data removal.
A temporary private window is another comparison, but a successful result there does not identify cookies as the only possible cause. Extensions, session state and policies can differ too.
Clear the smallest relevant scope
In desktop Chrome, open Settings > Privacy and security > Third-party cookies > See all site data and permissions. Search for the affected domain and remove its entry. In desktop Firefox, open Settings > Privacy & Security, find the browsing/site-data section, then Clear data for specific sites or Manage Data. Search for the domain, remove only the matching entry and confirm. Labels vary between browser releases.
If you use the broad browsing-data dialog for cache, inspect the selected categories. Leave passwords and unrelated history out of a cache-only test. Read the confirmation before deleting; do not click every checkbox because a troubleshooting post says so.
Documentation for these steps: Mozilla — remove cookies and site data ↗ · Google Chrome Help — remove data for a specific site ↗
Verify and stop repeating cleanup
Open the site and attempt the same action. Sign in again only on the correct domain if required. If a local list or draft disappeared, that is a consequence of deleting site storage, not proof of a new account breach.
If the failure remains, check whether another device or connection is affected and whether the service reports an outage. Repeatedly clearing all data does not fix a server that is unavailable.
Use one repeatable check
If a page’s menu looks outdated, reload without cache and check the same menu before deleting login data. If the menu updates, stop there. If sign-in keeps returning to the login screen, save any draft and confirm you can complete the account’s normal sign-in and second factor before removing that site’s data.
On LA24X, saved pages and preferences can live only in this browser. Clearing la24x.com site storage may remove that local list; it does not delete a separate server account. This is a concrete reason to distinguish a cache test from a site-data reset. Copy links you want to keep first.
A private window that works narrows the investigation but does not prove one specific cause. Check extensions and the original window’s settings next. Repeatedly deleting all browser data loses evidence without repairing an outage.
Documentation for these steps: Google Chrome Help — browsing data ↗ · Mozilla — remove cookies and site data ↗ · Google Chrome Help — remove data for a specific site ↗
Before you act
Clearing site data can remove a local draft or saved state. Make sure you can sign in again, and save anything you need before proceeding. It will not repair a service outage.
What to do next
- Save any local draft and identify whether the issue is stale appearance or session state.
- On a desktop browser, compare a cache-bypassing reload such as Ctrl+F5 where supported.
- For session trouble, use the browser’s site-data settings to remove the affected site only.
- Retry the same task once and check the service status if it still fails.
