I encountered the exact same problem after installing Firefox 63 on two Windows 10 machines residing on my home network, and my online research found the following:
Firefox 63 is slow at loading new pages
Found the reason for this behavior. For some reason the new version
puts the proxy settings so that the "Auto-detect proxy settings for
this network" is enabled. This makes it so that every page load it
tries to first find a proxy, which takes seconds, and after that loads
the page. Switched the setting back to No Proxy and everything is nice
and fast again.
This seemed to be confirmed in a pair of official "bugzilla" reports:
Version 63 very slow performance, proxy set to "use system default" - fixed if set to "no proxy"
Firefox checks to determine proxy settings on every request - RESOLVED FIXED in Firefox 64
As a result, their recommended fix action is as follows:
- Within Firefox, navigate to the
about:preferences
page
- In the default
General
section view, scroll to the bottom to find the Network Settings
area
- Click on the
Settings...
button
In the subsequent window, select the radio button to modify the settings under Configure Proxy Access to the Internet
to choose No proxy
![Connection Settings](../../I/static/images/90bfac1a12ca5b5ccb64de2088bc30fc1b0c4516e331f57bcc650a9cc22ff19e.jpg)
However, although this solution apparently worked for several people, in my personal experience the problem persisted even after I changed my settings to No proxy. One of the Mozilla contributors recommended installing the Firefox 64 "Nightly" version to see if that eliminated the issue and it did for some users, but I'm not really a big fan of Beta software on my primary computers.
As an alternate solution, I uninstalled Firefox 63 on one of my computers, installed Firefox 60.3.0 ESR, and that alleviated the problem. Web page navigation and downloads were as fast as they were in Firefox 62. Also, please remember that a transition like this one is relatively painless, because your Firefox personal data is preserved in another location.
I left Firefox 63.0.1 installed on my secondary computer for ongoing testing purposes. When Firefox 64 is released to the general public in December, I will double-check to ensure that the problem has been alleviated.
Update
Mozilla has apparently addressed this issue in their latest update that increments the mainstream iteration of Firefox to version 63.0.3:
![Firefox version 63.0.3](../../I/static/images/00d5f5cb317f046bc7a4bd3fac68a48d378e31127a45d61f3aa1aadf417ad374.jpg)
It has been several days since we heard from you. Did you have any lingering questions? – Run5k – 2018-11-28T21:11:16.870
@Run5k I'm not quite sure, if "no proxy" solved the problem. I'm waiting for Firefox 64 to see, if this solves the problem. It is released on 11. december. – SearchSpace – 2018-11-30T13:11:53.323
@SearchSpace if you take a look at the update within my answer, the latest Firefox patch to version 63.0.3 should have eliminated the problem. It did on the laptop that I utilize for testing purposes. – Run5k – 2018-11-30T13:34:09.523
@Run5k Ah, I didn't see that. Nice.I think it's a bit better. But I now assume that my problem is network bound. When I use F12 and look at the network analysis, it seems that my Firefox updates the Website in time with the frequests. With http/2 it should be better and I didn't found a setting which could enhance this (e.g. like pipelining in the early days). Prefetching astonishingly didn't make better side loads either (or i missconfigured??). – SearchSpace – 2018-11-30T17:29:43.420