section.io Website Performance and Security Blog

Back in February, Google announced an update that takes page load times into consideration as one of its signals in Google’s mobile search rankings. The change, which Google is calling the “Speed Update” began in March and will go into effect across July.

In this article we will outline what a WAF is, explore types of WAFs currently available and deployment options for those WAFs.

What is a 404 error, how does Varnish Cache handle them by default and how can it handle them? We also explore the cost of 404 Errors in this article: Cost of 404 Not Found.

Today we are pleased to announce we have closed our Series A funding round lead by Foundry Group.

We are pleased to announce today that we have added ShieldSquare Bot Mitigation and Management to section.io’s modular web optimization platform. Both section.io and Shieldsquare focus on improving the security of web applications and thier content.

One hurdle of Varnish Cache is that it is designed to accelerate HTTP, not the secure HTTPS protocol.

To maintain a well performing and highly available website, it is important to provide several layers of security. In addition to normal patching, user access management and good development hygiene, we recommend you use a combination of following to ensure your website is protected: DNS Protection HTTPS Network Protection Caching Rate Limiting And IP Blocking Web Application Firewall

The recently released top 50 people in Australian ecommerce has again demonstrated section.io’s market leadership.

Competition as an e-retailer has never been tougher. The marketplace has become so crowded that if I want to buy a boutique reindeer outfit for my dog, I have literally dozens of options. Online shoppers have an overwhelming number of choices, and even the slightest blemishes on their user experience can turn them somewhere else. One of the easiest ways to lose customers is through slow pageload times.

Announced in 2016 but postponed until now, Google has decided that all web certificates issued after April 30th, 2018 must comply with the Chromium CT Policy in order for the Chrome web browser to honor them. When Chrome visits a website with a certificate issued after this date that does not comply with the Chromium CT (Certificate Transparency) policy, it will display a full page warning notifying the user that their connection is not CT-compliant. To see what this will look like, check out this link