In our latest update, we have significantly reduced the amount of data that an average page needs from the database. This may sound very technical and not very relevant, but the results are! With many pages, especially the pages with relatively little content, the loading time has decreased to 40%. And this is very relevant to your visitors (and thus to you).
The improvements are also noticeable in the front-end and back-end. The systems work faster and therefore gives you a much better user experience.
More about data storage in Webanizr on the page about data storage on our hosting website.
Each time when a visitor browses a webpage from your website, the full page will be rendered - block by block. This costs time, while most of the pages remain the same for each visitor as there are no visitor unique elements on it. Therefore it should not be necessary to render the full page again and again, but render it just one time, capture the result, and reuse this result for any future visits. This technique makes the loading of a webpage incredibly fast, and is called 'loading a page from the cache'.
A result from the cache becomes outdated when anything relevant to the cached page is changed. For example by changing or adding a menu item or image to a page. If this happens, the cache invalidates and all related pages are cleaned up from the cache. We discovered an issue where the cache was invalidated more often than necessary. As caching is a complex feature, from version 430 on we started to investigate where, when and how often the cache is cleaned up, and when possible to fix the underlying cause. We from Webanizr want every website to be fast!
Although we do not see ourselfs as an hosting company, we have to admit hosting is a big part of what we do. Hosting allows us to create fast, scalable experiences accross all platforms. Hosting allows us to control every part of every service we offer. Managing our hosting ourselfs allows us to improve our services daily.
We realized hosting is that important to us that we dedicated a seperate website to the hosting section of our business. We've just launched today and will add more content to to make our efforts in hosting more transparent.
Webanizr uses caching extensively as a tool to keep website speed at an optimum. At the same time a lot of websites build on the Webanizr platform deal with dynamic and sometimes sensitive data. Take the page where you can view or edit your personal profile for an instant. These pages should stay out of the cache at all times to prevent a security breach.
We already had a system in place that performed numerous checks to determine if a page could be cached. If you are logged in for instance, no page is cached. On top of this system we now added a microcheck system. On a very low level checks are added to detect sensitive of dynamic data that should not be cached. If such data is encountered caching for the corresponding page is disabled.
The microcheck system supports the latest front-end options. In these options you can use datanames to display data from various datasets related to the current page. This gives the designer flexibility to create dynamic pages in every detail. The microchecks help to ensure no sensitive data accidentally ends up in the cache.
One of the key factors of success of a website is the speed. In the old days pages were all static and thus fast. Nowadays most of the pages are dynamically generated, and pages that do not change often can be optimized by remembering ('caching') the content.
Caching is a very complex and intensive technique. But we succeeded in realising a reliable solution for caching dynamic pages. When you change some content on the website, or when a page contains dynamic elements like a form, Webanizr automatically detects whether it safely can use or store a cached version of the page.
Recently Google has set the bar a lot higher with the tool PageSpeed Insights. Websites that previously achieved a reasonable or high score dropped significantly in score. Google clearly found it time to increase the pressure on website builders. A challenge that we gladly accepted.