jazzminus

Hi Eric-Oliver, I have already removed the plugin because I didn’t want to invest a lot of time to fix this. In the end I used it in only a few posts. I still hope, you’ll find the error.

Danke für euren Support! ??

Ich hatte einen 400er-Fehler in der Console mit Verweis auf admin-ajax.php. Meine Autoptimize-Einstellung für eingeloggte Benutzer ist aktiviert, d. h. auch für angemeldete Benutzer wird optimiert. Wenn ich diesen Haken rausnehme, also nicht mehr für eingeloggte Benutzer optimiert wird, habe ich ebenfalls keinen Fehler mehr. Scheinbar macht das also nichts aus.
Die URL ist Packlisten.org.

Ich habe das gleiche Problem auf meiner Seite. Soeben habe ich festgestellt, dass der Fehler in der Console verschwindet, wenn ich die Checkbox bei

“Tracking ausschlie?en für …” -> Angemeldete Benutzer

deaktiviere.

It’s already done. ??

Ok, thank you very much, Frank, for your awesome support. I’ll let the Generatepress team know about the “problem file”. I should have tested excluding the floating logo earlier (Packlisten-logo-neu-60.png). I had only tested the main logo and some classes. But anyways, thank you!

Yes, that resolves the issue. So why doesn’t AO like this image? ??

No, with header-image the issue remains.

– cropped-favicon –> issue remains
– Packlisten-logo –> issue resolved
– Packlisten-Logo –> issue resolved

Does it search for this string? Because the filename of the logo is actually Packlisten-Logo-min.png. But excluding Packlisten-Logo-min or Packlisten-Logo-min.png doesn’t help.

I tried different combinations in the exclusion list:

– svg, jpg, png: issue removed
– svg: issue still there
– svg, jpg: issue still there
– svg, png: issue removed
– png: issue removed
– jpg: issue still there
– jpg, png: issue removed

So it seems that png is the decisive format. My logo is also png, but when I exclude only this file, the issue remains.

Yes, the issue persists if JS optimization is off. I installed the beta of 2.5.1 on https://spielwiese.packlisten.org. Unfortunately I see the same behaviour.

I really appreciate your effort! If there is no solution to this, I will do without lazy load or try to use another plugin to lazy load images. ??

Unfortunately I see the issue in all three cases.

Sure! To reproduce I flush all caches (WP Super Cache and Autoptimize, also the browser cache).

https://spielwiese.packlisten.org/wp-content/uploads/IMG_1213.png is Safari on first load.
https://spielwiese.packlisten.org/wp-content/uploads/IMG_1211.png resembles Safari on second load (and when refreshing again and again).

https://spielwiese.packlisten.org/wp-content/uploads/IMG_1216.png is Chrome on first load.
https://spielwiese.packlisten.org/wp-content/uploads/IMG_1217.png is Chrome on second load (and when refreshing again and again).

Yes, in Safari and Chrome.

Hm, that’s interesting! I am using Chrome and Safari on iOS 12.2 on iPhone 6. A friend showed me the issue in Chrome on Huawei with Android a few days ago.