FF 92.0.1 (64-bit), NoScript 11.2.11
I’m not sure if it’s important at all in which order to add them both (I mean user.js and NoScript) and I can’t remember it… I think at first I added NoScript.
for meteofrance.com you should TRUST/Temp. TRUST in NoScript:
meteofrance.com
cloudflare.com
jsdelivr.net
unpkg.com
and maybe some more web sites
Ok I’ve tested Firefox 92.0.1 (64-bit) with NoScript 11.2.11 and arkenfox 91.0 (everything out of box and with default settings) here is my result:
no addons, no arkenfox:
Blocking tracking ads? Partial protection
Blocking invisible trackers? Partial protection
Protecting you from fingerprinting? Your browser has a unique fingerprint
Currently, we estimate that your browser has a fingerprint that conveys at least 17.75 bits of identifying information.
NoScript, no arkenfox:
Blocking tracking ads? Yes
Blocking invisible trackers? Yes
Protecting you from fingerprinting? No
Currently, we estimate that your browser has a fingerprint that conveys 15.75 bits of identifying information.
NoScript, arkenfox:
Blocking tracking ads? Yes
Blocking invisible trackers? Yes
Protecting you from fingerprinting? Yes
Currently, we estimate that your browser has a fingerprint that conveys 7.12 bits of identifying information.
NoScript and arekenfox, an amazing combo!
That’s what I did but it doesn’t work.
I uninstalled Noscript and disabled JavaScript in uBlock Origin.
Your site meteofrance.com does work after “TRUST/Temp. TRUST” the sites in NoScript, as indicated by HC.
If you have both NoScript and uBlock Origin installed then make sure you don’t have javascript disabled in uBlock Origin for the site meteofrance.com (the </> icon on uBlock Origin main panel should have no red cross when you open the meteofrance.com site).
I tried adding No Script. It’s been some time since I had it installed. If memory serves me, I had to do a lot of setting toggling to get things to work right on lots of sites.
Blocking tracking ads? Yes
Blocking invisible trackers? Yes
Protecting you from fingerprinting? Yes
Within our dataset of several hundred thousand visitors tested in the past 45 days, only one in 138.47 browsers have the same fingerprint as yours.
Currently, we estimate that your browser has a fingerprint that conveys 7.14 bits of identifying information.
Have you installed other addons or arkenfox to achieve this result or changed some NoScipt settings for that?
I tried NoScript without anything else and result was not very good (see tests).
There was an assortment of addons before I added no script. Canvas blocker, decentraleyes, ghostery, https everywhere, privacy badger, UBO. I made no changes to noscript. Just adding noscript moved me from partial to full protection on cover your tracks.
Thanks.
As I prefer to use FF out of the box (meaning without using arkenfox) I’ll start some new tests to find out which addon(s) next to using NoScript is required to get the fingerprint full protection.
New tests, started with a new and clean FF profile, using latest FF 92.0.1 and latest available addons.
All addons added to FF at their default settings.
Results:
No addons
Blocking tracking ads? Partial protection
Blocking invisible trackers? Partial protection
Protecting you from fingerprinting? Your browser has a nearly-unique fingerprint
Currently, we estimate that your browser has a fingerprint that conveys 16.76 bits of identifying information.
NoScript
Blocking tracking ads? Yes
Blocking invisible trackers? Yes
Protecting you from fingerprinting? No
Currently, we estimate that your browser has a fingerprint that conveys 15.18 bits of identifying information.
NoScript, Decentraleyes
Blocking tracking ads? Yes
Blocking invisible trackers? Yes
Protecting you from fingerprinting? No
Currently, we estimate that your browser has a fingerprint that conveys 14.95 bits of identifying information.
NoScript, Decentraleyes, Privacy Badger
Blocking tracking ads? Yes
Blocking invisible trackers? Yes
Protecting you from fingerprinting? Partial protection
Currently, we estimate that your browser has a fingerprint that conveys 13.01 bits of identifying information.
NoScript, Decentraleyes, Privacy Badger, Https Everywhere
Blocking tracking ads? Yes
Blocking invisible trackers? Yes
Protecting you from fingerprinting? Partial protection
Currently, we estimate that your browser has a fingerprint that conveys 12.95 bits of identifying information.
NoScript, Decentraleyes, Privacy Badger, Https Everywhere, Canvas Blocker
Blocking tracking ads? Yes
Blocking invisible trackers? Yes
Protecting you from fingerprinting? Partial protection
Currently, we estimate that your browser has a fingerprint that conveys 12.9 bits of identifying information.
NoScript, Decentraleyes, Privacy Badger, Https Everywhere, Canvas Blocker, Ghostery
Blocking tracking ads? Yes
Blocking invisible trackers? Yes
Protecting you from fingerprinting? Partial protection
Currently, we estimate that your browser has a fingerprint that conveys 12.86 bits of identifying information.
NoScript, Decentraleyes, Privacy Badger, Https Everywhere, Canvas Blocker, Ghostery, uBlock Origin
Blocking tracking ads? Yes
Blocking invisible trackers? Yes
Protecting you from fingerprinting? Partial protection
Currently, we estimate that your browser has a fingerprint that conveys 12.81 bits of identifying information.
As can be seen from the above tests using NoScript, Decentraleyes and Privacy Badger reduces the identifying information with 3.75 bits and sets protection level to Partial.
Strangely, when adding the addons Https Everywhere, Canvas Blocker, Ghostery and uBlock Origin this doesn’t reduce the identifying information bits any further and keeps protection level at Partial.
I can’t seem to reach the identifying information of 7.12 bits and protection level Yes from previous test using only NoScript and arkenfox.
What settings do I have to make in FF and/or Addons to achieve the identifying information of 7.12 bits?
[at]CommodoUser2019, are you using arkenfox too perhaps? Could you please check your FF profile directory if the file user.js exists?
I’ve never heard of arkenfox. It appears to be something from github and I don’t even know how it works. I use extensions right from FF and individual tweaks via about:config. I don’t see a user.js file. I checked here: C:\Users\xxxx\AppData\Roaming\Mozilla\Firefox\Profiles
I’ve made a good deal of FF tweaks, many of them from this site: Firefox Privacy - The Complete How-To Guide for 2024
There’s a lot of useful information on his site and that link is just about FF. OFF-TOPIC- Just before typing this I read a disturbing story on restore privacy.com about an attack against the VPN industry as a (former?) malware distributer has just bought out a bunch of VPNs including the one I use which I just re-subscribed to earlier this month. Also review websites. :o >:(
Thanks for checking the presence of user.js in the right spot.
That’s an excellent article on Firefox Privacy - The Complete How-To Guide for 2024.
I applied the tweaks from that article to the last FF test from above and bingo, identifying information = 7.15 bits.
As for “malware” VPNs, who can you trust these days… :o
The article from Firefox Privacy - The Complete How-To Guide for 2023 | RestorePrivacy is pretty good but a bit old…Some settings mentioned there aren’t actual anymore and there is a mistake also…(media.peerconnection.enabled (WebRTC) = false but media.peerconnection.enabled = false)
In general it covers basic privacy settings from arkenfox and the latter gets quite often updates which could be installed with just a mouse click. 
In section “Browser fingerprinting” the link to browser fingerprinting is quite recent (March 9, 2021) and it also covers arkenfox/ghacks user.js.
True, arkenfox is updated often and installing it is very easy but it changes a massive number of FF settings. Simply installing arenfox without knowing what settings get added or changed in FF may lead to confusion when using FF, for example, it does disable IPv6.
Read user.js carefully before using it.
I thought one should always read instructions before using something, especially when using scripts…? ;D
…If you are going to use the ‘arkenfox’ user.js file then you should never edit it, (nor the prefs.js file that Firefox creates) nor should you change important settings from about:config unless you’re only testing something. All of your custom preferences should be placed in your user-overrides.js file and then appended to the ‘arkenfox’ user.js using their updater script…Firefox Configuration Guide for Privacy Freaks and Performance Buffs – 12Bytes.org
CIS doesn’t flag the script so no need to read instructions. ;D
So if I want to enable IPv6 in arkenfox then I have to create a user-overrides.js file add the pref to enable IPv6 to it then execute the script to append user-overrides.js to user.js and then I have to restart Firefox?
That’s quite cumbersome, why not edit user.js directly? Are there any specific do-not-touch reasons?
I think I shouldn’t copy and paste the full article here. 
The main reason is as the author says: user.js file is quite a large and is updated fairly frequently, so if you edit it and then update it, all your custom changes will be lost, whereas if you copy the preferences you want to alter from the ‘arkenfox’ user.js to your user-overrides.js and change the values there, then updating the ‘arkenfox’ user.js one will be a lot less painful.
Better you read about it in Firefox Configuration Guide for Privacy Freaks and Performance Buffs – 12Bytes.org… When not fully, then just the Configuration files, Obtaining and maintaining the user preferences files, Verifying the integrity of user.js and especially Updating the user.js and user-overrides.js files sections.
I have created for my own use a simple batch file to update user.js with just one click.
Ok, thanks very much for explaining, much appreciated. :-TU
Maybe I’m going to use arkenfox too, will see.