Title: Optimization logging?
Last modified: September 1, 2016

---

# Optimization logging?

 *  Resolved [Dead Account](https://wordpress.org/support/users/xoroshiro/)
 * (@xoroshiro)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/optimization-loggin/)
 * The optimization logging is great!
 * Just wondering though, how does this affect performance? Would it be relevant
   in the future to have an option to disable it?
 * [https://wordpress.org/plugins/fast-velocity-minify/](https://wordpress.org/plugins/fast-velocity-minify/)

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

 *  Plugin Author [Raul P.](https://wordpress.org/support/users/alignak/)
 * (@alignak)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/optimization-loggin/#post-7506386)
 * I replied to your review, but basically:
 *     ```
       If you had to disable both merging on css and javascript, then most functionality has been disabled.
   
       The child theme should have not been removed, unless it's exactly the same as the parent theme (I've seen this happening before, where the child css file, has the same exact url as the parent).
   
       Have you tried the latest 1.0.1 version?
       Also, did you check the logs and does the child css style show on the list somewhere on one of those css files?
   
       If you would like me to have a look at your theme, let me know.
   
       It works fine with caching, all files are made static anyway.
   
       In terms of cpu load, it's mostly disk and network based (open, merge, send to api, write to cache) and once done, it stays there until there's a need for an update.
   
       There are a few fields in the options table, all prefixed.
       You could remove those from the database, but the plugin only deletes the cache files.
   
       I took that approach because
       1) the data that is saved is very small (basically yes or no) and
       2) if you accidentally disable the plugin, you don't need to redo all settings again (but I might add an option to delete the options soon).
       ```
   
 *  Plugin Author [Raul P.](https://wordpress.org/support/users/alignak/)
 * (@alignak)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/optimization-loggin/#post-7506388)
 * Additionally, the logging you see is just a simple text file that is created 
   during the minification process.
 * When we are minifying, we already know wich files we are processing anyway, so
   might as well save that information to a text file and load it on the admin area
   with ajax.
 * Should have nearly zero impact on performance as it’s also only generated once
   per minification.
 *  Thread Starter [Dead Account](https://wordpress.org/support/users/xoroshiro/)
 * (@xoroshiro)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/optimization-loggin/#post-7506395)
 * Thanks for the detailed reply. Got your message.
 * I hear what you are saying about removing DB options. I’m relatively new to WordPress,
   and have been trying out alot of plugins. Usually, I install them, and within
   a minute or so, decide they are not for me and delete them. The thing is many
   of them leave their settings behind, often with no prefix, so I end up with a
   large set of ophaned options (have started taking backups often). Like I say,
   I’m relatively new to WP, so had assumed that it would be possible to remove 
   options on delete rather than de-activate, but perhaps this is not so. Anyway,
   I think an option to remove would be a good future addition.
 * Sure you could look at my theme. Thanks! My site is here:
 * [http://kuiper.zone](http://kuiper.zone)
 * Note, that I’m updating it alot right now. Or I can send you the ccs and function.
   php. Need some way of sending it to you though. If this is appropriate, can I
   contact you via fastvelocity?
 *  Thread Starter [Dead Account](https://wordpress.org/support/users/xoroshiro/)
 * (@xoroshiro)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/optimization-loggin/#post-7506396)
 * PS. My parent theme is Sydney.
 *  Thread Starter [Dead Account](https://wordpress.org/support/users/xoroshiro/)
 * (@xoroshiro)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/optimization-loggin/#post-7506450)
 * Will do. Actually, the Java script merging seems to be working now. Still a problem
   with CS merging.
 *  Plugin Author [Raul P.](https://wordpress.org/support/users/alignak/)
 * (@alignak)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/optimization-loggin/#post-7506576)
 * Hi again,
 * Have you seen the logs file on the “Optimization Status” ?
 * It shows the 2 stylesheets being merged, with the child theme after the parent
   theme css, so it’s working.
 * However, I noticed there was a bug with the google fonts optimization and decided
   to replace google clousure with JSshrink (faster).
 * I also changed the html minification a bit to be safer (still working on it).
 * Take a look at version 1.0.2 and let me know if you have any issues with it.
 *  Plugin Author [Raul P.](https://wordpress.org/support/users/alignak/)
 * (@alignak)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/optimization-loggin/#post-7506577)
 * I’m marking this as solved, as your original question was about performance.

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

The topic ‘Optimization logging?’ is closed to new replies.

 * ![](https://ps.w.org/fast-velocity-minify/assets/icon-128x128.jpg?rev=1440946)
 * [Fast Velocity Minify](https://wordpress.org/plugins/fast-velocity-minify/)
 * [Support Threads](https://wordpress.org/support/plugin/fast-velocity-minify/)
 * [Active Topics](https://wordpress.org/support/plugin/fast-velocity-minify/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/fast-velocity-minify/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/fast-velocity-minify/reviews/)

 * 8 replies
 * 2 participants
 * Last reply from: [Raul P.](https://wordpress.org/support/users/alignak/)
 * Last activity: [9 years, 11 months ago](https://wordpress.org/support/topic/optimization-loggin/#post-7506577)
 * Status: resolved