I've finally had time to clean up some tech debt, so I migrated this blog onto Netlify fronted by Cloudflare and fixed the web performance issues I spotted.
Latest blog posts from Nooshu.com by
Feed dedicated to the random web developerment thoughts of Frontend developer, Matt Hobbs. Posts 99% related to either frontend development or web performance.
Wednesday 21st April 2021 was a day like no other. This certainly isn't my usual web performance related blog post!
The 'Graph Page Data' view is a one of those WebPageTest features that is hidden in plain sight. So lets shine a light on it and see what it can do.
A step by step guide on how to get started with using Cloudflare Workers for web performance optimisation.
Cloudflare Workers are an awesome tool for rapid prototyping and observing web performance changes, here are a few recipes you may find useful.
Priority hints may be on hold, but you can still enable them and investigate what they can do. And in one instance I found a nice set of improvements to visual metrics.
Twitter embeds are bad for web performance. They cause so many extra requests, and a huge amount of data added to a page, so how can we fix it?
It's important to remember staff members are users too, so optimise your internal tools for performance for more productive and less stressed workforce! Here are some tools and resources to help you out.
A small change in the ordering of your font sources in the `@font-face` rule can have a big impact on data and web performance, especially when used in conjunction with the `preload` resource hint.
Let's examine the WebPageTest homepage and investigate what all the settings do, including examples of what you can use them for.
It's amazing what a difference a single little response header can have on web performance. Lets 'fix' it at the edge with a
Cloudflare Worker CDN.
WebPageTest exposes all its data via an easy to access API, but the data listed can be overwhelming. Using a tool like jq can help. Here's how you use it.