# Floating Group vs. Popup for SPA Performance

**URL:** <https://forum.bubble.io/t/floating-group-vs-popup-for-spa-performance/339852>\
**Category:** Responsiveness\
**Created:** [September 18, 2024, 6:42pm UTC](https://forum.bubble.io/t/floating-group-vs-popup-for-spa-performance/339852 "2024-09-18T18:42:32Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![drixxon](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/drixxon/32/90231_2.png) [@drixxon](https://forum.bubble.io/u/drixxon)\
**Post date:** [September 18, 2024, 6:42pm UTC](https://forum.bubble.io/t/floating-group-vs-popup-for-spa-performance/339852/1 "2024-09-18T18:42:33Z")

</div>

Hi,

Currently using the blur effect for popups + Fullscreen

How much processing power does this use compared to just temporarily overlaying a [vertically float to both] floating group with ‘Go to Page’ URL Parameters?

What I like about the popup is the blur but the mobile back button doesn’t close the popup automatically.

What I like about the floating group is that the back button closes it, however, because it’s a “go to page” workflow, any & all “when page is loaded” workflows will run, even if they don’t fire off, bubble is still performing the check every time!

So,

What would you recommend I do?