After reading Paul Stamatious article on optimizing CSS for Wordpress I decided to give it a try and see if page loading times would benefit at all from it. I also had to check if the optimization would change the way my blog would be displayed or would throw up errors. I began by analyzing the page loading times of my blog without any optimization. The result for the frontpage was that my blog used 166K and that users with ISDN (128 Kbit) would have to wait 18.55 seconds before my site was fully loaded.
Users with T1 connections, that is 1.44 Mbps would have to wait 9.28 seconds. The figures are of course only valid if they do not use part of their download speed for other transfers at the same time. The first thing that I decided to do was to enable gzip compression in the Wordpress options in the reading tab. Before I enabled it I did a quick check that my server was actually able to gzip by using the simple phpinfo() command.
I tested the result and the page size went down almost 35%! It went down 58K to 108K total. The time users with ISDN had to wait before the full page is loaded was reduced by almost 4 seconds from 18.55 seconds to 14.80 seconds. The loading time for T1 users was reduced by 0.51 seconds to 8.77 seconds in total.
I still did not apply the optimization that Paul suggested and that is what I intended to do next. His suggestion was to gzip compress the css file as well to reduce loading time even further. I found a reference to a nice Wordpress plugin in the comments of his post. The plugin is called css-compress. It just has to be activated in the plugin tab in Wordpress. The advantage of using css-compress over Paul's method is that css compress compresses all css files even those of third parties such as those from advertisers or other plugins.
Another check reported that the total size of my blogs frontpage was again reduced by almost 10k from 108K to 98K. Loading time was again reduced by 1.17 seconds for ISDN users and 0.65 seconds for users with a T1 connection.
I was not able to witness any negative effects on my blogs design, the functions or server load. Sure it uses a little bit processing power but this should only be a problem for weak shared hosts.
Users with T1 connections, that is 1.44 Mbps would have to wait 9.28 seconds. The figures are of course only valid if they do not use part of their download speed for other transfers at the same time. The first thing that I decided to do was to enable gzip compression in the Wordpress options in the reading tab. Before I enabled it I did a quick check that my server was actually able to gzip by using the simple phpinfo() command.
I tested the result and the page size went down almost 35%! It went down 58K to 108K total. The time users with ISDN had to wait before the full page is loaded was reduced by almost 4 seconds from 18.55 seconds to 14.80 seconds. The loading time for T1 users was reduced by 0.51 seconds to 8.77 seconds in total.
I still did not apply the optimization that Paul suggested and that is what I intended to do next. His suggestion was to gzip compress the css file as well to reduce loading time even further. I found a reference to a nice Wordpress plugin in the comments of his post. The plugin is called css-compress. It just has to be activated in the plugin tab in Wordpress. The advantage of using css-compress over Paul's method is that css compress compresses all css files even those of third parties such as those from advertisers or other plugins.
Another check reported that the total size of my blogs frontpage was again reduced by almost 10k from 108K to 98K. Loading time was again reduced by 1.17 seconds for ISDN users and 0.65 seconds for users with a T1 connection.
I was not able to witness any negative effects on my blogs design, the functions or server load. Sure it uses a little bit processing power but this should only be a problem for weak shared hosts.
