[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fgdT39WgrLBRQ8LEWV-GgY6MydSQKHOUfg5O8uqsIfE0":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":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":38,"analysis":124,"fingerprints":149},"embed-javascript-file-content","Embed JavaScript File Content","1.0","Palasthotel GmbH","https:\u002F\u002Fprofiles.wordpress.org\u002Fpalasthotel\u002F","\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  …",10,1097,0,"2020-04-29T20:03:00.000Z","5.4.19","4.1","5.4",[19,20,21,22,23],"embed","enqueue","inline","javascript","scripts","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fembed-javascript-file-content.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":34,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},"palasthotel",4,120,89,30,86,"2026-04-04T14:07:15.989Z",[39,53,72,86,104],{"slug":40,"name":41,"version":42,"author":7,"author_profile":8,"description":43,"short_description":44,"active_installs":11,"downloaded":45,"rating":46,"num_ratings":47,"last_updated":48,"tested_up_to":15,"requires_at_least":49,"requires_php":17,"tags":50,"homepage":24,"download_link":52,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"inline-javascript-in-head","Inline JavaScript in Head","1.2.0","\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.",1534,20,1,"2020-04-29T20:05:00.000Z","4.0",[20,51,21,22,23],"head","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Finline-javascript-in-head.1.2.0.zip",{"slug":54,"name":55,"version":56,"author":57,"author_profile":58,"description":59,"short_description":60,"active_installs":61,"downloaded":62,"rating":36,"num_ratings":63,"last_updated":64,"tested_up_to":65,"requires_at_least":66,"requires_php":24,"tags":67,"homepage":70,"download_link":71,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"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",[68,51,22,23,69],"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":73,"name":74,"version":75,"author":57,"author_profile":58,"description":76,"short_description":77,"active_installs":78,"downloaded":79,"rating":80,"num_ratings":32,"last_updated":81,"tested_up_to":65,"requires_at_least":66,"requires_php":24,"tags":82,"homepage":84,"download_link":85,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"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",[83,68,22,23,69],"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":87,"name":88,"version":89,"author":90,"author_profile":91,"description":92,"short_description":93,"active_installs":11,"downloaded":94,"rating":13,"num_ratings":13,"last_updated":24,"tested_up_to":95,"requires_at_least":96,"requires_php":24,"tags":97,"homepage":100,"download_link":101,"security_score":102,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":103},"custom-resources","Custom Resources","1.0.7","Fineswap","https:\u002F\u002Fprofiles.wordpress.org\u002Ffineswap\u002F","\u003Cp>This plugin will make developers and site builders (hopefully very) happy.\u003C\u002Fp>\n\u003Cp>It enables site administrators to supply additional styles or\u002Fand scripts to\u003Cbr \u002F>\nbe loaded alongside the theme’s resources. It will work regardless which\u003Cbr \u002F>\ntheme the site is running, which makes it brilliant for adding custom\u003Cbr \u002F>\nprogramming and content blocks.\u003C\u002Fp>\n\u003Cp>Styles and scripts can be either entered manually or loaded from\u003Cbr \u002F>\nexternal URL’s.\u003C\u002Fp>\n\u003Cp>Brought to you by \u003Ca href=\"http:\u002F\u002Ffineswap.com\u002F?utm_source=wordpress&utm_medium=plugin&utm_term=readme-desc&utm_campaign=custom-resources\" title=\"A blog and a mobile app advocating sustainability and green living\" rel=\"nofollow ugc\">Fineswap\u003C\u002Fa> Team.\u003C\u002Fp>\n","Easily load additional styles and scripts (for both front and backend pages). Works by direct inline embedding or by using URL's.",2540,"3.7.41","3.0.1",[98,19,21,23,99],"custom","styles","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcustom-resources\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcustom-resources.zip",100,"2026-03-15T10:48:56.248Z",{"slug":105,"name":106,"version":107,"author":108,"author_profile":109,"description":110,"short_description":111,"active_installs":112,"downloaded":113,"rating":102,"num_ratings":114,"last_updated":115,"tested_up_to":116,"requires_at_least":117,"requires_php":118,"tags":119,"homepage":122,"download_link":123,"security_score":102,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"flying-scripts","Flying Scripts: Delay JavaScript to Improve Site Speed & Performance","1.2.4","Gijo Varghese","https:\u002F\u002Fprofiles.wordpress.org\u002Fgijo\u002F","\u003Cp>Download and execute JavaScript on user interaction.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fyoutu.be\u002FYJ8TQ3bh-TA\" rel=\"nofollow ugc\">Demo video\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Flying Scripts delay the execution of JavaScript until there is no user activity. You can specify keywords to include JavaScripts to be delayed. There is also a timeout which executes JavaScript when there is no user activity.\u003C\u002Fp>\n\u003Ch3>Why should I use this plugin?\u003C\u002Fh3>\n\u003Cp>JavaScript is very resource-heavy. By delaying the execution of non-critical JavaScript (that are not needed for the initial render), you’re prioritizing and giving more resources to critical JavaScript files. This way you will reduce render time, time to interactive, first CPU idle, max Potential input delay etc. This will also reduce initial payload to browsers by reducing the no. of requests.\u003C\u002Fp>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fflying-scripts\u002F\" rel=\"ugc\">Official Support Forum\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.facebook.com\u002Fgroups\u002Fwpspeedmatters\" rel=\"nofollow ugc\">Facebook Group\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Our premium products\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fflyingpress.com\" rel=\"nofollow ugc\">FlyingPress\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fflyingcdn.com\" rel=\"nofollow ugc\">FlyingCDN\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Our free plugins\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fflying-pages\u002F\" rel=\"ugc\">Flying Pages\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fnazy-load\u002F\" rel=\"ugc\">Flying Images\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fflying-scripts\u002F\" rel=\"ugc\">Flying Scripts\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fflying-analytics\u002F\" rel=\"ugc\">Flying Analytics\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fflying-fonts\u002F\" rel=\"ugc\">Flying Fonts\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Contributors\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwpspeedmatters.com\u002F\" rel=\"nofollow ugc\">Gijo Varghese – WP Speed Matters\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.shaytoder.com\u002F\" rel=\"nofollow ugc\">Shay Toder\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Delay JavaScript to improve speed and performance by loading scripts only when needed, reducing render-blocking for a faster and smoother user experie …",30000,272456,37,"2025-12-02T13:23:00.000Z","6.9.4","4.5","5.6",[120,121],"3rd-party-scripts","defer-javascript","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fflying-scripts\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fflying-scripts.1.2.4.zip",{"attackSurface":125,"codeSignals":137,"taintFlows":144,"riskAssessment":145,"analyzedAt":148},{"hooks":126,"ajaxHandlers":133,"restRoutes":134,"shortcodes":135,"cronEvents":136,"entryPointCount":13,"unprotectedCount":13},[127],{"type":128,"name":129,"callback":130,"priority":46,"file":131,"line":132},"filter","script_loader_tag","anonymous","plugin.php",53,[],[],[],[],{"dangerousFunctions":138,"sqlUsage":139,"outputEscaping":141,"fileOperations":47,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":143},[],{"prepared":13,"raw":13,"locations":140},[],{"escaped":13,"rawEcho":13,"locations":142},[],[],[],{"summary":146,"deductions":147},"The \"embed-javascript-file-content\" plugin v1.0 exhibits a very strong security posture based on the provided static analysis. The complete absence of identified attack surface points like AJAX handlers, REST API routes, and shortcodes significantly limits potential entry vectors for attackers. Furthermore, the code signals are overwhelmingly positive, with no dangerous functions, all SQL queries using prepared statements, and all output properly escaped. The single file operation, while noted, is not inherently risky without further context, but it is the only area that deviates from a perfect score in this section.\n\nThe taint analysis shows no identified flows with unsanitized paths, reinforcing the impression of well-sanitized code. The plugin's vulnerability history is also spotless, with zero recorded CVEs of any severity. This indicates a history of secure development or effective patching if any issues were previously present and addressed. The lack of any recorded vulnerabilities, common or otherwise, further solidifies its current secure standing.\n\nOverall, this plugin appears to be exceptionally well-secured, with no immediate or historical security red flags. The developer has implemented robust security practices, resulting in a remarkably clean static analysis and no known vulnerabilities. The only minor point of attention is the single file operation, which, in the absence of other issues, does not represent a significant risk.",[],"2026-03-17T00:34:42.764Z",{"wat":150,"direct":156},{"assetPaths":151,"generatorPatterns":153,"scriptPaths":154,"versionParams":155},[152],"\u002Fwp-content\u002Fplugins\u002Fembed-javascript-file-content\u002F",[],[],[],{"cssClasses":157,"htmlComments":158,"htmlAttributes":159,"restEndpoints":160,"jsGlobals":161,"shortcodeOutput":162},[],[],[],[],[],[]]