#frontend-performance
#frontend-performance

[ follow ]

A Broken Heart

in a modern web app there are many potential causes of a performance problem: third-party JavaScript, overburdened servers, bloated assets, missing database indexes - a list as long as your arm. But decades of building for the web told me that this was a frontend problem. I could just smell it. The page looked janky while loading. And despite being the least-bad approach for web frontends today, the React ecosystem is lousy with ways for a codebase to get tangled, slow, and fishy.

Software development

Privacy technologies

fromNew Relic

3 weeks ago

Browser consent mode allows for flexibility in evolving privacy regulations

New Relic's browser monitoring and consent mode enable full frontend performance visibility while providing configurable user-consent controls to meet privacy and regulatory requirements.

React

fromLogRocket Blog

2 months ago

Server Components vs. Islands Architecture: The performance showdown - LogRocket Blog

Islands architecture minimizes first-visit JavaScript payloads, while React Server Components minimize shipped client code and excel across longer sessions by avoiding full-page reloads.

Web development

fromLogRocket Blog

2 months ago

Stop using JavaScript to solve CSS problems - LogRocket Blog

Modern CSS features like content-visibility:auto and dynamic viewport units eliminate many JavaScript virtualization needs and are production-ready.

Web development

fromVue.js Jobs

5 months ago

Nuxt 3 Front End Performance Specialist at YouWish.no - VueJobs

Frontend performance issues on a Nuxt 3 app are harming SEO despite image CDN, srcset, and caching; urgent frontend optimization and code review are needed.