Amazing Plugin

  • Most “intelligent” one around.
    You can really feel page speed influence when activating plugin. On default settings, just plugin activated.

    Some quick stats:

    CSS = all separate files 1.2 MB
    CSS & Fast Velocity Minify = 967 KB
    CSS Fast Velocity Minify & GZIP (mod_deflate) = 118 KB

    JS = all separate files 303 KB (without theme JS files)
    JS & Fast Velocity Minify = 247 KB + 277 KB theme JS files not touched by plugin (hardcoded in theme)
    JS Fast Velocity Minify & GZIP (mod_deflate) = 151 KB + 89.7 KB theme JS files not touched by plugin (hardcoded in theme)

    So, shortly.
    CSS files 1.2 MB, to 118 KB with FVP and mod_deflate.
    JS files 303 KB, to 151 KB with FVP and mod_deflate.
    (Can appear as not much gain without mod_deflate. But remember to many HTTP requests make page load slower, or at least feels like it loads slower)

    Website is one testing ground for different plugins and code snippets, that is why so many JS, CSS files. But as such it is perfect ground to test power of Fast Velocity plugin.
    Using some other theme that properly enqueue JS files results can be much better.

    Those are incredible results.

    Allways use Apache mod_deflate module, better results than GZIP in my case anyway, nothing scientific, (or mod_gzip.c) to really feel speed improvements with this plugin.

    And do not overdo by insisting to include all JS (or CSS) files, if you have problems with display and functions. Google does not punish if not all files are minimized and combined, not at all. It is expected today to have many JS, CSS files on website.

    Use it together with “Expire headers”, mod_expires.c Apache module. If you are afraid webhoster will complain for high CPU usage on shared hosting.

    Code for .htaccess file, to be used with Fast Velocity plugin:

    <IfModule mod_deflate.c>
  # Compress HTML, CSS, JavaScript, Text, XML and fonts
  AddOutputFilterByType DEFLATE application/javascript
  AddOutputFilterByType DEFLATE application/rss+xml
  AddOutputFilterByType DEFLATE application/vnd.ms-fontobject
  AddOutputFilterByType DEFLATE application/x-font
  AddOutputFilterByType DEFLATE application/x-font-opentype
  AddOutputFilterByType DEFLATE application/x-font-otf
  AddOutputFilterByType DEFLATE application/x-font-truetype
  AddOutputFilterByType DEFLATE application/x-font-ttf
  AddOutputFilterByType DEFLATE application/x-javascript
  AddOutputFilterByType DEFLATE application/xhtml+xml
  AddOutputFilterByType DEFLATE application/xml
  AddOutputFilterByType DEFLATE font/opentype
  AddOutputFilterByType DEFLATE font/otf
  AddOutputFilterByType DEFLATE font/ttf
  AddOutputFilterByType DEFLATE image/svg+xml
  AddOutputFilterByType DEFLATE image/x-icon
  AddOutputFilterByType DEFLATE text/css
  AddOutputFilterByType DEFLATE text/html
  AddOutputFilterByType DEFLATE text/javascript
  AddOutputFilterByType DEFLATE text/plain
  AddOutputFilterByType DEFLATE text/xml

  # Remove browser bugs (only needed for really old browsers)
  BrowserMatch ^Mozilla/4 gzip-only-text/html
  BrowserMatch ^Mozilla/4\.0[678] no-gzip
  BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
  Header append Vary User-Agent
</IfModule>
    • This topic was modified 7 years, 7 months ago by Stagger Lee.
    • This topic was modified 7 years, 7 months ago by Stagger Lee.
    • This topic was modified 7 years, 7 months ago by Stagger Lee.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Stagger Lee

    (@stagger-lee)

    It is my advice to plugin author to add options to insert mod_deflate (or mod_gzip) and mod_expires options in .htaccess file, as options in plugin settings.

    Maybe just some code to detect if those Apache modules are enabled on hosting first. When User is visiting plugin settings page.

    You can maybe put some warning text about higher CPU usage on shared hostings.

    mod_expires takes care of it. But if some few freaks decide to disable browser cache, for any strange reason, it can make problems So better with warning.

    Plugin Author Raul P.

    (@alignak)

    @stagger-lee not all systems use apache, so .htaccess files do not work in those cases. These settings, should be added either manually or by a cache plugin, such as w3tc. The main purpose of FVM is only to merge and minify css and js files.
    But maybe I’ll add this to the faqs, thanks.

    @stagger-lee thanks for the review. FVM can only capture those js and css files that have been enqueued (as you said), but some others are preemptively excluded due to incompatibilities known (see the faqs).
    You can further increase speed by using nginx and gzip static.
    I wouldn’t recommend apache for speed, but that’s the default in many servers… so the deflate option is a good solution.

    Thanks

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Amazing Plugin’ is closed to new replies.