summaryrefslogtreecommitdiff
path: root/_posts/2024-10-26-firefox-first-site-load-delay-of-5-seconds.md
diff options
context:
space:
mode:
Diffstat (limited to '_posts/2024-10-26-firefox-first-site-load-delay-of-5-seconds.md')
-rw-r--r--_posts/2024-10-26-firefox-first-site-load-delay-of-5-seconds.md29
1 files changed, 29 insertions, 0 deletions
diff --git a/_posts/2024-10-26-firefox-first-site-load-delay-of-5-seconds.md b/_posts/2024-10-26-firefox-first-site-load-delay-of-5-seconds.md
new file mode 100644
index 0000000..0f006ca
--- /dev/null
+++ b/_posts/2024-10-26-firefox-first-site-load-delay-of-5-seconds.md
@@ -0,0 +1,29 @@
+---
+layout: post
+title: 'Firefox: First site load delay of several seconds'
+date: 2024-10-26 17:11 +0200
+lang: "en"
+categories: ["tech"]
+---
+
+For quite a while now, I've wondered why, when as a first thing upon opening Firefox
+and loading furry.engineer, the page load would always be delayed by several seconds.
+
+I actually thought it was the "fault" of furry.engineer, or maybe my cursed DNS setup,
+but yesterday (?) I did the actual sane thing and looked at Wireshark. (I mostly forgot
+to do this). Turns out, there actually was first a HTTPS type DNS request for furry.engineer,
+followed by 5 seconds of "next to nothing", until the actual A/AAAA type DNS request.
+Inbetween, there were a few adblock related DNS queries.
+
+Upon some searching of issues, I found this:
+
+{% image
+ img="https://pics.uvokchee.de/upload/2024/10/26/20241026151032-a27b1634.jpg"
+ alt="Screenshot of uBlock Origin settings"
+%}
+
+It's simply uBlock Origin behaving "as intended" with the
+"Suspend network activity until all filter lists are loaded".
+As I have quite a few of them activated, it's no wonder this delay happens.
+
+I'll keep this setting activated anyway, even though the behavior is annoying.