This Week in Website Performance

This Week in Website Performance is a weekly feature of the blog. It summarizes recent articles about website performance. How to make yourweb site better, how to improve your users experience when they come to your website and how to optimize the overall experience. Why? Because your friends at care.

The Right Stuff: Breaking the Page Speed Barrier with Bootstrap

Author: Dan Riti.

If you have ever wondered what it takes to get a perfect PageSpeed score, this article is for you. Inspired by a talk about the need for speed, Dan Riti wondered what it takes to get a score of 100 and set out to find out. Read this article to learn more about how well the basic performance tweaks improve performance, as well as some more advanced strategies for dealing with above and below the fold optimisations. The 5 tweaks made to the test site reduced DOMContentLoaded from 833 ms to 151 ms.

Linux performance tuning tips for MySQL

Author: Alexander Rubin.

If you have a website, you have data. This is often held in a MySQL database on a linux host. Tuning tips for that environment are delivered in this short blog post. The basics of filesystem, memory and CPU are touched on.

Measuring network performance with Resource Timing API

Author: Ilya Grigorik

W3C Resource Timing API can provide detailed insight into network timing of each resource loaded on a page. This is critical information to help focus efforts to improve site performance. If you are curious about how long it takes for your favourite font, library, or other resource to load, this is the tool for you. You can easily keep tabs on all internal and external resources, whether they are served directly or through a CDN.

How to Improve the Performance of Drupal Sites

Author: Sridhar Pandurangiah.

Drupal is a popular Content Management System (CMS). This article covers several ways to improve performance of a drupal based website. There are tips specific to Drupal, as well as how to handle bots and other crawlers that might be consuming too many resources. The author’s environment is apache on CentOS and some tips are specific to apache and/or linux.