iiinova — where your digital self keeps evolving

Brian Louis Ramirez

@screenspan.net

298 followers 110 following 40 posts

Born in California, made in Germany. Loves making music, hiking and running. Blogs at screenspan.net.

Brian Louis Ramirez @screenspan.net · 01/11/2025

This marks my fifth year attending my favorite conference, #perfnow in Amsterdam. Again, I leave super-charged from the inspiring talks, nerdy chats and unforgettably fun times. The perf community is just so amazing!

Tim Kadlec speaking at Performance Now in Amsterdam, 2025

240

Brian Louis Ramirez @screenspan.net · 07/12/2024

Nice sleuthing, Harry! 🤩 Good points to keep in mind when debugging LCP. Looks like Lighthouse would have called out the <article> (and a massive render-blocking CSS file) as well.

010

Brian Louis Ramirez @screenspan.net · 06/12/2024

Hi support@bsky.app, I've been enjoying BSKY :-) Just wanted to point out something that @kojordan.com spotted: the app is loading TTF fonts, which are very large. You should be using WOFF2 – and if you're preloading them, you need the "crossorigin" attribute :-)

1100

Brian Louis Ramirez @screenspan.net · 06/12/2024

Thanks! 😊 Geesh, you're right — massive font and JS files. I wonder why they're serving TTF...

110

Brian Louis Ramirez @screenspan.net · 04/12/2024

I've been using: • "% Good CWV" – i.e. the % of all page views that support the CWV which have "good" LCP, CLS and INP. That can be used for different levels of aggregation (URL-level, page types, origin). • Displaying "Passed" or "Failed" – i.e. if the p75 for the CWV are "good".

Table showing the % of Good Core Web Vitals and whether p75 CWV are good (by device and page)

020

Brian Louis Ramirez @screenspan.net · 22/11/2024

I guess BSKY should also link to info about just using a custom handle as well on the initial signup page.

010

Brian Louis Ramirez @screenspan.net · 22/11/2024

Please don't use JavaScript to determine which layout version to use on a device, otherwise the layout may shift. I spotted a customer loading a desktop version by default and using JS to load the mobile version on a mobile device, and was able to see the DOM diff by dis-/enabling JS in DevTools.

HTML code showing a div with a class set for desktop and a class set for mobile

050