Kilotest: Diagnoses of script element invalidly deferred violation by HTML element 872 on 350 Sacramento page

Basics

About the 350 Sacramento page

• URL: https://350sacramento.org/
• Tested 28 days ago by job 029 on 2026-05-04 at 16:59

About HTML element 872

• Tag name: SCRIPT
• Text: [not applicable]
• Start tag: <script defer="" data-pagespeed-no-defer="" data-nowprocket="" data-wpacu-skip="" data-no-optimize="" type="salientlazyscript" data-salient-lazy-type="text/javascript" src="https://350sacramento.org/wp-content/plugins/js_composer_salient/assets/js/dist/js_composer_front.min.js?ver=8.6.1" id="wpb_composer_front_js-js">
• XPath: /html/body/script[19]
• Bounding box: x = 0, y = 0, width = 0, height = 0

About the script element invalidly deferred issue

• Why it matters: Browser processes the document improperly
• Priority: highest
• Related WCAG standard: 1.3.1

Diagnoses

Here is how tools diagnose the script element invalidly deferred issue for HTML element 872 of the 350 Sacramento page.

1. 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 a defer attribute.

   Tool: Html Checker API (World Wide Web Consortium)