WEBO Site SpeedUp completely automates any quantity of CSS and JavaScript files merging. Also for CSS files recursive structure of @import
rules of any complexity is calculated. Also inline code is parsed and merged, this can significantly decrease HTML pages’ size.
Powerful mix of WEBO Site SpeedUp performance options allows you to easily manage balance between performance and cache integrity. Here you can choose either to check files’ modification time or not, or just disable check for cache integrity – this completely eliminates HDD requests while page load and greatly improve performance, and much more.
WEBO Site SpeedUp incorporates a large number of gzip techniques. They include .htaccess
and ob_gzhandler
usage, static gzip (to prevent CPU wasting) and optional gzip check via cookies (to defeat firewalls). Also the product supports all font types and has advanced support for old and tricky browsers. Minify rate here is up to 88%.
Unobtrusive JavaScript logic allows you to completely eliminate JavaScript blocking behavior on your website *. You can manage placement of merged JavaScript file to achieve the best load speed and move counters, ads, and widgets to the end of the document.
A quick algorithm is used to remove excessive symbols from CSS files, or complete CSS Tidy logic (to extremely minify them). To minify JavaScript files you can apply JSMin (by default), or YUI Compressor (if java is available), or even Packer.
.htaccess
for ApacheWEBO Site SpeedUp has a large predefined set of rules to tune Apache usage for your website. These rules include mod_gzip
or mod_deflate
+ mod_filter
for gzip, mod_mime
+ mod_rewrite
for static gzip, mod_expires
or mod_rewrite
for client side caching, and mod_headers
+ mod_setenvif
for improved backward compatibility.
By default all static files are cached for 10 years. To force cache reload either GET parameter, or new file name (what provides complete proxy caching support) is used. Additionally you can set client side caching for HTML files and their conditional (ETag) caching.
There can be a grand effect from server side caching for your website — it can load up to 50x faster. WEBO Site SpeedUp has several layers of server side caching, and you can use any number of them. Particularly there can be cached minified CSS and JavaScript files, their gzipped version, parts of HTML documents, or even complete web pages.
CSS Sptires technology is completely cross browser and allows you to significantly reduce number of CSS images on your website. This don’t need any additional work to add meta information to CSS files for parsing — WEBO Site SpeedUp parses CSS rules and uses them to create combined images. Additionally all images are optimized via smush.it.
data:URI
(+ mhtml
)There is one more approach to merge CSS images besides CSS Sprites technology. It’s combined data:URI
+ mhtml
approach. In this case all CSS images are included to resource file and are loaded all together. .cur
, .htc
, .eot
, .ttf
, .otf
, .svg
files are excluded. Also there is optional CSS files separation and ability to load resource file on DOMready
event.
In addition to automated website acceleration WEBO Site SpeedUp has few manual optimization tools. You can prepare statically compressed files (.gz versions for static gzip) and optimized images (file size reduction 5-60%).
WEBO Site SpeedUp allows you to use various CDN services compeltely automatically. It also introduces its own CDN service that improves static assets download speed for the most of your clients.
WEBO Site SpeedUp is being tested and working for a large amount of different server environments — they include PHP4/5 as an Apache module or CGI, Denwer, VPS / VDS, shared hosting, collocation, and even cloud hosting (i.e. Media Temple). Also there is complete PHP4 backward compatibility for old servers.
At the bottom line WEBO Site SpeedUp installation can be protected via .htpasswd
, and any installation folder can be used. Also you can use plugins API to perform automation for any additional server side optimization actions.
* By enabling ‘Include merged JavaScript file before </body>
‘, ‘Move advertisement…’, ‘Move counter calls…’, ‘Move JavaScript informers calls…’ options all external JavaScript includes for supported patterns (Amazon Ads, eBuzzing, BlogBang, Google Analytics, Google AdWords, Google Connect, Google Search, Facebook Connect, Yandex.Metrica, Yandex.Direct, LiveInternet, SpyLog, HotLog, Rambler Top100, Rating@Mail.ru, bigmir)net, hit.ua, I.UA, 1Gb.ua, Number One Counter, OpenX, Begun, Odnaknopka, AddThis, Reformal, Novoteka) will be moved to </body>
without any damage to their functionality. If you don’t have any other JavaScript on your pages — content will be loaded before any client side logic. This avoids blocking scripts behavior.
Testimonials
Daiv (wordpress.org), 2010
All testimonials