Title: issues with broken internal JavaScript and CSS files
Last modified: April 4, 2020

---

# issues with broken internal JavaScript and CSS files

 *  Resolved [romeing](https://wordpress.org/support/users/romeing/)
 * (@romeing)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/issues-with-broken-internal-javascript-and-css-files/)
 * hello. After I activated your plugin (that I use in combination with Fastest 
   Cache) I got many error from the SemRush Audit. In particular it seems there 
   are several issues with broken internal JavaScript and CSS files (146 errors).
   
   an example on this page: [https://www.romeing.it/best-cocktail-bars-in-rome-for-gin-whiskey-mezcal/](https://www.romeing.it/best-cocktail-bars-in-rome-for-gin-whiskey-mezcal/)
   it results a 404 page for this CSS resource url: [https://www.romeing.it/wp-content/cache/autoptimize/1/css/autoptimize_d2dbea8fc3584d00d78ac15f8e895449.css](https://www.romeing.it/wp-content/cache/autoptimize/1/css/autoptimize_d2dbea8fc3584d00d78ac15f8e895449.css)
 * or on this page: [https://www.romeing.it/portfolio/romeing-magazine-february-2020/](https://www.romeing.it/portfolio/romeing-magazine-february-2020/)
   
   it results a 404 page for this Javascript resource url: [https://www.romeing.it/wp-content/cache/autoptimize/1/js/autoptimize_9eab299a2ae804596f62c9cb003da719.js](https://www.romeing.it/wp-content/cache/autoptimize/1/js/autoptimize_9eab299a2ae804596f62c9cb003da719.js)
 * please help me, I’m afraid this can affect my SEO
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fissues-with-broken-internal-javascript-and-css-files%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 12 replies - 1 through 12 (of 12 total)

 *  Thread Starter [romeing](https://wordpress.org/support/users/romeing/)
 * (@romeing)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/issues-with-broken-internal-javascript-and-css-files/#post-12628968)
 * maybe it’s something related to this article? [https://blog.futtta.be/2020/03/27/autoptimize-no-more-broken-pages-due-to-css-js-not-found/](https://blog.futtta.be/2020/03/27/autoptimize-no-more-broken-pages-due-to-css-js-not-found/)
 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/issues-with-broken-internal-javascript-and-css-files/#post-12629385)
 * 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](https://github.com/futtta/autoptimize/archive/beta.zip)
   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
 *  Thread Starter [romeing](https://wordpress.org/support/users/romeing/)
 * (@romeing)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/issues-with-broken-internal-javascript-and-css-files/#post-12630123)
 * 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](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](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.
 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/issues-with-broken-internal-javascript-and-css-files/#post-12630274)
 * 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?
 *  Thread Starter [romeing](https://wordpress.org/support/users/romeing/)
 * (@romeing)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/issues-with-broken-internal-javascript-and-css-files/#post-12630353)
 * ok please check my updated setting of fastest cache here: [https://www.dropbox.com/s/gs320a72oafy898/fastest%20cache%20updated.png?dl=0](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
 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/issues-with-broken-internal-javascript-and-css-files/#post-12630362)
 * > 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 🙂
 *  Thread Starter [romeing](https://wordpress.org/support/users/romeing/)
 * (@romeing)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/issues-with-broken-internal-javascript-and-css-files/#post-12630435)
 * thank you 🙂
 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/issues-with-broken-internal-javascript-and-css-files/#post-12630459)
 * you’re welcome, feel free to [leave a review of the plugin and support here](https://wordpress.org/support/plugin/autoptimize/reviews/#new-post)!
   🙂
 *  Thread Starter [romeing](https://wordpress.org/support/users/romeing/)
 * (@romeing)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/issues-with-broken-internal-javascript-and-css-files/#post-12640909)
 * 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/](https://www.romeing.it/rome-national-gallery-modern-art/)
   you will see an error.
 * any ideas how to resolve it?
    thanks again A.
 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/issues-with-broken-internal-javascript-and-css-files/#post-12640994)
 * ![](https://i0.wp.com/i.imgur.com/hMaVjwX.jpg?ssl=1)
 * 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) 🙂
 *  Thread Starter [romeing](https://wordpress.org/support/users/romeing/)
 * (@romeing)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/issues-with-broken-internal-javascript-and-css-files/#post-12641086)
 * that’s strange. This is what I see: [https://www.dropbox.com/s/djuw16vargu0kun/console.png?dl=0](https://www.dropbox.com/s/djuw16vargu0kun/console.png?dl=0)
   and these are the errors that Semrush find: [https://www.dropbox.com/s/patyio4hl3qyiqs/semrush%20errors.png?dl=0](https://www.dropbox.com/s/patyio4hl3qyiqs/semrush%20errors.png?dl=0)
 *  Plugin Author [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * (@optimizingmatters)
 * [6 years, 2 months ago](https://wordpress.org/support/topic/issues-with-broken-internal-javascript-and-css-files/#post-12641335)
 * 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](https://github.com/futtta/autoptimize/archive/beta.zip)
   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)?

Viewing 12 replies - 1 through 12 (of 12 total)

The topic ‘issues with broken internal JavaScript and CSS files’ is closed to new
replies.

 * ![](https://ps.w.org/autoptimize/assets/icon-256X256.png?rev=2211608)
 * [Autoptimize](https://wordpress.org/plugins/autoptimize/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/autoptimize/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/autoptimize/)
 * [Active Topics](https://wordpress.org/support/plugin/autoptimize/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/autoptimize/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/autoptimize/reviews/)

 * 12 replies
 * 2 participants
 * Last reply from: [Optimizing Matters](https://wordpress.org/support/users/optimizingmatters/)
 * Last activity: [6 years, 2 months ago](https://wordpress.org/support/topic/issues-with-broken-internal-javascript-and-css-files/#post-12641335)
 * Status: resolved