Site loads so slow on computer [Firefox bug, maybe?

[TheDemonLord12]

Covers for Manga load slow and the updates page takes so slow

 

[kouyo]

Could you ELI5 the problem?

Potentially an issue on HAProxy with the QUIC protocol (this is still unconfirmed as the devs deemed it as "really difficult to diagnose right now").
Explaining what QUIC does requires a rather lengthy explanation, and I'm also not well verse on the matter, sorry.

 

[SoraKagami]

Potentially an issue on HAProxy with the QUIC protocol (this is still unconfirmed as the devs deemed it as "really difficult to diagnose right now").
Explaining what QUIC does requires a rather lengthy explanation, and I'm also not well verse on the matter, sorry.

Thank you to you and the Mangadex team for looking into and addressing the problem!

 

[TheMinester]

I experience this too when a page opens on a new tab where it half loads and I have to refresh the page so it actually loads

 

[Roler]

Ok, this has been happening to me lately too and I've tested it on multiple Firefox versions (all clean installs, default settings, DOH disabled), from 128 to 132, all versions caused the issue.

Chrome is also sometimes slower and takes seconds to respond, but still much faster than Firefox.

This is the issue in Firefox:
View attachment 10791
View attachment 10794
View attachment 10797
A single request takes several seconds after the site makes several other requests to the API, but I'm unsure what "Blocked" exactly means here. Also, it appears the more requests the site makes prior to that the longer the "Blocked" status is (some requests above this one also had the "Blocked" status but for a much shorter period)

I have also tested in Chrome, and while it also gets "throttled" in Chrome, it's for much shorter periods (sometimes it did take a bit more):
View attachment 10803

I have managed to fix this issue by changing the value of network.http.http3.max_accumlated_time_ms from 1 (I don't even know why this is default) to 500.

So to fix the Firefox issue:

1. go to about:config
2. search for network.http.http3.max_accumlated_time_ms
3. change the value of the setting to 500
4. restart Firefox

 

[Nojay]

I have managed to fix this issue by changing the value of network.http.http3.max_accumlated_time_ms from 1 (I don't even know why this is default) to 500.

So to fix the Firefox issue:

1. go to about:config
2. search for network.http.http3.max_accumlated_time_ms
3. change the value of the setting to 500
4. restart Firefox

I just tried this fix in my own copy of Firefox (132.0.2 regular). The occasional delay of 10-15 seconds between selecting a title and loading the first page still occurs for me, same as when the default value was set to 1. I'm mostly using Edge with Mangadex at the moment and it doesn't seem to suffer from the same delays (current version 130.0.2849.80).

 

[BraveDude8]

I have managed to fix this issue by changing the value of network.http.http3.max_accumlated_time_ms from 1 (I don't even know why this is default) to 500.

So to fix the Firefox issue:

1. go to about:config
2. search for network.http.http3.max_accumlated_time_ms
3. change the value of the setting to 500
4. restart Firefox

Still getting the issue myself in Firefox 132, just less so, and it's consistently in that 10-15 second range. Hard to catch it in network logs because >99% of my site usage involves opening new tabs.

 

[goldencircle]

I've had this problem of pages sometimes half loading ever since I replaced my pcie wireless network adapter with a usb dongle last week. If I wait around long enough the page does load though. However it's often quicker to hit F5. My usb dongle is the TP-Link TL-WN821N and my machine is running Linux, and the browser in all cases is Firefox. (The pcie adapter while more reliable would periodically not send packets for seconds at a time, which is unacceptable during zoom calls.)

All this leads me to believe that the underlying issue might be something funky going on with the network packets.

 

[Roler]

I just tried this fix in my own copy of Firefox (132.0.2 regular). The occasional delay of 10-15 seconds between selecting a title and loading the first page still occurs for me, same as when the default value was set to 1. I'm mostly using Edge with Mangadex at the moment and it doesn't seem to suffer from the same delays (current version 130.0.2849.80).

Still getting the issue myself in Firefox 132, just less so, and it's consistently in that 10-15 second range. Hard to catch it in network logs because >99% of my site usage involves opening new tabs.

10-15 second delays?
I'm not sure if that's the same issue because my delays were longer.
You can try to check if any requests are still getting "Blocked" by Firefox like they were in my case.

Does it happen only when opening a new tab?
Because Firefox does seem slower in rendering the Nuxt app than Chrome, but if you're not opening a bunch of tabs at the same time and still have 10-15 second delays in new tab loads, that might be caused by an extension, try with a clean Firefox profile and see if it still occurs.

 

[Aenir]

I've noticed when a page isn't loading, that refreshing will cause it to immediately load.

 

[Manko-sensei]

Today's Firefox update seems to have solved Firefox issue, with all add-ons and usual stuff it's working properly with no delay from the app (loading time entirely depends on my end). I'm calling the update "Firefox, stop hitting yourself".
Correction: loading works fine, but search with MangaDex search tool still acts oddly (I don't know how to describe it).
Second edit: as the day passed, the performance turned for the worse.

 

[UnnamedPlayer]

Today's Firefox update seems to have solved Firefox issue, with all add-ons and usual stuff it's working properly with no delay from the app (loading time entirely depends on my end). I'm calling the update "Firefox, stop hitting yourself".
Correction: loading works fine, but search with MangaDex search tool still acts oddly (I don't know how to describe it).
Second edit: as the day passed, the performance turned for the worse.

For me, the problem manifest even with the last Firefox update. It did improved a little, but not that much. But it don't manifest on the front page, or very rarely. Loading chapters is another story.

 

[froggie2345]

Problem still persists for me (in a firefox-based browser). Swapped to a chromium browser and it doesn't appear to have the same issues.

 

[AbuHajaar]

Is this the issue? 29.5 seconds to GET chapter.
Firefox 133.0, saved HAR file if needed

 

[dweeceman]

Hi. I'm also having this issue with Firefox Mobile app. Have been for a few weeks now.

 

[kouyo]

I have managed to fix this issue by changing the value of network.http.http3.max_accumlated_time_ms from 1 (I don't even know why this is default) to 500.

So to fix the Firefox issue:

1. go to about:config
2. search for network.http.http3.max_accumlated_time_ms
3. change the value of the setting to 500
4. restart Firefox

After two weeks I can confirm doing these changes completely solves the issue. I suggest everyone to also try making these changes. For mobile users try Firefox Nightly (about:config is not enabled on stable Firefox mobile) or switch to Chrome.

 

[UnnamedPlayer]

I have managed to fix this issue by changing the value of network.http.http3.max_accumlated_time_ms from 1 (I don't even know why this is default) to 500.

Just to be sure : what is this setting doing, what's his interpration ? From the name, it looks like it set a time limit for something, but google don't tell me more.

 

[Trodsen]

After two weeks I can confirm doing these changes completely solves the issue. I suggest everyone to also try making these changes. For mobile users try Firefox Nightly (about:config is not enabled on stable Firefox mobile) or switch to Chrome.

there's actually a way to reach about:config on the stable firefox mobile(source: I did it myself), instead of about:config you need to go to:
chrome://geckoview/content/config.xhtml

Can also confirm it works great, both on mobile and PC.

Edit: Also guess it's also a neat thing to mention, that field in settings used to be undefined until version 122 of firefox, which matches my experience of these issues starting out this year.

 

[Roler]

Just to be sure : what is this setting doing, what's his interpration ? From the name, it looks like it set a time limit for something, but google don't tell me more.

I have traced it back to:
https://github.com/mozilla/gecko-de...fc70/netwerk/socket/neqo_glue/src/lib.rs#L693
https://github.com/mozilla/gecko-de...fc70/netwerk/socket/neqo_glue/src/lib.rs#L789

What I understood from taking a quick look at the code, by default, if all outgoing datagrams/packets of a HTTP3/QUIC request are not processed within 1ms, it interrupts and reschedules it, creating a constant rescheduling loop.

1ms doesn't seem like anything close to a realistic time, increasing it to just a bit more should already be better (I set it to 500ms but you can try setting it to lower if you want).

 

[Akule]

After two weeks I can confirm doing these changes completely solves the issue. I suggest everyone to also try making these changes. For mobile users try Firefox Nightly (about:config is not enabled on stable Firefox mobile) or switch to Chrome.

Yeah, when Roler posted their solution, it had fixed my problem as well.