if the page is broken when you visit it, clearing your page cache(s) should fix it.
if the pages are not *really* broken, this indeed is just an issue with Google not finding old CSS/ JS (they have their own page cache). the new option in the upcoming AO 2.7 might be able to fix that automatically. if you want you can download the beta here and run it instead of 2.6.2 to test the new experimental feature?
lastly; I see you have CSS/ JS minification active in WP Fastest Cache, do disable those options when using Autoptimize.
hope this helps,
frank
yes the pages are broken and they are still broken after clearing page cache.
I mean the url is correct what is broken is the resource url, for example:
https://www.romeing.it/wp-content/cache/autoptimize/1/css/autoptimize_d2dbea8fc3584d00d78ac15f8e895449.css
Here you can see my fastest cache setting:
https://www.dropbox.com/s/863u6pe3gqwg2xm/fastest%20cache.png?dl=0
do you think are they correct in combination with autoptimize?
thanks for your help
A.
re. WPFC: nope, you’ll have to disable all JS/ CSS related options
re. missing files: Autoptimize is not active now, so I can’t really see things breaking so hard to comment on this. do you have a staging site where you could leave things broken?
ok please check my updated setting of fastest cache here: https://www.dropbox.com/s/gs320a72oafy898/fastest%20cache%20updated.png?dl=0
why are you saying that autoptimize is not active?
anyways if the setting are now good I can launch again the audit and see if there are still broken internal JavaScript and CSS files.
thanks
ok please check my updated setting of fastest cache here:
WPFC settings look OK now.
why are you saying that autoptimize is not active?
because there was no mention of AO in the HTML source, but there is now.
anyways if the setting are now good I can launch again the audit and see if there are still broken internal JavaScript and CSS files.
sure but do keep in mind that the semrush audit is different from what is really happening on your website 🙂
Hello, I will do with pleasure.
About the broken resources the problem continues:
if you make a console inspection for example on this page (like many others):
https://www.romeing.it/rome-national-gallery-modern-art/
you will see an error.
any ideas how to resolve it?
thanks again
A.
the 3 first ones are warnings about a change in Chrome
the 4th is jquery migrate logging “i’m he-here”
the 5th one is from “youtube embed plus” logging the fact the YT API is initaited
so nothing to worry about; no real errors and the same ones are visible when AO is not active (by adding ?ao_noptimize=1 to the URL) 🙂
re. semrush; those are deleted Autoptimized files, likely due to having cleared the cache when changing settings. AO 27 will have an (experimental) option to catch 404’s and redirect to fallback CSS/ JS, if you want you can download the beta here and install that instead of 2.6.2.
re. console; only one error there, which is the admin-ajax.php call which responds with a 403 Forbidden. no idea where that originates from, I tried again but I still can’t reproduce it. maybe try to find out which of the 9 (?!) admin-ajax-ing plugins is doing that (could be due to an expired nonce, which in turn could be due to page caching, but impossible to confirm from my end)?
