Manage your Front-end Stack with WebriQ CMS

By Philippe Bodart | Created on December 20, 2016

Everyone is fed up with constant update cycles of database driven websites. The use of technology Stack of WebriQ will simplify your entire build and management process by quite a bit.

Everyone is fed up with thebs constant admin and update cycles of bulky server-dependent softwares such as Wordpress, Drupal, and Heroku. It’s time to take the headaches and monotony out of developing and making your site faster and more secure. A front-end Stack based on Javascript, API and Markup on WebriQ CMS is the obvious solution and this article is aimed at helping you step into the light much like Lanarkshire Chamber of Commerce , Gas Cerificate and many other s have done .

Regardless of where you’re coming from (Wordpress, Drupal, Heroku, etc.), WebriQ has you covered with great boiler-plate templates to get your new site up and running in a span of days.

Not only are Wordpress and other platforms like it cumbersome, annoying, and tedious to maintain but they also effect your site’s speed and security immensely. Let’s break your site’s performance and security down into seven simple factors.

Why using the WebriQ Stack and CMS system?

1. The time it takes for a full download of your HTML

Additional components, javascript and events won’t load before this happens, which affects your page load speed significantly. Not only does it frustrate the hell out of users but it also negatively affects your Google search ranking as well as increases user bounce rates and ultimately lowers conversions.

When using WebriQ Stack you significantly reduce your full download time because the assets are there already .

2. The Time To First Byte (TTFT)

The time it takes for the user’s browser to begin receiving your website also affects your page load speed significantly. Congruently this too negatively affects your Google search ranking as well as increases user bounce rates and ultimately lowers conversions.

We mitigate this by using smart CDN technology that finds the nearest server to the user and determines (based on speed, downtime, and a magnitude of other factors) which instance of your site is fastest for the user/browser viewing your site.


Google has been pushing for a more secure web. In this effort, Google is now demoting HTTP sites in favor of more secure HTTPS sites. Technically speaking, Google’s search index gives preferential ranking to sites secured with HTTPs, and takes it a step further by marking standard HTTP sites as insecure.

4. HTTP2

HTTP2 is an update to the HTTP protocol engineered to improve performance of the web with consideration for how modern web applications are built. Enabling HTTP2 will make your site load faster - better yet, it comes standard for all builds.

5. DNS lookup time

This is the time it takes to lookup your DNS and discover your site’s IP address. Much like your Time to Full Download and TTFB, this also negatively affects your Google search ranking as well as increases user bounce rates and ultimately lowers conversions.

6. HTTPS handshake time

This is the time to negotiate the encrypted connection between the browser and the secure site server. We carefully optimize this handshake to avoid effecting your sites page load speed.

7. Valid SSL certificate

To test if the SHA certificate is up-to-date, some servers use an old encryption mechanism that’s no longer secure when using HTTPS . An obsolete or broken certificate means your users will get warnings in certain browsers. Avoid these blockers and bad experiences for your users .

How can you migrate to the WebriQ Stack?

Most websites will have a single database to migrate from . Use a Wordpress to Static site converter like , Wordpress Converter. One-click WordPress plugin that converts all posts, pages, taxonomies, metadata, and settings to Markdown and YAML which can be dropped into our Static Website Generator and published on the WebriQ CMS system for editing and content updates. You can find the entire set-up guide HERE. More compIex websites that are using multiple databases can use proxying ruling as a step up solution towards a complete migration. Using proxying rules indefinitely is not an ideal solution. However, it is a great interim solution that breaks your migration into digestible phases without having to spread development time across a single massive project around redesign your server.

The benefits of Gradual Migration and decoupling the front-end from the back-end are virtually endless but to name a few:

  • You spread the risk of switching with Gradual Migration
  • Your site will load much, much faster
  • Enjoy much simpler and less-frequent maintenance
  • Easily add features without fighting complex and bloated syntax
  • Never have your front-end go down with your back-end does

  Go Back

About us

A diverse group of people coming from four continents with backgrounds in sales management, web design, open source web development, cloud based content management platforms and digital marketing.

Keep in touch

Join our newsletter to receive updates