Skip to main content

RemoteAsset


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:

<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.0/jquery.min.js" defer></script>
{{ "https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css" | stylesheet_tag }}
<img src="https://example.com/heart.png" alt="" />

The following example doesn't use the image_url filter to retrieve the image.

<img src="/content-v2/assets/images/{{ image }}" alt="" />

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:

<script src="{{ 'theme.js' | asset_url }}" defer></script>
{{ 'bootstrap.min.css' | asset_url | stylesheet_tag }}
<img src="/content-v2/assets/images/{{ image | image_url: width: 500 }}" alt="" />

The following example contains the default configuration for this check:

RemoteAsset:
enabled: true
severity: warning
ParameterDescription
enabledWhether this check is enabled.
severityThe severity of the check.

Anchor to Disabling this checkDisabling 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

Was this page helpful?