Freek.dev

This chart shows the number of requests per second that were performed (more is better). You can see that PHP 7 can do a lot more in comparison with the other versions. Response times drop from 0.2269 to 0.0865 seconds in the production environment.

Nice benchmark-work by Tom Van Looy. It is clear that you'll benefit from impressive speed bumps when upgrading to the next major version of PHP. Tom also provides instructions on how to setup PHP7 so you can perform your own tests.

Read more

This is a "living document" in the sense that I keep posting updates, and I care about and value feedback, questions and comments I get about it. This document improves over time thanks to a joint effort.

Read more

The DOM and all additional resources don't need to be parsed, the client can already begin the download of the `screen.css` resource, without "wasting time" processing the DOM and all external resources, only to make a new request to the server to begin fetching them.

When you add this all up for all resources on a page, this can easily save 100-200ms of the total page load/paint of a website. Those are numbers that should really have you consider implementing HTTP/2.

Read more

Chrome has supported SPDY since Chrome 6, but since most of the benefits are present in HTTP/2, it’s time to say goodbye. We plan to remove support for SPDY in early 2016, and to also remove support for the TLS extension named NPN in favor of ALPN in Chrome at the same time. Server developers are strongly encouraged to move to HTTP/2 and ALPN.

Read more

Yep.

http://stackoverflow.com/questions/1868874/does-php-run-faster-without-warnings/1869185#1869185

Read more

An old, but still relevant, blogpost by Derick Rethans (of Xdebug fame) about why the @-operator should be avoided.

http://derickrethans.nl/five-reasons-why-the-shutop-operator-should-be-avoided.html

Read more

Zend Framework 3 will be an evolution from ZF2, concentrating on simplicity, reusability, and performance.

Optimizing for PHP7, and supporting PHP 5.5 seems like a good idea.

Read more

An overview of the hard- and software used by the StackExchange network to render 560 million pages views per month.

http://stackexchange.com/performance

Read more

The arrival of HTTP/2 will require a bit of re-thinking how we handle websites (and webservers), so perhaps it's time to reflect on what those changes can bring. This post is based entirely on theory (the HTTP2 spec), as HTTP/2 is hard to test today (with a lack of servers and browser support).

Read more

Patrick Dubroy explains how you can track down client-side performance problems using the Chrome Dev Tools.

http://vimeo.com/77322983

Read more

Backblaze is transitioning from using 4 TB hard drives to 6 TB hard drives in the Storage Pods we will be deploying over the coming months. With over 10,000 hard drives needing to be purchased over the next several months, the choice of which 6TB hard drive to use is critical.

Backblaze needs to store 130 TB of incoming customer data every day.

Read more

Nginx Server Configs is a collection of configuration snippets that can help your server improve the web site's performance and security, while also ensuring that resources are served with the correct content-type and are accessible, if needed, even cross-domain.

Read more

Compare load times of the unsecure HTTP and encrypted HTTPS versions of this page.

Read more

If you've been following the news, you'll have noticed that yesterday Composer got a bit of a speed boost. And by "bit of a speed boost", we're talking between 50% and 90% reduction in runtime depending on the complexity of the dependencies. But how did the fix work? And should you make the same sort of change to your projects? For those of you who want the TL/DR answer: the answer is no you shouldn't.

Read more

When creating a new website you should always use HTTPS. Here's a video recorded at Google I/O earlier this year on the why and how.

The New York Times switched to HTTPS last month. Here are their reasons for doing so:

http://open.blogs.nytimes.com//2014/11/13/embracing-https/

Read more

Perfmap consists of a bookmarklet and Chrome extension to create a front-end performance heatmap of resources loaded in the browser using the Resource Timing API.

https://github.com/zeman/perfmap

Read more

Spoiler: it's all about performance. Coming to a host near you in 2015.

http://www.infoworld.com/article/2841561/php/php-7-moves-full-speed-ahead.html

Read more

Vary is one of the most powerful HTTP response headers. Used correctly, it can do wonderful things. Unfortunately, this header is frequently used incorrectly, which can lead to abysmal hit ratios. Worse still, if it's not used when it should be, the wrong content could be delivered.

Read more