Open in the explorer

Block JavaScript optimizations on these sites

Type
Computer and user
GPO path
Computer Configuration › Policies › Administrative Templates › Microsoft Edge › Content settings User Configuration › Policies › Administrative Templates › Microsoft Edge › Content settings
Supported on
Microsoft Edge version 134, Windows 7 or later
ADMX file
msedge.admx
Internal name
msedge/JavaScriptOptimizerBlockedForSites

Explanation

Allows you to set a list of site URL patterns that specify sites for which advanced JavaScript optimizations are disabled.

Disabling JavaScript optimizations means that Microsoft Edge may render web content more slowly.

For detailed information on valid URL patterns, see https://go.microsoft.com/fwlink/?linkid=2095322. Wildcards, *, are allowed.

You can set policy exceptions for specific subdomains and entire sites. For example, a policy set only for subdomain.contoso.com applies to subdomain.contoso.com without affecting contoso.com. In some cases, when a subdomain can't be isolated from its parent site, it may inherit the policy set on the parent site. Exceptions also may not take effect for frames loaded in an existing tab until the site is opened in a new tab. On low-memory Android devices, site-specific exceptions may not be enforced. Instead, sites use the policy from 'DefaultJavaScriptOptimizerSetting' (Control use of JavaScript optimizers), if set, or default to the profile's JavaScript optimization setting.

To enforce exceptions, Microsoft Edge may place sites or subdomains with settings that differ from the default in dedicated processes. This behavior can increase memory usage, especially on Android devices or when a wildcard pattern matches many subdomains, because each matching origin may be isolated separately. Isolated subdomains also can't use document.domain to access their parent site.

Note: In version 138 and earlier, policy exceptions were enforced only at the site level (eTLD+1). A policy set only for subdomain.contoso.com didn't take effect, even for subdomain.contoso.com. The policy had to be set on contoso.com to apply to both contoso.com and subdomain.contoso.com.

This policy applies on a frame-by-frame basis and isn't based only on the top-level origin URL. For example, if contoso.com is listed in the 'JavaScriptOptimizerBlockedForSites' (Block JavaScript optimizations on these sites) policy, but contoso.com loads a frame that contains fabrikam.com, contoso.com has JavaScript optimizations disabled. However, fabrikam.com uses the policy from 'DefaultJavaScriptOptimizerSetting', if set, or defaults to JavaScript optimizations enabled. Blocklist entries have higher priority than allowlist entries, and allowlist entries have higher priority than the configured default value.

If you don't configure this policy for a site, the policy from 'DefaultJavaScriptOptimizerSetting' applies to the site, if set. Otherwise, JavaScript optimization is enabled for the site.

Example value:

[*.]example.edu

Registry

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge
HKEY_CURRENT_USER\Software\Policies\Microsoft\Edge
Value name
not defined in the ADMX

Enable / disable values: not defined in the ADMX (see the options below).

PowerShell

PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.

Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.

Computer (HKLM)

Enable

# Enable: msedge/JavaScriptOptimizerBlockedForSites
$k = 'HKLM:\Software\Policies\Microsoft\Edge\JavaScriptOptimizerBlockedForSites'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Block JavaScript optimizations on these sites
# Non-additive list: existing values of the key are cleared first
if (Test-Path -Path $k) { (Get-Item -Path $k).Property | ForEach-Object { Remove-ItemProperty -Path $k -Name ([WildcardPattern]::Escape($_)) -ErrorAction SilentlyContinue } }
$values = @('<value1>', '<value2>')  # Replace the values with your own
$i = 1
foreach ($v in $values) { Set-ItemProperty -Path $k -Name ('' + $i) -Value $v -Type String; $i++ }

Disable

# Disable: msedge/JavaScriptOptimizerBlockedForSites
# No value is written in the "Disabled" state (nothing defined in the ADMX)

Revert to "Not configured"

# Revert to "Not configured": msedge/JavaScriptOptimizerBlockedForSites
$k = 'HKLM:\Software\Policies\Microsoft\Edge\JavaScriptOptimizerBlockedForSites'
Remove-Item -Path $k -Recurse -Force -ErrorAction SilentlyContinue

User (HKCU)

Enable

Disable

Revert to "Not configured"

Options (1)

LabelControlRegistry valueREG typeConstraints / details
Block JavaScript optimizations on these sitesJavaScriptOptimizerBlockedForSitesDescList (table)listSoftware\Policies\Microsoft\Edge\JavaScriptOptimizerBlockedForSitesValues named “” + numberREG_SZ (values under the key)

Application

Microsoft Edge (+ Edge Update, WebView2) (Microsoft) — November 2026 templates

Official templates downloaded on November 12, 2026.