# Multiple Spotify Oneboxes causing performance issues

**URL:** https://meta.discourse.org/t/multiple-spotify-oneboxes-causing-performance-issues/356465
**Category:** 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:** 4
**Page:** 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.

---

<div class="post-metadata">

### Author: ![SeanDrownedinSound](https://avatars.discourse-cdn.com/v4/letter/s/76d3ee/32.png) [@SeanDrownedinSound](https://meta.discourse.org/u/SeanDrownedinSound)
#### Post date: [March 9, 2025, 9:08am UTC](https://meta.discourse.org/t/multiple-spotify-oneboxes-causing-performance-issues/356465/3 "2025-03-09T09:08:55Z")

</div>

Thanks for posting this

For clarity, I’ve temporarily blocked the domain from OneBox to try to prevent people having the issue

---

<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 17, 2025, 12:13pm UTC](https://meta.discourse.org/t/multiple-spotify-oneboxes-causing-performance-issues/356465/4 "2025-03-17T12:13:36Z")

</div>

Sadly no suggestions on this, so I’ll share what Drowned in Sound did in case any other forums encounter the same issue.

The following was added to the CSS:

```plaintext
iframe[src*="spotify.com"] {
  max-height: 150px;
  height:80px;
}

```

Which results in the embeds looking like this:

 ![Spotify embed screenshot taken from the Drowned in Sound community](https://global.discourse-cdn.com/meta/original/4X/d/f/f/dff4fa9d15018cfbccae707330d6d54aeb1d063d.jpeg)

Those who faced the performance problems before have stopped complaining, so it seems that this fix was good enough to resolve things.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [April 16, 2025, 12:13pm UTC](https://meta.discourse.org/t/multiple-spotify-oneboxes-causing-performance-issues/356465/5 "2025-04-16T12:13:48Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.