Ask HN: Why still embed heavy 3rd-party iFrames for simple social proof?

I was auditing a React site recently and noticed that the 'Wall of Love' widget added 400kb of JS and 3 iFrames, tanking the LCP. It felt wrong. We spend weeks optimizing every pixel, then we throw it all away for a slow, black-box testimonial slider.

I decided to build Reviewskits [0] to see if we could move to a purely headless, data-first approach using Bun and Hono.

The goal: Fetch raw JSON, build your own UI components, and keep a 100/100 Lighthouse score.

My question to HN: Do you prioritize the 'ease of use' of pre-made widgets over performance, or is the industry ready for a developer-first, headless infrastructure for social proof? I'm curious to hear how you handle this in your projects.

[0] https://github.com/reviews-kits-team/reviews-kits [1] https://reviewskits.com/