Web best Practices

Whether they are automated on DareBoost.com or not , find in details the best practices of web performance and quality. This area is also yours, don’t hesitate to suggest us a post of your own, or a topic you would like us to write about.

On the way to HTTP/2: what to expect for front-end development?

We have announced it a couple months ago: our web performance testing tool now fully supports HTTP/2 and our best practices repository has been updated to handle the particularities of this new protocol. Now, let’s go back to the reasons of HTTP/2 emergence and talk about the major changes this protocol brings, and these old HTTP/1 best practices that we will have to give up! Continue reading

Why you should avoid using document.write, specifically for scripts injection

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?

Continue reading

HTTPs is a requirement for your website

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!)

Continue reading