Rookie Guide to Pole Position at the Race for Performance
Everybody likes speed. We've all heard about studies showing website visitors moving on if a page take over 1 second to load. We've heard about Google sending your site to the next results page if your competitors load faster. We've all been irritated when having to wait on any random computational process taking longer than we would like. Still... I witnessed many times how site performance is an afterthought. Too often slow page load times is something the end client complains about days or even hours before launch. Or worse: the first visitors mock the sites slowness on social media right after it's launched.
In this session I will go over some of the strategies to prevent all this pain. The main recommendation is obvious: start caring about performance earlier in your build process. I'll go over some of the tools you can use for continuous monitoring of page load times from the start of your project. Some of the configuration tuning you can do to make any Drupal site perform better. Some of the additional techniques you can add to take it to the next level. And some to keep things running smooth after launch and through you next releases.
This is a session for Site Builders at a Beginner level but even more advanced Drupalists may learn a thing or two. Don't expect me to show you how interact with Drupal 8s advanced caching API, share the ultimate Varnish 5.1 VCL for Drupal 8.4 or disclose that an .htaccess oneliner that discovers your clients perception a cache header. These are topics for a Coding and Development track, both things I hardly ever do.