1/21/2024 0 Comments Joomla improve image compress![]() The amount of time saved in data transfer has a significant impact to your site's performance.ĭoes it not slow down the site? No, not really. This reduces the total size of the data transferred to the client substantially. This option makes sure that the HTML content sent by your site to the browser is compressed using the GZip (also called "deflate") algorithm. If you haven't already done so, go ahead and enable it. If there was a contest for the most-overlooked option in Joomla, Gzip Page Compression would win hands down. That should give you a sense of the site scale that would benefit from caching using a dedicated caching server. Even my own business site falls into this category, despite the fact that we're getting traffic in the order of hundreds of dozens of thousands of unique monthly visitors. Chances are that if you're reading this you do not, in fact, have this kind of site, and you're looking at speeding up a much more run–of–the–mill site. If you have a truly massive or extremely busy site it makes sense to use a dedicated memcached or Redis server as your caching backend. I agree with your sentiment, to an extent. “Heresy!” the more technically minded between you cry. ![]() It will definitely work towards making your public, non–logged-in pages faster - exactly what is most relevant for your site's search engine ranking.Īs to the caching back-end, most sites can get away with using the file caching which is similar in performance to memcached or Redis running on a decent, commercial, shared or virtualised, host - with much less memory use, therefore much cheaper to run. This can even work towards mitigating some performance lost to a pre–built, non–optimized template. When a request comes through, the page is stitched together from those pieces of cached content whenever possible. The progressive caching option is the better implementation of Joomla built-in caching, making sure that the output of each extension used to construct your page is individually cached. Go to your site's Global Configuration and set caching to "ON - Progressive Caching". I feel that people don't give it enough credit because they were used to the subpar caching experience in Joomla 1.0 and 1.5. Joomla, unlike WordPress, has a built-in caching system. Most of the time spent on the server side of a site has to do with constructing the page that will be displayed to the visitor. ![]() A few simple switches in the Global Configuration before delivering the site and a few simple server checks can make all the difference in the world. When building a site we get so caught up in the design and functionality that we forget that some very basic and fairly straightforward system settings can have a massive impact on the performance of our sites. In the second part of this series we'll dive into some of the basic things you can do in Joomla to unlock a decent amount of performance. That post was by necessity a bit generic. In the first part of this series I described why tuning the performance of your site is something you should do for both philosophical and practical reasons, as well as where to start.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |