Tonight at 6pm the NYC WebPerf Meetup is running another in person "Meet for Speed" session. We'll be taking requests from attendees for sites to do a web performance analysis on. Fastly will be hosting us at their NYC office.
https://www.meetup.com/web-performance-ny/events/304709044/
=> More informations about this toot | View the thread
This Friday afternoon I'll be at the Boston Web Performance meetup giving my talk on "Performance Mistakes". If you are in the Boston area and interested in web performance, join us!
https://www.meetup.com/boston-web-performance/events/304542099/
=> More informations about this toot | View the thread
Last week I gave a talk at the #PerfNow conference titled “Performance Mistakes”. I started off explaining a bit about Etsy’s blameless culture, and how it’s ok to make mistakes. Then I shared 17 common #webperf mistakes using HTTP Archive data, with examples.
Slides are here - https://www.slideshare.net/slideshow/performance-now-24-performance-mistakes-final-pdf/273431101
A few attendees told me they found some of these mistakes on their websites while we were still at the conference! So now they can be considered performance opportunities!
=> More informations about this toot | View the thread
Tomorrow at 6pm the NYC WebPerf Meetup is running another "Meet for Speed" session. We'll be taking requests from attendees for sites to do a web performance analysis on. Fastly will be hosting us at their NYC office.
RSVP here - https://www.meetup.com/web-performance-ny/events/300512872/
=> More informations about this toot | View the thread
I wrote a new tool to help analyze potential third party performance risks on your site. It uses data from WebPageTest to group results in a sortable/filterable table with lots of metrics that might be helpful for estimating whether a third party is a performance/failure risk.
Give it a try and see if you learn anything new about your third party content! More details on how to use it here - https://paulcalvano.com/2024-09-03-discovering-third-party-performance-risks/
=> More informations about this toot | View the thread
After last week's DigiCert certificate revocation incident, I thought it would be interesting to dig into some HTTP Archive data. I found that 1,241,943 websites would have been affected in some way (due to third parties). Imagine how disruptive that could have been!
I wrote a blog post about this here - https://paulcalvano.com/2024-08-04-third-parties-and-certificate-revocations/
=> More informations about this toot | View the thread
=> This profile with reblog | Go to paulcalvano@webperf.social account This content has been proxied by September (ba2dc).Proxy Information
text/gemini