Open lordyavin opened 2 years ago
And yet another discussion that backs this issue.
I can confirm that the website is still slow. Some requests are quite fast, but often you wait for 5 or more seconds. This makes navigation quite cumbersome. I am also based in Germany if that matters.
Technically, the slow request is usually the very first when opening a link, the one for the HTML document:
All the other requests (for this page I got 99 within the first 20 seconds) are quite fast (usually <100ms).
It's actually the only major issue for me and has been for a long time now.
Just right now I'm trying to contribute to the area I'm currently climbing at. Unfortunately the response times while editing are so annoying, that I lose interest in contributing.
Please, please make that editing is not a pain in the ass.
Don't what is going on, but photo uploading takes way longer than I'm used to. Submitting images takes extremely long.
Just now, my firefox waits to receive HTML of Donautal for around 1 Minute. After the HTML document is received, the following request to load JS, CSS, media and so on is okay fast.
I had issues with IPv4/IPv6 connections via my DualStack-Lite WAN. My ISP provides me (and probably a lot of other users) no external IPv4 address. Because of that my ISP needs to do network-address-translation (NAT) in their gateways, if I access a service through its IPv4 address. This can (and probably does) increase latency. So I checked if www.thecrag.com provides a IPv6 address: https://mxtoolbox.com/SuperTool.aspx?action=a%3aww.thecrag.com&run=toolpage Obviously not. Please think about setting up a IPv6 address to see if this does improve something. Someday you need to do this anyway ;-)
+1, such a great website but painfully slow to use
What happened?
Since a while I experience very bad performance when navigating the site. I don't know where the problem is but as it did not disapear over time I'm raising the issue.
See attached logs: firefox-logs.zip
Sometime navigating to another crag, or starting to log an ascent or finishing a log the browser does nothing and waits for data served by site or third party resources. This makes the usage quite unresponsive even though streams are lazy loaded in the background.
I experience this issue on mobile and desktop.
What you expected: