We all know slow sites suck. According to research by Amazon, customers buy more when a site is responsive. Google ranks fast sites better.

Using a WordPress case study, I’ll take you on a journey through the jungle of web page performance. You’ll learn to discern the many factors that are important in performance. I’ll show you the techniques, tricks and tools used to overcome slowness.

You’ll learn about image, script and stylesheet optimization, roundtrip minimization and why it’s important. In addition, you’ll discover a unique tool that allows you to do all that automatically.

After this talk you will be able to confidently measure a website’s performance, and diagnose the reasons for it being slow. You’ll know what to fix and how, and make your customers happy.

From a technical perspective, there are a lot of highly entertaining surprises regarding what can be done with PHP features, such as output buffering and HTML parsing, as well as in the browser: reordering DOM events and changing the way scripts and stylesheets are loaded.

Comments

Please login to leave a comment

Excepted to hear how to optimize php code, not html rendering. IMHO, it is a problem of the frontend team

Maybe it is good enough for wordpress portfolio sites, but I don't think this library will work for real world applications.

Also as mentioned in other comments I expected tips on how to optimize the code and not a preview of html post processor

I really liked this presentation. Although (as per some comments) the presentation is not about the code optimization, it is still important and useful to do this kind of stuff (script, images and CSS optimization) from the backend

I knew what I was getting into before the talk and have already used PhastPress so for me it was interesting to learn more about the motivation and how it was developed.

The delivery was solid and Albert's easy going style makes even writing a custom html5 parser to sound fun which is great.

For me it's definitely a 5, but it would be nice to spend a little bit more time on the actual plugin and maybe add it to the abstract so it's clear that the talk is not about code optimisations.