A “script” element with a “type” attribute whose value is neither a JavaScript MIME type, “module”, “importmap”, nor “speculationrules” (i.e., a data block) must not have an “async” attribute.

The async attribute is invalid on a <script> element whose type marks it as a data block, because browsers never fetch or execute data blocks.

When the type attribute is anything other than a JavaScript MIME type, module, importmap, or speculationrules, the browser treats the element as a data block: inline content that other scripts on the page can read, but that is never downloaded or run. The most common example is application/ld+json structured data. async controls when a script downloads and executes, so it has no meaning on an element that does neither.

This usually happens when a template or a performance plugin adds async to every <script> tag on the page, including the data blocks.

Examples

Invalid: async on a data block

<script type="application/ld+json" async>
  {
    "@context": "https://schema.org",
    "@type": "Organization",
    "name": "Example"
  }
</script>

Valid: data block without async

<script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "Organization",
    "name": "Example"
  }
</script>

Remove the async attribute. If the script was actually meant to run, fix the type value instead: use a JavaScript MIME type, module, or omit the attribute entirely.

Learn more:

MDN Reference

HTML script element - MDN

→

MDN Reference

The script type attribute - MDN

→

WHATWG Spec

Scripting - WHATWG HTML Standard

→