Kilotest: Diagnoses of script element invalid violation by HTML element 863 on 350 Sacramento page

Here is how tools diagnose the script element invalid issue for HTML element 863 of the 350 Sacramento page.

Basics

• About the script element invalid issue
  • Why it matters: Browser processes the document improperly
  • Priority: highest
  • Related WCAG standard: 1.3.1
• About the 350 Sacramento page
  • URL: https://350sacramento.org/
  • Tested on 2026-04-02 at 14:10
• About HTML element 863
  • 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/cache/autoptimize/js/autoptimize_single_900bad1dbd9b131a99f31703a66340f3.js?ver=4.0.2" id="nectar-waypoints-js">
  • XPath: /html/body/script[10]
  • Bounding box: x = 0, y = 0, width = 0, height = 0

Diagnoses

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)