---
schema_version: "1"
id: 89f7283697ba4fce1edaded5d374b36fabbe4d7ca3193020e3d9ff896131e86e
title: Use Lightning CDN to Load Applications Faster
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform/aura-platform/guides/aura/perf/perf-cdn.md
canonical_url: https://developer.salesforce.com/docs/platform/aura-platform/guide/perf-cdn.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 62a089fb93bbe8eb81fef67680122ff3df6f8247635b5d43a7194ecfd0df11ca
products:
  - Lightning Aura Components Developer Guide
  - Platform Developer Content
---

# Use Lightning CDN to Load Applications Faster

To load Lightning Experience faster, the Lightning content delivery network (CDN) is enabled for your org by default. The Lightning CDN serves static content for the Lightning component framework.

Salesforce uses a CDN partner to serve the static content for the Lightning Component framework over a CDN. CDNs are the industry standard for web applications because they provide faster and more secure content delivery. A CDN is a geographically distributed network of servers that store cached versions of web assets. To optimize page load times and site performance, a CDN efficiently delivers publicly cacheable content to users.

Lightning CDN is enabled by default for new and existing orgs. When enabled, this setting turns on the Lightning CDN for the static JavaScript and CSS in the Lightning Component framework at the org level. It doesn’t distribute your Salesforce data or metadata in a CDN. Admins can turn off this preference in Setup | Session Settings by deselecting the **Enable Content Delivery Network (CDN) for Lightning Component framework** checkbox. However, disabling the CDN isn’t recommended because it can impact performance.

If you experience any issues, ask your IT department if your company’s firewall blocks CDN content. Your IT department can make sure that `static.lightning.force.com`, `a.static.lightning.force.com`, `b.static.lightning.force.com`, and `*.static.lightning.force.com` are added to any allowlist or firewall that your company operates. If you’re using Lightning Out, make sure that Content Security Policy doesn't block `a.static.lightning.force.com` and `b.static.lightning.force.com domains`. You can ping `static.lightning.force.com`, but you can’t browse directly to the root URL at `https://static.lightning.force.com`.

**important:** Don’t use IP addresses for network filtering because that can cause connection issues with `https://static.lightning.force.com`. IP addresses for `https://static.lightning.force.com` are dynamic and aren’t maintained in Salesforce’s list of allowed IP addresses.

**See Also**  


-   [*Salesforce Help:* Options to Serve a Custom Domain](https://help.salesforce.com/articleView?id=domain_mgmt_domain_config_options.htm&type=5)
-   [*Knowledge Article:* Salesforce Lightning CDN Preference Auto Enablement](https://help.salesforce.com/s/articleView?id=005115596&type=1)
-   [*Knowledge Article:* Salesforce IP Addresses and Domains to Allow](https://help.salesforce.com/articleView?id=000003652&type=1)