About the browser cache

Hello @atutrabajo

Thank you for reaching out and I am happy to assist you with this.
The default TTL for the HTML in Browser Cache settings is 3600s. Just to confirm, when you update the media query string and check the website in the “normal” window, does the issue persists if you hard reload the page using Ctrl + F5?
Thanks!

Hi Marko.

First of all, thanks for responding!

Having said that…

To your question. The answer is no.

That’s why I mentioned that…”it’s temporary”…

Although, you can imagine that…

I can NOT “depend” on my visitors to do that! TRUE? ??

Definitely.

Is there a way to avoid this, without it being “mandatory”…

to do F5 and/or refresh the site?

I await your comments.

From already thank you very much.

Greetings.

PS: As I already mentioned, I’m redesigning my site.

And, in that “way”, also improving the WPO (Optimization) of my site.

Ergo…
I read somewhere about “server-side caching” and accordingly turned on “object caching”.

Do you think this will help – too – with this “problem”?

P.d 2: Regarding the TTL, if you tell me that, with 3600 seconds (6 minutes) this is normal, then I don’t worry.

I understand that, perhaps, mine is pure “anxiety”.

What’s more, if you tell me that nothing else needs to be done, I believe you, heh.
Anyway, now I have few visits (10/day/average) Which means less than 1 visit every TTL (3600 seconds). But…
The idea of ??all this is – obviously – to improve this to (at least) 1000 visits/day.

And, if I succeed, would I have to “tweak” something in the TTL or simply update my changes and “pray” that visitors don’t find themselves – just – with a page without the latest changes?`

Hello @atutrabajo

Thank you for your feedback.
That hard refresh or restarting the browser is needed. The reason for this is that the Browser also has a cache and once the content is changed or any files for that matter with different strings, they need to be updated in the browser, meaning that the browser needs to fetch new files.
I would recommend that if you do any changes you do this after or before the users usually visit the page so you can ensure that no uses are on the page you are currently editing.
So this is not related to the W3TC or server-side cache, instead, it’s on the user’s end – in their browsers. This is completely normal behavior.

I hope this helps!

THanks!

Hi Marko.

Yes. Help (a little, heh!).

So what I’m doing is fine (I think:).

That is:

1) I am finishing the redesign of my site.

2) When I’m done I reupload it (through my staging service).

And this – in turn – will “imply” that…

3) ALL those assets (Pages/Posts) will NO longer have changes, heh.

Therefore, I will only have to “worry” about the new articles and/or pages that I load, right?

I await your comments.

From already thank you very much.

Greetings.

Hello @atutrabajo

Thank you for your feedback.
Yes, that is correct. And once the new or updated posts/articles are added or updated, W3TC will automatically purge the cache and the changes will be visible on the users’ end.
Thanks!

Okay. So, that’s all for now.

Again, thanks for everything.

Greetings.

Hello @atutrabajo

You are most welcome!

Thanks!

Hi Marko.
First of all, excuse my insistence. But there is something I don’t understand:
You say that…
…”The reason for this is that the browser also has a cache and once the content is changed or any files with different strings need to be updated in the browser, which means the browser needs to check for new files”. .
Me what…
…”I would recommend that if you do make any changes, you do so after or before users usually visit the page, so that you can ensure there are no uses on the page you are currently editing.”…
And that, consequently…
…”this is not related to W3TC or server-side caching, but is on the user’s end, in their browsers. This is completely normal behavior”…
Let me tell you that, last night I was adding content to one of my articles until 3am and, this morning, I saw ALL the changes made to it in an incognito window. But…
I didn’t see ANY in my normal window. Until I updated the browser.
And – honestly – I’m “afraid” that I’m doing something wrong with the browser and/or page cache.
That is, you and I know that NO visitor will search for information in – for example – Google and, when they find my article (I hope, heh), they will enter using an incognito window, heh.
And, if it is the 1st. time you enter, you will also not know if there is “something else”. So I highly doubt you’ll do F5 and/or Refresh the page.
Ergo. You are going to enter from a “common” window and, my fear is, you will NOT see the changes I have made.

Just in case, I'll pass you my numbers (Obviously, the ones with a check mark like this ? are enabled and the ones that aren't, no:) :
1) Page Cache: Enable
Page Cache Method: Disk: Basic
2) Browser Cache: Enable
3) Page Cache: General
? Cache the ticket page
Do not cache the home page
? Caching feeds: site, categories, tags, comments
? Cache SSL (HTTPS) requests
? Cache URIs with query string variables
Cache 404 pages (not found)
? Do not cache pages for connected users
Do not cache pages for the following user roles
3.1) Cache preload
? Automatically prioritize page cache
Refresh interval: 1800 seconds
Pages per interval: 10
Sitemap URL: ***/sitemap_index.xml
? Preload the post cache upon publish events

4) Browser Cache: General
? Set Last-Modified header
? Set header expiration
? Set header control cache
? Set Entity Tag (ETag)
? Set the W3 full cache header
? Enable HTTP (gzip) compression
Enable HTTP (brotli) compression
Prevent caching of objects after settings have been changed
Remove query strings from static resources
Cache exception list:
Do not set cookies for static files.
Removes the Set-Cookie header for responses.
Do not process 404 errors for static objects with WordPress
404 Error Exception List
Rewrite URL structure of objects

4.2) CSS & JS
? Set Last-Modified header
? Set header expiration
Header expiration: 15552000 seconds
? Set header control cache
Cache control policy: cache with maximum time and validation ("max-age=EXPIRES_SECONDS, public, must-revalidate, proxy-revalidate"
? Set entity tag (eTag)
? Set the W3 full cache header
? Enable HTTP compression (gzip)
Enable HTTP (brotli) compression
Prevent caching of objects after settings have been changed
Remove query strings from static resources
Disable cookies for static files
4.3) HTML & XML
? Set Last-Modified header
? Set header expiration
Header expiration: 3550 seconds
? Set header control cache
Cache control policy: cache with maximum time ("public, max-age=EXPIRES_SECONDS")
? Set Entity Tag (ETag)
? Set the W3 full cache header
? Enable HTTP compression (gzip)
Enable HTTP (brotli) compression
4.4) Media and Other Files
? Set Last-Modified header
? Set header expiration
Header expiration: 15552000 seconds
? Set header control cache
Cache control policy: cache with maximum time ("public, max-age=EXPIRES_SECONDS")
? Set Entity Tag (ETag)
? Set the W3 full cache header
? Enable HTTP compression (gzip)
Enable HTTP (brotli) compression
Prevent caching of objects after settings have been changed
Remove query strings from static resources
Disable cookies for static files

To finish a couple of things:
a) Although (as you can see), I have GZip compression enabled (both through W3TC and from my own hosting) and, in online tools where I performed checks like this; https://ibb.co/1QMRfYQ
Everything indicates that I have everything compressed, according to Pingdom Tools…
https://ibb.co/NpbHBWz
My site… Has 0 compression!
Do you know what could be causing this?
b) Just in case. Same goes for understanding brotli. That although, it does not have it enabled with you if it is with Cloudflare.
Finally and, taking into account all the above…
c) Do you have any idea if I’m doing something wrong?
I await your comments.
From already thank you very much.
Greetings.

Another yes, I say.
I forgot to tell you 2(two) things (in case you want to incorporate them into your analysis of the case):
1) On my site, I have this code installed in my function.php…
/* 10) Remove unnecessary query tags from scripts and style sheets in the header */
function _remove_script_version( $src ){
$parts = explode( ‘?’, $src );
return $parts[0];
}
add_filter( ‘script_loader_src’, ‘_remove_script_version’, 15, 1 );
add_filter( ‘style_loader_src’, ‘_remove_script_version’, 15, 1 );
Which, you will surely realize, what it does is remove the versions of the CSS and JS files.
This is because I “hate” to see WordPress (or whoever) is adding versions to my files all the time.
And because, as I could read somewhere, that helps to optimize (accelerate) my site.
2) In my Cloudflare I have…
caching
Setting
Browser cache TTL: 6 months
Which (as I also read out there), contributes to the speed of the site.
Does it have something to do with the problem that I raised?
Thanks, again.
Greetings.