Heavy inline script (> 200 KB)
inline_script_heavyShort answer
The page contains more than 200 KB of JavaScript inside <script> tags, not in external files. Inline code is re-downloaded with every page view, cannot be cached by the browser or the CDN, and adds to the HTML size that Googlebot has to parse. This issue affects how fast the page opens and the user experience. Move large scripts to external files with cache headers.
Why it matters
A 200 KB inline script is 200 KB of HTML on every visit, for every user, with no caching. It also delays the parser from reaching the content below it. Large inline blocks are usually a sign of a page builder or framework dumping its runtime, or a JSON state blob, into the page.
How Glimana detects it
The rule fires when the total size of inline <script> content on the page exceeds 200,000 bytes. The evidence shows the measured size.
How to fix it
Find the block in the page source (look for the largest <script> without src). Page builders and some sliders inline their JS and settings; most have an option to load from files instead. If it is a plugin without such an option, ask the author or replace the plugin.
Theme sections sometimes inline settings JSON for every block. Keep per-section data minimal and move shared code into assets/*.js loaded with {{ 'file.js' | asset_url | script_tag }}.
Build-time frameworks (Next, Nuxt) inline hydration data; keep it to what the page needs (getStaticProps returning only the used fields). Everything else goes to a cached bundle.
How the fix is verified
Re-crawl; the task closes when inline script on the page is under 200 KB.