Technical Consultation

Another yes, I say.


Oh. I forgot that – also – I have the following problem…


https://ibb.co/6N58Sbc


As you can see in the screenshot above, in addition to a header and a footer, created with the Elementor Header & Footer Builder plugin, precisely in an Elementor template (Hello Elementor) which, in case you don’t know, comes without these elements (neither header nor footer), in my hompage (the one you see in the screenshot), I chose to add a numerator.
The same (included in the plugin), loads (or should load), from 0 to certain numbers (*)
[(*) I have to update them but, for now they are; 249,682, 415,910 and 14,000,000]


The problem is that, from time to time, what you are seeing in the screenshot happens.
That is to say, the numerator does NOT work! (**)

[(**) And that, what you are seeing, is in an incognito window]


And this, just as I told you about the header, is also “fixed” if the visitor refreshes the page. But you and I know that this will NOT happen if said visitor does not think it is necessary.


Ergo. The numerators will remain at 0 and will generate the opposite effect to the one I am looking for (***)

[(***) This is to let them know that they actually have A LOT of employment opportunities, heh]


Finally, and regarding this last inconvenience:
If you want, you can analyze my source code to see if there is something from all the files (JS and/or CSS) that, I am;
a) Minifying + Adding to the Head + Not blocking using async and/or
b) Minifying + Adding before closing the body + Not blocking using defer and/or
c) CSS minify settings: Enable
Minify method: Minify only
Minify engine settings: Remove protected comments (does not apply when “merge only” is active)
Line break removal (does not apply when “merge only” is active)
@import handling: None
d) Loading scripts after a timeout when there is no user interaction (5s) but NO Minification (****)

[(****) The latter, of course, I do with another plugin – Flying Script – well, yours does NOT have it]

Note:

Just in case, the scripts that are in a) are NOT in b) or d) and vice versa ??

I await your comments.

Like always, thank you.

Greetings.

Hello @atutrabajo

Can you please confirm that the site in question is the URL you shared (staging)?

If so, I’ve checked your website numerous times and tried various browsers, however, every time the header looks as it should look and the counter always shows the same result (no 0’s)

SO can you please share if this is the correct website URL and the specific browser you are seeing the problem on?

Thanks!

Hello Marko. Thanks for answering.

And yes, the site in question is stage9.atutrabajo.org and, as I said, the problem is “occasional”.

This is, sometimes it happens (like the screenshots I sent you), and sometimes it doesn’t.

In fact, in an incognito browser, it works fine for me. But, when I send a link out there (for example by mail), the site that, obviously, will be seen in a “normal” browser, looks HORRIBLE.

And I understand that it is a cache issue + minified because, after a while of making a change (editing) a page or an entry, the problem is solved.

Because? Because in my W3TC I have activated the page preload in 10 pages every 10800 seconds (3 hours). And, since I have 32 pages + 8 posts (40 pages), the ENTIRE site is preloaded, every 12 hours.
But NOBODY is going to come back 12 hours later yes, the 1st. Once you enter, the site looks “ugly” and/or the numerator is set to 0.

I hope it is understood.

Greetings.

Dear friends: I am writing to inform you that, related to this ticket/problem, I think…I found the “solution”!, heh

First of all, you should know that what I “discovered” is that the “problem” was generated by myself, heh.

Because? Well. I’m going to explain…

It turns out that, in my eagerness (I would say obsession:) to “comply” with Pagespeed, I read ALL the material, there was and by proxy (Yes. The classic problem of “infodemic”, heh).

And among so many things, I found a tutorial that showed how to improve the initial response times of the server.

And for that, among many other things, he told us to go to:

And among so many things, I found a tutorial that showed how to improve the initial response times of the server.

And for that, among many other things, he told us to go to:

Cloudflare/Rules/Page Rules/Browser Cache TTL…

And on top of that, at the beginning I had given it 1 year! (*)

(*) Although later I lowered it to 6 months, heh.

So what was happening? Simple.

On the one hand, I was telling Cloudflare in Caching/Configuration to…”Respect existing headers”… and, on the other, I was telling it to keep them for 6 months, heh.

Anyway.

Ergo. What happened is, I cleaned and cleaned but, until Cloudflare “craved”, the changes in the browser were NOT reflected.

Conclusion: I removed that rule and soooo! The “problem” was fixed.

But EYE! Even so, today (which was when I realized it and that’s why I’m here, heh:) I made a small change on a page (To be more exact, I removed 2 words and added 2 emojis) and AGAIN I had the same problem.

And then? Simple.

As it turns out, until the preload does NOT (AGAIN) preload the ENTIRE page in question, the change will NOT be seen immediately.

Therefore, what needs to be done, is to Clean EVERYTHING (Minified+Media+Page) with EVERY change.

Whether this is a “nonsense” or is “giant”.

Conclusion:

Now that I know all this, whether I have to make a small or big change, I write it down and try to “put them all together”.

This way, I do the ENTIRE cleanup process (Minified/Media/Page) in one pass.

Definitely…

I just wanted to record this “discovery” in case the same thing happened/happens/will happen to someone.

I hope it’s helpful, and of course I’m assuming THIS issue is ALREADY resolved (and I’ll flag this ticket as such).

See you.