[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fqgkr6kCnxpe15QnbR9HMyXxo75rSjaOJ490MNo4pYMo":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":22,"download_link":23,"security_score":13,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26,"vulnerabilities":27,"developer":28,"crawl_stats":25,"alternatives":36,"analysis":37,"fingerprints":80},"inline-image-base64","Inline Image Base64 – inline specific images into the HTML","0.0.4","Jose Mortellaro","https:\u002F\u002Fprofiles.wordpress.org\u002Fgiuse\u002F","\u003Cp>With Inline Image Base64 you can \u003Cstrong>inline specific images directly into the HTML\u003C\u002Fstrong> as base64.\u003C\u002Fp>\n\u003Cp>You can also use it to \u003Cstrong>disable the native lazy loading for specific images\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>After successful activation, you will see two checkboxes when you open an attachment in the media library. One for inlining the image and another one to disable the native lazy loading.\u003C\u002Fp>\n\u003Cp>Inlining the first image that appears in the viewport can drastically improve the rendering performance.\u003C\u002Fp>\n\u003Cp>The benefits will be higher for light images. A typical example is a light logo.\u003C\u002Fp>\n\u003Cp>If you do it for too big images the size of the HTML may become too big.\u003C\u002Fp>\n\u003Cp>Inlining images is very useful for images that are not more than 20-30 kB. But it depends on the size of the HTML that you already have.\u003C\u002Fp>\n\u003Cp>We suggest perform some speed tests with \u003Ca href=\"https:\u002F\u002Fpagespeed.web.dev\u002F\" rel=\"nofollow ugc\">Google PageSpeed Insights\u003C\u002Fa> to check the benefits.\u003C\u002Fp>\n\u003Cp>Upload an image that already has the right dimensions.\u003C\u002Fp>\n\u003Cp>To have a minimum Content Layout Shift, better you assign the width and hight to the image with custom CSS.\u003C\u002Fp>\n\u003Cp>In any case, we suggest disabling the native lazy loading for all the images that appear on the viewport during the first rendering.\u003C\u002Fp>\n\u003Cp>Disabling the lazy loading for those images can only give benefits.\u003C\u002Fp>\n\u003Cp>You will find the settings on every single attachment in the media library, no dedicated settings page for this plugin.\u003C\u002Fp>\n\u003Ch3>Backend Speed Optimization\u003C\u002Fh3>\n\u003Cp>Is your dashboard slow? We optimize admin performance by improving queries and reducing plugin load.\u003Cbr \u002F>\nRead \u003Ca href=\"https:\u002F\u002Fjosemortellaro.com\u002Fbackend-speed-optimization\u002F\" rel=\"nofollow ugc\">Backend Speed Optimization Service\u003C\u002Fa> for more information.\u003C\u002Fp>\n\u003Ch3>How to inline an image into the HTML\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Install and activate Inline Image base64\u003C\u002Fli>\n\u003Cli>Go to the media library and open the image that you want to inline into the HTML\u003C\u002Fli>\n\u003Cli>Check the checkbox “Inline Image”\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>How to disable the native lazy loading of a specific image\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Install and activate Inline Image base64\u003C\u002Fli>\n\u003Cli>Go to the media library and open the image that you want to load without lazy loading\u003C\u002Fli>\n\u003Cli>Unheck the checkbox “Native Lazy Loading”\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Suggestions\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Always disable the lazy loading for the images that appear in the viewport during the page loading\u003C\u002Fli>\n\u003Cli>Inline only the images that appears in the viewport during the page loading, only if they aren’t too big. Until 20-30 kB should be ok, but it depends on the size of the HTML.\u003C\u002Fli>\n\u003Cli>Perform some tests with \u003Ca href=\"https:\u002F\u002Fpagespeed.web.dev\u002F\" rel=\"nofollow ugc\">Google PageSpeed Insights\u003C\u002Fa> before and after inlining an image. So you can evaluate the benefits and drawbacks that could be caused by a too large HTML\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Help\u003C\u002Fh3>\n\u003Cp>For any kind of issue, don’t hesitate to open a thread on the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Finline-image-base64\u002F\" rel=\"ugc\">Support Forum\u003C\u002Fa>\u003C\u002Fp>\n","Improve the rendering performance inlining the little images directly into the HTML as base64 (e.g. the logo).",90,2979,100,1,"2025-12-10T09:12:00.000Z","6.9.4","4.6","5.6",[20,21],"layout-shift","speed-optimisation","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Finline-image-base64.0.0.4.zip",0,null,"2026-03-15T15:16:48.613Z",[],{"slug":29,"display_name":7,"profile_url":8,"plugin_count":30,"total_installs":31,"avg_security_score":32,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"giuse",56,26370,99,62,87,"2026-04-04T06:32:16.682Z",[],{"attackSurface":38,"codeSignals":60,"taintFlows":68,"riskAssessment":69,"analyzedAt":79},{"hooks":39,"ajaxHandlers":56,"restRoutes":57,"shortcodes":58,"cronEvents":59,"entryPointCount":24,"unprotectedCount":24},[40,46,50],{"type":41,"name":42,"callback":43,"file":44,"line":45},"filter","attachment_fields_to_edit","eos_iib64_add_image_attachment_fields_to_edit","admin\\iib64-admin.php",5,{"type":41,"name":47,"callback":48,"file":44,"line":49},"attachment_fields_to_save","eos_iib64_add_image_attachment_fields_to_save",35,{"type":41,"name":51,"callback":52,"priority":53,"file":54,"line":55},"wp_get_attachment_image_attributes","img_atts",10,"inline-image-base64.php",28,[],[],[],[],{"dangerousFunctions":61,"sqlUsage":62,"outputEscaping":64,"fileOperations":14,"externalRequests":24,"nonceChecks":24,"capabilityChecks":24,"bundledLibraries":67},[],{"prepared":24,"raw":24,"locations":63},[],{"escaped":65,"rawEcho":24,"locations":66},12,[],[],[],{"summary":70,"deductions":71},"The inline-image-base64 plugin v0.0.4 demonstrates a generally strong security posture based on the provided static analysis.  The complete absence of known vulnerabilities, including critical and high severity issues, is a significant positive indicator.  Furthermore, the code adheres to several good security practices, such as using prepared statements for all SQL queries and properly escaping all outputs. The limited attack surface with no discovered AJAX handlers, REST API routes, shortcodes, or cron events also contributes to a lower risk profile.\n\nHowever, there are a couple of areas that warrant attention. The plugin has a single file operation, and while the analysis doesn't explicitly flag it as insecure, file operations can sometimes introduce risks if not handled with extreme care, especially concerning user-controlled input. More critically, the complete absence of nonce and capability checks across all entry points (even though the attack surface is currently zero) is a notable concern. If the plugin were to evolve and introduce any user-facing features or AJAX\u002FREST endpoints in the future, this lack of built-in authorization and CSRF protection would immediately become a significant vulnerability. The plugin's vulnerability history being completely empty is reassuring, suggesting a history of secure development, but the lack of checks is a proactive security measure that should be addressed regardless of past incidents.",[72,74,76],{"reason":73,"points":53},"No nonce checks",{"reason":75,"points":53},"No capability checks",{"reason":77,"points":78},"One file operation (potential risk)",3,"2026-03-16T21:17:45.041Z",{"wat":81,"direct":86},{"assetPaths":82,"generatorPatterns":83,"scriptPaths":84,"versionParams":85},[],[],[],[],{"cssClasses":87,"htmlComments":90,"htmlAttributes":91,"restEndpoints":94,"jsGlobals":95,"shortcodeOutput":97},[88,89],"iib64-","eos-iib64-txt",[],[92,93],"eos_iib64_lazy","eos_iib64",[],[96],"eos_iib64_toggle_warning",[]]