Other frankly embarassing loading times for *.maplelegends.com/* webpages

you got this shit behind 137 CDNs and reverse proxies or what? i get consistently piss-poor loading times (regardless of cache usage or dis-usage on my own part):

(the above measurements are from loading https://maplelegends.com/lib/npc)

ye you read that right, somewhere between 17 and 18 seconds. now my internet connexion ain't exactly the fastest draw in the west, but i assure you it ain't no slouch and i ain't usin it for anything else at the moment.

hey, maybe it's my browser. but i tell ya hwat, i tested this shit with Firefox 65.0.2 (the latest stable version as of this writing, 2019-03-05) AND with Chromium 72.0.3626.121 (the latest stable version as of this writing, 2019-03-05) and boy all i got is some funky monkey shit. Firefox just hangs, apparently doing nothing, saying it's "resolving the host", and eventually either gives up or successfully loads. maybe my DNS is just shitting its pants or something, but it ain't shittin its pants resolving any other domain names, dig? Chromium somehow almost immediately gets an HTTP 503 response and shows its generic error page, before (eventually...) finally coming to its senses and lighting my shit up with those sweet, sweet green HTTP 200 headers.

my user-agent string: Mozilla/5.0 (X11; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0

to be more specific, that "Linux x86_64" is 4.20.13-arch1-1-ARCH.†

browser extensions/plugins i got on & shit:

• Cookie AutoDelete (https://addons.mozilla.org/firefox/addon/cookie-autodelete/)
• Decentraleyes (https://addons.mozilla.org/firefox/addon/decentraleyes/)
• DuckDuckGo Privacy Essentials (https://addons.mozilla.org/firefox/addon/duckduckgo-for-firefox/)
• HTTPS Everywhere (https://addons.mozilla.org/firefox/addon/https-everywhere/)
• Privacy Badger (https://addons.mozilla.org/firefox/addon/privacy-badger17/)
• uBlock Origin (https://addons.mozilla.org/firefox/addon/ublock-origin/)

† if any of you buncha schmucks so much as dares to rehash another god damn "btw i use arch" joke i will f,strike you down

 

well i'm getting a file that is nearly 6 times the size in 237ms so i don't think it actually takes 16529ms to download the html, firefox just counts the entire loading process (including actually resolving the host so that a GET request can be made in the first place) against the first file loaded, i.e. the html

EDIT: (https://www.speedtest.net/)

 

i should note that

and more specifically, once chromium finally establishes a connection, it wipes the network panel entirely (the thing y'all've posted screenshots of) and starts over with the HTTP 200's. that's why i didn't include a screenshot, because i'm not sure how to get a good representative one

EDIT:

that seems plausible, although this consistently happens even after having not made any requests for, say, 36 hours. and when i do make requests i do so reasonably, i don't use any *.maplelegends.com/* webpages terribly often or in any unusual ways, so any such influx of requests sure ain't comin from me, and yet i consistently face unusually long loading times (and often abortive attempts to even connect to the server at all) pretty much every day when i try to access the website (say, to vote)

 

so, it seems to be that it depends on what DNS you use! apparently the DNS i was using wasnt caching aggressively enough or something? i'm honestly very confused since this is literally the only site that i have ever had problems with, and i had consistent problems every time i tried to visit any maplelegends.com page, including usually having to try 2 or 3 times on average since most attempts to get such webpages would fail entirely

 

on second thought, what is with the

shit that comes up before you can get into these websites?

 

that's what i figured. it takes a little while for me (6 seconds or so) but i guess someone is caching the results somewhere because i dont usually see it more than once per browser session

assuming that the """invisible check""" (emphasis on the "check" and not the "invisible", presumably) is getting some data from my browser, client-side, im guessing it takes so long because i use privacy-minded browser plugins that dont let very much entropy leak, so it takes a while for whateverthefuck it's doing (???) to come to a conclusion, and a lot of times it seems that it comes to the conclusion that i am a bot

i'm flattered, really, but i can assure you i am no cyborg.

ah, i thought that was just me and Wine being finicky. well god damn

yeah, that's why i created this thread basically. my experience is very similar, although switching DNS's helped

 

make another thread for it

 

nothing that would consume bandwidth, at the time i did that test

most users where? nevermind the fact that lots of people browse the web on devices (PCs, cellphones) using WiFi or cellular networks, which can mean drastically varying throughput just between the router and the client, depending on the conditions and hardware involved

13Mb/s down is much more than enough to load a webpage (some text and the occasional compressed image)

right, obviously; there's nothing wrong with using proxies, but many-second load times for a single dinky webpage, plus the fact that most loads fail entirely and require manual retries, is usually not considered acceptable performance

i don't. i find it much more odd that your upload throughput is that much lower than your download's. in principle, they are limited by the same things so they should be equal, but on most consumer setups (like mine) the upload's is generally a bit (significantly, but not order(s) of magnitude or anything) higher, since ISPs don't need to throttle upload throughput that much because consumers are using the vast majority of bandwidth for download (uploading being done by servers, rather than consumers)

no.

as i state in the original post, i'm not running windoze at all

i'll call them, i'm sure they'll be right on it

 

tried loading the forums just now in a session launched as firefox -private -safe-mode

the "bot detection" (Please Wait...) seemed to take even longer (roughly 8 seconds), but otherwise the same. like i said, switching DNSs improved it significantly so i no longer have the "try loading it 3 or 4 times over the course of a minute until it works" problem.