Blazor WebAssembly Keeps Accumulating Network Data on Page Navigation

Hi Mahir Mirapakayala,

Thank you for reaching out to Microsoft Q & A forum. 

If your Blazor WebAssembly app keeps accumulating network data on navigation, here are some steps to resolve it: 

1.Use a Singleton HttpClient: Avoid creating a new instance on each request to prevent unnecessary connections. 

2.Dispose of Resources Properly: Ensure components implement IDisposable to clean up event listeners, timers, or SignalR connections. 

3.Force Cache Refresh: Append a version query string to the Blazor script to ensure the latest assets load: 

<script src="_framework/blazor.webassembly.js?version=8"></script>

Alternatively, use the Clear-Site-Data: "cache" HTTP header. 

4.Manually Clear Cache: Reload the page with window.location.reload(true); or unregister service workers: 

navigator.serviceWorker.getRegistrations().then(regs => regs.forEach(reg => reg.unregister()));

 5.Check CDN Settings: Ensure your CDN isn’t serving outdated files, which can cause stale data to persist. 

If the issue continues, try opening the app in Incognito Mode or refreshing with Ctrl+F5 to check for caching problems.     

If you have found the answer provided to be helpful, please click on the "Accept answer/Upvote" button so that it is useful for other members in the Microsoft Q&A community.        

Blazor is a SPA. There is no browser navigation, JavaScript interop updates the dom on Blazor page “navigation”. The devtools only know about real page loads.