Preload LCP Image


This plugin will add the ability to preload the largest contentful paint (LCP) Image on an individual page or post. This is designed to remove the “Preload the image used by the LCP element in order to improve your LCP time” warning that Google’s Pagespeed Insights sometimes serves.

For Support

I offer support in two places:-

On Github

This project is now on github, you can view the repository here. There are other versions, but this is the one I’ve put up, so where all the developmental will be tracked.


  1. Upload the plugin to the /wp-content/plugins/ directory or use the Add New feature
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Go to any post and page and specify the LCP Image for that page.

Should you wish to use this plugin for custom post types, go to Settings > Preload LCP Image. By default it appears on posts and pages although you can set it to appear on any custom post type on this page.

For more guidance on how to determine the URL to use, please use my guide on how to determining the LCP image for a WordPress post


2023 年 2 月 1 日 3 則留言
Plugin working as described, really like that you added “fetchpriority high” I do have a suggestion for some future update though: I have a large site with nearly 1000 posts, would love if the plugin could automatically add Preload to post featured images, or possible by Class Name, in my instance that would be: class=”post-featured-image” This would save users with large sites from having to updated hundreds if not thousands of posts, Thanks for listening and good luck with Preload LCP Image, Good Plugin!
閱讀全部 1 則使用者評論


以下人員參與了開源軟體〈Preload LCP Image〉的開發相關工作。


將〈Preload LCP Image〉外掛本地化為台灣繁體中文版


任何人均可瀏覽程式碼、查看 SVN 存放庫,或透過 RSS 訂閱開發記錄



  • Fixes a bug that causes a console error that ignores the “as” types due to unknown “as” or “type” values, or non-matching “media” attribute.
  • Improves the UX of the page in question


  • Allow the ability to specify different URLs for mobile or desktop viewpoints.


  • Tested with WordPress 6.4


  • Tested with WordPress 6.3


  • Tested with WordPress 6.2


  • First Public Release