Web performance testing tools like Google Page Speed or Dareboost already pointed it: injecting a script by using document.write instruction causes severe issues about websites loading time. Let’s talk about this topic one more time, as the next Chrome update to come won’t allow such scripts injections any longer. What kind of issues may you experience? Which alternatives to find?
Now that we have seen how CSP can be useful in preventing injections of content within your web pages, let’s have a look on some technical elements about CSP implementation, and a few ideas about the methodology to adopt. Continue reading
Thanks to Content Security Policy, you can protect your website from numerous vulnerabilities concerning content injection. Let’s see why and how to use that simple but powerful HTTP header, now widely supported by web browsers.
Dareboost celebrates its second anniversary ! The perfect opportunity to offer a special gift to all our users, to announce a few informations about our business development and a new arrival in the DareBoost team !
About a year ago, I have published an article about HTTPs usage growth: Chrome, Firefox and Google Search: HTTPS forcing its way. In this article I detailed some major announcements, that would probably result in pushing HTTPs forward.
Ever since, requests using HTTPs reach 25% according to HttpArchive data (compared to 15% in April 2015).
In this post, we’re going to focus on today’s results of the previous announcements, on the last changes, and especially on why you should consider HTTPs as a requirement for your website (not only for security or SEO considerations!)
It’s not usual on this blog, but today I’m going to write about a proposal that might become real, but that is still at its very early stage.
It is now more than a year since we added a recommendation about Content Security Policy with our website analysis on dareboost.com. It’s a great feature to add more security to your website, particularly to prevent your visitors from the effects of an XSS attack.
Tim Kaldec and Yoav Weiss borrowed the CSP general concept to apply it to web performance topic, proposing a new HTTP header (Content Performance Policy), allowing to declare precisely the compliance level of a given page with some web performance best practices. Then, the user agent would be responsible to ensure the effectiveness of the announced best practices. Continue reading
If you’re reading this blog, you probably know that load time matters when it comes to user experience, a lot. And it’s even a major factor determining the success of a website.
Server response time, speedindex or start render, or again fully loaded time, whatever is the metric you want to collect, your measurement method should take into account several major parameters if you want reliable results through time. Continue reading
I’d like to suggest a fundamental concept that will allow you to implement a true performance culture for your web projects: the performance budget.
It’s a kind of budget that isn’t expressed in dollars, but in seconds, megabytes or even the number of files served!