Read on Twitter
Live perf tweets!
I& #39;m going to be making performance improvements on https://tosbourn.com/ ">https://tosbourn.com/">... today and thought it would be fun to live tweet my process.
Will keep it all to this thread, so feel free to mute if you don& #39;t like fun.
Please play along by suggesting/questioning
I& #39;m going to be making performance improvements on https://tosbourn.com/ ">https://tosbourn.com/">... today and thought it would be fun to live tweet my process.
Will keep it all to this thread, so feel free to mute if you don& #39;t like fun.
Please play along by suggesting/questioning
The problem:
Posts such as https://tosbourn.com/what-is-the-gemfile/">https://tosbourn.com/what-is-t... are scoring ~51 in lighthouse for performance.
That is a joke, we can do better.
Lighthouse isn& #39;t a perfect tool, but it is quick to run and understand the results. Until we& #39;re scoring in the 90s there is no need for more data
Posts such as https://tosbourn.com/what-is-the-gemfile/">https://tosbourn.com/what-is-t... are scoring ~51 in lighthouse for performance.
That is a joke, we can do better.
Lighthouse isn& #39;t a perfect tool, but it is quick to run and understand the results. Until we& #39;re scoring in the 90s there is no need for more data
Before I even start delving into the details, there is one thing I want to do.
We have Google Ads on the site, but it makes us very little money, not worth the tracking and perf issues. I& #39;m going to remove these first.
We have Google Ads on the site, but it makes us very little money, not worth the tracking and perf issues. I& #39;m going to remove these first.
It is tempting when doing this work to branch your code into a branch such as "performance-improvements".
I find that too generic and I much prefer to make small changes and submit them for review as distinct units of work.
Therefore, my branch is called remove-google-ads
I find that too generic and I much prefer to make small changes and submit them for review as distinct units of work.
Therefore, my branch is called remove-google-ads
Some important tech details.
This is a static site, built with Jekyll and hosted on Github
It doesn& #39;t contain any CI/build tools, just the basic Github setup of "we check this branch and deploy whatever is on it"
I feel like this can be improved to add some perf steps.
This is a static site, built with Jekyll and hosted on Github
It doesn& #39;t contain any CI/build tools, just the basic Github setup of "we check this branch and deploy whatever is on it"
I feel like this can be improved to add some perf steps.
Because I& #39;m removing an ad, it is worth making sure my ads.txt is up to date ( https://support.google.com/adsense/answer/7532444?hl=en)
Turns">https://support.google.com/adsense/a... out there was only one entry in it so I can remove the file from the project. I love deleting stuff.
Turns">https://support.google.com/adsense/a... out there was only one entry in it so I can remove the file from the project. I love deleting stuff.
17 lines removed from the codebase in total. The changes are deploying now and I will test.
When it comes to web performance, I& #39;ve found testing locally or even on staging sites to be a bit rubbish.
Focus on fast deploys then you can do perf testing live, where it matters.
When it comes to web performance, I& #39;ve found testing locally or even on staging sites to be a bit rubbish.
Focus on fast deploys then you can do perf testing live, where it matters.
