[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fGtu1sx6nZaDphyihx_IWwGnYkMN1blLEeQLV6G2-l9s":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":40,"analysis":126,"fingerprints":165},"inline-javascript-in-head","Inline JavaScript in Head","1.2.0","Palasthotel GmbH","https:\u002F\u002Fprofiles.wordpress.org\u002Fpalasthotel\u002F","\u003Cp>\u003Cstrong>CAUTION\u003C\u002Fstrong>: This plugin is now deprecated! The successor plugin is \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fembed-javascript-file-content\u002F\" rel=\"ugc\">Embed JavaScript File Content\u003C\u002Fa>. The new plugin is rebuild from scratch and more rock solid: It respects order and position of scripts and extra scripts added via \u003Ccode>wp_add_inline_script\u003C\u002Fcode> or \u003Ccode>wp_localize_script\u003C\u002Fcode> don’t get lost. Give it a try!\u003C\u002Fp>\n\u003Cp>In some cases you cannot wait for a JavaScript file to load, even if it is placed early in the \u003Ccode>\u003Chead>\u003C\u002Fcode> section of your template. You can benefit from better performance, if you place the JavaScript code directly inside a \u003Ccode>\u003Cscript>\u003C\u002Fcode> tag into the header. This is where this plugin comes in: It provides a filter \u003Ccode>inline_javascript_in_head_handles\u003C\u002Fcode>, which takes JavaScript handles, dequeues those scripts and echos their code content inline into the head section instead of linking them via a script tag.\u003C\u002Fp>\n\u003Cp>Please beware that placing lots of JavaScript code inline in the \u003Ccode>\u003Chead>\u003C\u002Fcode> section can be critical! First you lose caching benefits and second the document size can increase easily. A general rule of thumb is that you should only consider JavaScript files for inline placement, which are critical and which have a file size lower than ~500 Bytes.\u003C\u002Fp>\n\u003Ch4>Example\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>add_action( 'wp_enqueue_scripts', 'my_scripts' );\nfunction my_scripts() {\n    \u002F\u002F Some critical script is enqueued\n    wp_enqueue_script( 'js-detection', get_template_directory_uri() . '\u002Fjs\u002Fjs-detection.js' );\n}\n\n\u002F**\n * Define JavaScript handles to be echoed inline in the html head section.\n *\u002F\nadd_filter( 'inline_javascript_in_head_handles', 'my_inline_javascript_in_head_handles', -20 );\nfunction my_inline_javascript_in_head_handles( $handles ) {\n    $scripts = [ 'js-detection' ];\n\n    return array_merge( $handles, $scripts );\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Boosts performance of critical short JavaScripts by placing their content directly into the HTML head.",10,1534,20,1,"2020-04-29T20:05:00.000Z","5.4.19","4.0","5.4",[20,21,22,23,24],"enqueue","head","inline","javascript","scripts","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Finline-javascript-in-head.1.2.0.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":33,"display_name":7,"profile_url":8,"plugin_count":34,"total_installs":35,"avg_security_score":36,"avg_patch_time_days":37,"trust_score":38,"computed_at":39},"palasthotel",4,120,89,30,86,"2026-04-04T14:07:16.464Z",[41,60,72,93,107],{"slug":42,"name":43,"version":44,"author":45,"author_profile":46,"description":47,"short_description":48,"active_installs":49,"downloaded":50,"rating":38,"num_ratings":51,"last_updated":52,"tested_up_to":53,"requires_at_least":54,"requires_php":25,"tags":55,"homepage":58,"download_link":59,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"speed-up-javascript-to-footer","Speed Up – JavaScript To Footer","1.0.11","nigro.simone","https:\u002F\u002Fprofiles.wordpress.org\u002Fnigrosimone\u002F","\u003Cp>This small plugin (2 Kb) moves JavaScript to the footer and improve page load times.\u003Cbr \u002F>\nNote: this only works if your other plugins and theme add the JavaScripts correctly.\u003C\u002Fp>\n\u003Cp>Configurations are not required! You just have to install it and after the plugin does it all, none further action it’s required.\u003C\u002Fp>\n","Move all the possible JavaScript files from head to footer and improve page load times.",1000,43852,6,"2023-03-05T07:56:00.000Z","6.0.11","3.5",[56,21,23,24,57],"footer","wp_enqueue_scripts","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fspeed-up-javascript-to-footer\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fspeed-up-javascript-to-footer.1.0.11.zip",{"slug":61,"name":62,"version":63,"author":7,"author_profile":8,"description":64,"short_description":65,"active_installs":11,"downloaded":66,"rating":28,"num_ratings":28,"last_updated":67,"tested_up_to":16,"requires_at_least":68,"requires_php":18,"tags":69,"homepage":25,"download_link":71,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"embed-javascript-file-content","Embed JavaScript File Content","1.0","\u003Cp>In some critical cases you cannot wait for a JavaScript file to load. Then you can benefit from better performance, if you embed the JavaScript code directly into the \u003Ccode>\u003Cscript>\u003C\u002Fcode> tag. This is where this plugin comes in: It provides a filter \u003Ccode>embed_javascript_file_content_handles\u003C\u002Fcode>, which takes JavaScript handles and echos their code content into the DOM instead of linking to a file.\u003C\u002Fp>\n\u003Cp>Please beware that placing lots of embedded JavaScript code can be critical! First you lose caching benefits and second the document size can increase easily. A general rule of thumb is that you should only consider JavaScript files for inline placement, which are critical and which have a file size lower than ~500 Bytes.\u003C\u002Fp>\n\u003Ch4>Example\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>add_action( 'wp_enqueue_scripts', 'my_scripts' );\nfunction my_scripts() {\n    \u002F\u002F Some critical script is enqueued\n    wp_enqueue_script( 'js-detection', get_template_directory_uri() . '\u002Fjs\u002Fjs-detection.js' );\n}\n\n\u002F**\n * Define JavaScript handles to be echoed inline in the html head section.\n *\u002F\nadd_filter( 'embed_javascript_file_content_handles', 'my_embed_javascript_file_content_handles' );\nfunction my_embed_javascript_file_content_handles( $handles ) {\n    $scripts = [ 'js-detection' ];\n\n    return array_merge( $handles, $scripts );\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Boosts performance of critical short JavaScript files by allowing to embed their code instead of linking to files. Script positions and extra scripts  …",1097,"2020-04-29T20:03:00.000Z","4.1",[70,20,22,23,24],"embed","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fembed-javascript-file-content.zip",{"slug":73,"name":74,"version":75,"author":76,"author_profile":77,"description":78,"short_description":79,"active_installs":80,"downloaded":81,"rating":82,"num_ratings":83,"last_updated":84,"tested_up_to":85,"requires_at_least":17,"requires_php":18,"tags":86,"homepage":90,"download_link":91,"security_score":92,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"javascript-autoloader","Smart JavaScript Auto Loader","5.0.3","Peter Raschendorfer","https:\u002F\u002Fprofiles.wordpress.org\u002Fpetersplugins\u002F","\u003Cp>The Smart JavaScript Auto Loader Plugin allows you to load additional JavaScript files without the need to change files in the theme directory\u003C\u002Fp>\n\u003Ch3>Retired Plugin\u003C\u002Fh3>\n\u003Cp>Development, maintenance and support of this plugin has been retired in october 2023. You can use this plugin as long as is works for you.\u003C\u002Fp>\n\u003Cp>There will be no more updates and I won’t answer any support questions. Thanks for your understanding.\u003C\u002Fp>\n\u003Cp>Feel free to fork this plugin.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>To load additional JavaScript files just put them into a directory named \u003Cstrong>jsautoload\u003C\u002Fstrong>. This directory can be placed in three different locations that are loaded in the following order:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Child Theme dependent (if using a Child Theme) : in the Child Theme’s directory\u003C\u002Fli>\n\u003Cli>Theme dependent : in the Theme’s directory\u003C\u002Fli>\n\u003Cli>Theme independent : in the wp-content directory\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Only files with extension .js are added, all other files are ignored. Subdirectories can be used and will also be scanned. To ignore a complete directory (including all subdirectories) name the directory beginning with an underscore (_). The files are added in alphabetical order. Directories always are added \u003Cstrong>after\u003C\u002Fstrong> files.\u003C\u002Fp>\n\u003Cp>To load one ore more JavaScript files at the end of your HTML file just place them into a directory named \u003Cstrong>footer\u003C\u002Fstrong>. To add the files to the footer of your theme it is required to call wp_footer() in your footer.php.\u003C\u002Fp>\n\u003Ch3>Plugin Privacy Information\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>This plugin does not set cookies\u003C\u002Fli>\n\u003Cli>This plugin does not collect or store any data\u003C\u002Fli>\n\u003Cli>This plugin does not send any data to external servers\u003C\u002Fli>\n\u003C\u002Ful>\n","Load JavaScript files without coding",400,24546,100,8,"2024-04-17T20:13:00.000Z","6.3.8",[56,87,23,88,89],"header","jquery","wp_enqueue_script","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjavascript-autoloader\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjavascript-autoloader.5.0.3.zip",92,{"slug":94,"name":95,"version":96,"author":45,"author_profile":46,"description":97,"short_description":98,"active_installs":99,"downloaded":100,"rating":101,"num_ratings":34,"last_updated":102,"tested_up_to":53,"requires_at_least":54,"requires_php":25,"tags":103,"homepage":105,"download_link":106,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"speed-up-clean-wp","Speed Up – Clean WP","1.0.8","\u003Cp>This small plugin (5 Kb) clean WordPress by remove comment-reply.min.js and jquery-migrate.js scripts, disable “embeds” and “emoji” features and clean the head from unnecessary metadata.\u003C\u002Fp>\n\u003Cp>Configurations are not required! You just have to install it and after the plugin does it all, none further action it’s required.\u003C\u002Fp>\n","Clean WP remove comment-reply.min.js and jquery-migrate.js scripts, disable \"embeds\" and \"emoji\" features and clean the head from  …",300,19316,80,"2022-11-24T06:52:00.000Z",[104,56,23,24,57],"emoji","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fspeed-up-clean-wp\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fspeed-up-clean-wp.1.0.8.zip",{"slug":108,"name":109,"version":110,"author":111,"author_profile":112,"description":113,"short_description":114,"active_installs":82,"downloaded":115,"rating":116,"num_ratings":117,"last_updated":118,"tested_up_to":119,"requires_at_least":120,"requires_php":25,"tags":121,"homepage":25,"download_link":125,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"wp-script-optimizer","WP Scripts & Styles Optimizer","0.4.5","Hendrik Lersch","https:\u002F\u002Fprofiles.wordpress.org\u002Friddler84\u002F","\u003Cp>Optimization of included JavaScript- and CSS-files can be a very important thing, if you want a faster site. Many WordPress plugins comes with multiple third-party and\u002For own JavaScript-files that are then often be included on every page of your site. In worst cases you have more than one of the same file included on your site. That slows down your site!\u003C\u002Fp>\n\u003Cp>But also “Render blocking” can easily slow down a website. Every external JavaScript- or CSS-file, that is included in the head of your site, blocks the site from rendering, until all files are completely processed. It’s a common practice to move all these Scripts and Styles (except critical CSS) to the footer of your site, so the rendering is no longer blocked and your website loads faster.\u003C\u002Fp>\n\u003Cp>This is where WP Script Optimizer helps you! It makes it possible to control the output of every registered JavaScript or CSS-file. You can easily create rules for it or deactivate files completely. You can also move files to the footer of your site or vice versa.\u003C\u002Fp>\n\u003Cp>Check out the following lists for all currently avaiable and planned features. If you like this plugin, please upvote and comment. That would be really helpful.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What you can currently do with WP Script Optimizer\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Get an overview of all frontend JavaScript and CSS files, that are included on your site (divided in categories)\u003C\u002Fli>\n\u003Cli>Control scripts and styles for as many single pages as you want or simply globally\u003C\u002Fli>\n\u003Cli>Change the positioning (Header\u002FFooter) of specific JavaScripts \u002F CSS or all at once\u003C\u002Fli>\n\u003Cli>Deactivate specific Javascripts or CSS-files completely, if not needed\u003C\u002Fli>\n\u003Cli>Easily create logical rules to control under which conditions a file is included or not (by use of wordpress’s conditional tags)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>What you can do in future with WP Script Optimizer (planned, but not currently implemented)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Minify and\u002For encrypt JavaScript- and CSS-files\u003C\u002Fli>\n\u003Cli>Include your own JavaScript\u002FCSS files or JavaScript\u002FCSS inline code, without do it manually through functions.php\u003C\u002Fli>\n\u003Cli>Add extra code to any registered JavaScript or CSS-file\u003C\u002Fli>\n\u003Cli>Concatenate two or more (or all) files of one type (JS or CSS) to speed up loading times\u003C\u002Fli>\n\u003Cli>Better overview of dependents and its dependencys\u003C\u002Fli>\n\u003Cli>… feel free to make suggestions 🙂\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>IMPORTANT – Please read:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This plugin can not decide if a file is needed or not needed in a specific situation. Your settings have the potential to break features and functions of your site. If that is the case, you can easily change or delete your settings via the admin panel, so everything will be like it was before.\u003C\u002Fp>\n\u003Cp>tl;dr: you have to know what you’re doing 😉\u003C\u002Fp>\n\u003Cp>\u003Cstrong>If You had any problems with this plugin, please contact me, so i could fix it. Please don’t write a negative review without gave me the chance to correct any issues. Thanks.\u003C\u002Fstrong>\u003C\u002Fp>\n","Improve your site-rendering speed by customizing all of your JavaScript- and CSS-files. Deactivate, set conditions or change positioning of files",16219,94,15,"2017-10-10T14:37:00.000Z","4.8.28","4.4.0",[122,123,23,24,124],"css","into-header","styles","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-script-optimizer.0.4.5.zip",{"attackSurface":127,"codeSignals":139,"taintFlows":149,"riskAssessment":150,"analyzedAt":164},{"hooks":128,"ajaxHandlers":135,"restRoutes":136,"shortcodes":137,"cronEvents":138,"entryPointCount":28,"unprotectedCount":28},[129],{"type":130,"name":131,"callback":132,"priority":28,"file":133,"line":134},"action","wp_print_scripts","inline_scripts_in_head","plugin.php",41,[],[],[],[],{"dangerousFunctions":140,"sqlUsage":141,"outputEscaping":143,"fileOperations":14,"externalRequests":28,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":148},[],{"prepared":28,"raw":28,"locations":142},[],{"escaped":28,"rawEcho":14,"locations":144},[145],{"file":133,"line":146,"context":147},79,"raw output",[],[],{"summary":151,"deductions":152},"The 'inline-javascript-in-head' plugin v1.2.0 exhibits a generally strong security posture based on the provided static analysis and vulnerability history.  The absence of any known CVEs and a clean vulnerability history are positive indicators. Furthermore, the code demonstrates good practices by not utilizing dangerous functions, performing all SQL queries using prepared statements, and making no external HTTP requests. The attack surface is minimal with zero entry points identified, and there are no indications of dangerous taint flows.  However, a significant concern arises from the output escaping. With one total output and 0% properly escaped, this presents a potential risk for Cross-Site Scripting (XSS) vulnerabilities if user-supplied data is directly outputted without sanitization.  Additionally, the presence of file operations without clear context in the analysis warrants attention, as this could be a vector for further exploitation depending on its implementation. The lack of nonce and capability checks, while tied to the zero attack surface, could become a vulnerability if the plugin's functionality were to expand or be misused in the future.",[153,156,159,162],{"reason":154,"points":155},"Output not properly escaped",7,{"reason":157,"points":158},"File operations present",3,{"reason":160,"points":161},"No capability checks",2,{"reason":163,"points":161},"No nonce checks","2026-03-16T23:53:02.842Z",{"wat":166,"direct":171},{"assetPaths":167,"generatorPatterns":168,"scriptPaths":169,"versionParams":170},[],[],[],[],{"cssClasses":172,"htmlComments":173,"htmlAttributes":174,"restEndpoints":175,"jsGlobals":176,"shortcodeOutput":177},[],[],[],[],[],[]]