Title: animations.css
Last modified: July 1, 2022

---

# animations.css

 *  Resolved [Webprom Design](https://wordpress.org/support/users/webprom/)
 * (@webprom)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/animations-css/)
 * Hi!
 * Could you please stop changing animations CSS file location, I’m reusing this
   for some pages without using your plugin/editor. The last versions of the plugin
   changed it already 2 times.
 * Alternatively, can you make some settings page, where we’d be able to enable 
   the loading of CSS files on all pages?
 * Thanks.

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

 *  Plugin Author [Hardeep Asrani](https://wordpress.org/support/users/hardeepasrani/)
 * (@hardeepasrani)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/animations-css/#post-15789019)
 * Hey [@webprom](https://wordpress.org/support/users/webprom/),
 * We merged them into one file to optimize the web page speed. We won’t be changing
   the file location anytime soon now. 🙂
 *  Thread Starter [Webprom Design](https://wordpress.org/support/users/webprom/)
 * (@webprom)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/animations-css/#post-15789340)
 * thanks, but maybe better to allow the loading of CSS to all pages, to avoid future
   problems 🙂
 *  [rinart73](https://wordpress.org/support/users/rinart73/)
 * (@rinart73)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/animations-css/#post-15813668)
 * > We merged them into one file to optimize the web page speed
 * Can I suggest a plugin settings page where users will be able to toggle separate
   animations on and off? After they press “Save settings” the plugin generates 
   CSS file that only contains enabled animations. This file is then enqueued whenever
   animations are used. That way we reduce CSS file size without creating tons of
   small files.
 *  Plugin Author [Hardeep Asrani](https://wordpress.org/support/users/hardeepasrani/)
 * (@hardeepasrani)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/animations-css/#post-15813736)
 * Hey [@rinart73](https://wordpress.org/support/users/rinart73/),
 * That really won’t be needed as our own styles are pretty small and don’t make
   the CSS any much heavier than animate.css already is.
 * Also, we generate the CSS build during build process (before release) so we can’t
   separate or merge them based on options.
 *  [rinart73](https://wordpress.org/support/users/rinart73/)
 * (@rinart73)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/animations-css/#post-15813849)
 * If you were to separate them at build you would be able to join them later with
   PHP
 *  Plugin Author [Hardeep Asrani](https://wordpress.org/support/users/hardeepasrani/)
 * (@hardeepasrani)
 * [3 years, 11 months ago](https://wordpress.org/support/topic/animations-css/#post-15815209)
 * [@rinart73](https://wordpress.org/support/users/rinart73/) We can do it but it’s
   really 1kb of CSS in a 70kb file. And probably we can extract more and make it
   less than half a kb of extra CSS. The optimization done here was to stop the 
   server from making two HTTP calls instead of one. Our own CSS that we had is 
   very small as we don’t need much.

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

The topic ‘animations.css’ is closed to new replies.

 * ![](https://ps.w.org/blocks-animation/assets/icon-256x256.png?rev=2619319)
 * [Blocks Animation: CSS Animations for Gutenberg Blocks](https://wordpress.org/plugins/blocks-animation/)
 * [Support Threads](https://wordpress.org/support/plugin/blocks-animation/)
 * [Active Topics](https://wordpress.org/support/plugin/blocks-animation/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/blocks-animation/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/blocks-animation/reviews/)

 * 6 replies
 * 3 participants
 * Last reply from: [Hardeep Asrani](https://wordpress.org/support/users/hardeepasrani/)
 * Last activity: [3 years, 11 months ago](https://wordpress.org/support/topic/animations-css/#post-15815209)
 * Status: resolved