Question: I'm developing a website based on WordPress source code through XAMPP. Sometimes I change the CSS code, scripts or something else and I notice my browser takes time to apply the modifications. This leads me to use multiple browsers to refresh one and if it doesn't apply the new styles I try the second one and it's always this.

There is some way of avoiding this problem?

Sometimes I'm changing code without noticing the previous modifications.

Answer: 
**Developer point of view**  

If you are in development mode (like in the original question), the best approach is to disable caching in the browser via HTML meta tags. To make this approach universal you must insert at least three meta tags as shown below.

```
<meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" />
<meta http-equiv="Pragma" content="no-cache" />
<meta http-equiv="Expires" content="0" />

```

In this way, you as a developer, only need to refresh the page to see the changes.
But do not forget to comment that code when in production, after all caching is a good thing for your clients.

**Production Mode**  

Because in production you will allow caching and your clients do not need to know how to force a full reload or any other trick, you must warranty the browser will load the new file.
And yes, in this case, the best approach I know is to change the name of the file.
If you want to be sure that these files are properly refreshed by Chrome for all users, then you need to have `must-revalidate` in the `Cache-Control` header. This will make Chrome re-check files to see if they need to be re-fetched. 

Recommend the following response header:

```
Cache-Control: must-validate

```

This tells Chrome to check with the server, and see if there is a newer file. If there is a newer file, it will receive it in the response. If not, it will receive a 304 response, and the assurance that the one in the cache is up to date.

If you do NOT set this header, then in the absence of any other setting that invalidates the file, Chrome will *never* check with the server to see if there is a newer version.

Here is a [blog post](https://agiletribe.wordpress.com/2018/01/29/caching-for-chrome/) that discusses the issue further.