RemoteAsset
Discourages use of third party domains for hosting assets. You should deliver as much as you can from the Shopify content delivery network (CDN). Using the same host for your assets avoids unnecessary HTTP connections and allows the server to prioritize delivery of blocking resources using HTTP/2 prioritization. Learn more about hosting assets on Shopify servers.
The following examples contain code snippets that either fail or pass this check.
In these examples, multiple connections are competing for resources, are accelerating download independently and are improperly prioritized.
The following example retrieves assets from multiple CDNs:
The following example doesn't use the image_url filter to retrieve the image.
In the following examples, JavaScript, CSS and images are all loading from the same connection. The browser and CDN can properly prioritize which assets are downloaded first while maintaining a "hot" connection that downloads fast.
This can be done by downloading the files from those CDNs directly into your theme's assets directory and using the image_url filter for images, as in the following example:
The following example contains the default configuration for this check:
| Parameter | Description |
|---|---|
enabled |
Whether this check is enabled. |
severity |
The severity of the check. |
Disabling this check
Anchor link to section titled "Disabling this check"Consider disabling this check the remote content that you're retrieving is highly dynamic.
For backward compatibility with configuration files made for Theme Check v1.X.X, this check is also recognized in configuration files with the following name:
AssetUrlFilters