Since I've reported this in a very scattered manner across multiple threads, I thought I'd create a bug thread to centralize my information and see if anyone else is having this issue.

My Older Reports

October 11th, 2025

Quote by Luck

I love Subeta, and I wouldn&;t even know what to do with my time if it wasn&;t here, but Kumos is unplayable in many ways.
While I would love to use Kumos, and have previously, there&;s clearly been some sort of change in the past few months I haven&;t used it. Any time I open it now, it wants to use as much as my computer&;s GPU as possible, putting me at 100% usage and slowing down my computer IMMENSELY to the point where I can barely scroll the page and if I do manage to do my quests on there (I have been opting not to for a while because of this) I have to restart my computer afterward because firefox won&;t stop lagging and crashing.
Like... is this normal? Is it just me? Is there anything I can do on my end to limit kumos&; GPU usage?
I hate to hear that legacy is on its deathbed, because trying to use kumos puts my computer on its deathbed...
And since apparently Keith likely won&;t see this, can someone tell him in the discord that kumos makes my computer crawl?! It wasn&;t like this before!!! Windows 10, Firefox 143.0.4 (64-bit)

Quote by Luck

Have you tried again recently (like, in the last few days?) - I&;ve made some changes to the way the layout in general loads, that I think might have addressed this. If you&;re getting it today I&;ll take another look!

Unfortunately yes, I opened it a couple times before I submitted my post just then, just to make sure, and watched my task manager as I did so. Immediate spike to 100% GPU usage and very slow.[/quote]

November 3rd, 2025

Quote by Luck

Unfortunately I&;m still having trouble with it using 100% GPU. To be clear that&;s GPU (graphics processing unit), not CPU (central processing unit). When I open kumos, bam, 100%. However, when I scroll down so that the top bar with the navigation and everything is no longer visible on the screen, it drops significantly. As I write this post now on Kumos far enough down the page without the navigation visible, it&;s hovering between 10%-40%.

November 14th, 2025

Quote by Luck

The wardrobe on kumos was something that I used to be excited for, and would have loved to help test, but kumos is still simply unusable for me. And I will keep posting this issue because it&;s killing my enthusiasm.
[quote=Luck]Unfortunately I&;m still having trouble with it using 100% GPU. To be clear that&;s GPU (graphics processing unit), not CPU (central processing unit). When I open kumos, bam, 100%. However, when I scroll down so that the top bar with the navigation and everything is no longer visible on the screen, it drops significantly. As I write this post now on Kumos far enough down the page without the navigation visible, it&;s hovering between 10%-40%.

I have an Intel UHD Graphics 600 and the drivers are updated.

December 1st, 2025

Quote by Luck

I&;d love to use Kumos more, but it&;s just too hardware intensive, which I feel is strange for a browser-based virtual pet site to be. I have an Intel UHD Graphics 600 and the drivers are updated, and it&;s simply not powerful enough so Kumos puts a strain on my computer, using 100% of its GPU.
To be clear that&;s GPU (graphics processing unit), not CPU (central processing unit). When I open Kumos, bam, 100%. However, when I scroll down so that the top bar with the navigation and everything is no longer visible on the screen, it drops significantly, hovering between 10%-40%. It temporarily spikes whenever I scroll the page however.
Something about Kumos changed over the summer, because it was not like this earlier this year when I used to do the quests on there. I don&;t do my quests there anymore as I have to restart my computer afterward because firefox won&;t stop lagging and crashing. Now I have to quickly get in and get out for anything that is being transferred there, like Melody now.
It&;s going to reach a point where I won&;t be able to play anymore once legacy is gone, so I&;m going to keep posting this issue wherever and whenever I can. :( Kumos is the only website I use that gives me this kind of issue.

December 3rd, 2025 (Kumos Shoutbox)

Quote by Luck

I wish Kumos wasn&;t so hardware intensive.

Quote by Keith

I am pushing up a change to Kumos now that should significantly reduce the strain it puts on the browser after being open for a few minutes
if you&;re still around - i made some changes to the layout and have them fully pushed out, if you want to see. i&;m hoping it doesn&;t make your GPU flare up, or at least not as much and I can keep heading in that direction

Quote by Luck

I cleared my cache and did a hard refresh but I&;m not seeing any improvements on my end. It&;s still using 100% GPU and (less often, but) up to 50% of my CPU. In contrast to legacy, which uses 1-15% for both GPU and CPU.

Quote by Keith

😮‍💨 If you remove the shoutbox from your sidebar widgets, does that change it?

Quote by Luck

I removed it but there was no change. It always uses 100% GPU when I&;m at the top of the page, but once I scroll so that the navigation is no longer visible it drops off to 5-30% (spiking to 50% when scrolling).

MY COMPUTER INFORMATION:

Browser: Firefox 146.0.1 (64-bit) System: Windows 10 Home System Type: 64-bit operating system, x64-based processor Graphics Card: Intel UHD Graphics 600 (128 MB) Processor: Intel Celeron J4125 CPU @ 2.00GHz RAM: 4.00 GB (Speed: 3200MHz)

Please let me know if I can provide anything else.

Click images to see larger.

Legacy Site as a baseline:

Using 1% GPU.

Clicked on my Kumos bookmark:

100% GPU usage, and 35% more CPU usage than legacy.

Offscreen Navigation GPU Dropoff:

The very pixel that the navigation/header etc is no longer on screen, the GPU usage drops a huge amount, to 28% shown here. CPU usage also halves.

🆕

Performance Spike

Image of what it looks like in my performance tab of the task manager.

I just pushed out a branch I've been noodling on over the last few days, it did a couple of things:

Removed a file atmopshere.css that I was working on in the early days of Kumos, that was being imported but not used. This had a lot of CSS animations in it, that weren't being run... but I think your browser was maybe interpreting them so that it could run them later.
Removed a lot of blur effects from around the site. These came with our CSS library so required me doing some overwrites. blur() is a really expensive on the GPU effect and we weren't getting any benefit from it. Buttons look less blurry I guess
To resolve a bug with the navigation menu a long time ago I set the z-index of the header to 9999. Apparently, browsers have to actually calculate 9998 layers before that! No problem for modern devices, but your GPU has pretty minimal RAM so it was getting caught up on this. I've re-placed everything and am only using 10 layers now!
Removed some very very very subtle gradients from the sidebar and header, which just removes some calculations that weren't needed

I know that this probably won't bring it down to 1%, and there are probably more modifications I can make to the library that we're importing for CSS to remove more of these GPU heavy effects, but this should at least make it possible to navigate the site 🙏

Logged Out

Kumos being too hardware intensive

Filter

Replies

My Older Reports

MY COMPUTER INFORMATION:

Legacy Site as a baseline:

Clicked on my Kumos bookmark:

Offscreen Navigation GPU Dropoff:

Performance Spike