# Multiple Spotify Oneboxes causing performance issues

**URL:** <https://meta.discourse.org/t/multiple-spotify-oneboxes-causing-performance-issues/356465>\
**Category:** Product Support\
**Tags:** performance, onebox\
**Created:** [March 9, 2025, 7:53am UTC](https://meta.discourse.org/t/multiple-spotify-oneboxes-causing-performance-issues/356465 "2025-03-09T07:53:24Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![ma0sm](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ma0sm/32/259526_2.png) [@ma0sm](https://meta.discourse.org/u/ma0sm)\
**Post date:** [March 9, 2025, 7:53am UTC](https://meta.discourse.org/t/multiple-spotify-oneboxes-causing-performance-issues/356465/1 "2025-03-09T07:53:24Z")

</div>

There’s an issue that many users on the [Drowned in Sound community](https://community.drownedinsound.com) have encountered where [topics which contain a large number of Spotify links](https://community.drownedinsound.com/t/new-releases-07-march-25/87027/37) are [rendering the topic unusable to them](https://community.drownedinsound.com/t/issue-with-spotify-players/87033?u=ma0sm).

It’s been discussed there over the last few days, with a proposed solution to edit the CSS to minimise the maximum height for a Spotify Onebox (they don’t want to disable Onebox generation for the domain completely, for aesthetic reasons) and I thought I’d mention it here to see if you have any other thoughts or ideas on a solution.

I have not encountered the problem personally, so unfortunately cannot give more specifics than what has been posted above. It didn’t used to happen when the Spotify Oneboxes were more basic, but seems to have been triggered since they became extra.

---

_[View the full topic](https://meta.discourse.org/t/multiple-spotify-oneboxes-causing-performance-issues/356465)._
