Sometimes an F5 refresh or clicking the refresh button in your browser will do the trick for you. However, what about changes that don't show up when you refresh?
Most of the time, clearing your browser's cache or using a Shift + F5 refresh (or shift + click) will solve the problem. If that doesn't work, clear the cache in your page builder, web host, and/or CDN.
Read on to learn about refreshing web pages in your browser, as well as other cache clearing suggestions that operate outside of your web browser.
What Is the difference Between F5 Refresh and Shift + F5 Refresh?
It ignores the cached content when refreshing. In Google Chrome, for example:
- F5 or Ctrl + R will reload the current page.
- Ctrl + Shift + R or Shift + F5 will reload your current page, ignoring cached content.
Note: Even though Chrome is used as an example here, most web browsers follow this logic.
Note 2: In browsers that don't support Shift + F5, you would need to do Ctrl + Shift + R.
Note 3: Using F5 to reload from cache may yield different results due to cache expiry.
Note 4: Using Shift + F5 usually takes longer for the web page to load since it is fully retrieving web content.
Still Not Working?
If a page refresh still isn't showing your changes, try the following:
Clear Theme/Builder Cache
Sometimes your theme or page builder caches your pages in static CSS files.
In Divi, for example, do the following:
- Go to Divi menu item in your admin dashboard.
- Under Theme Options, click on Builder.
- Click on Advanced.
- Click the button marked Clear or disable Static CSS File Generation.
You should be using caching anyway, so you can keep your page builder's caching mechanism disabled.
Clear Your Web Host's/CDN's Cache
Sometimes your web host has a built-in cache to help automate speed improvements.
In Flywheel, for example, do the following:
- Under one of your sites, Click on Advanced.
- Click the Flush Cache button to manually flush your cache.
Flywheel has the Fastly CDN built into the platform (at least from an interface integration standpoint). If you have a separate CDN, follow your specific CDN's cache clearing procedure. This part is a must as a Content Delivery Network speeds up page loads for your site’s visitors by serving cached and compressed files.
Did one of these do it for you? If so, which one? If not, why not? What did you have to do? Sound off in the comments below!