Disable Lazy Load
View on WordPress.orgScores higher than 70% of indexed plugins
About
Activate this plugin to disable the Lazy Loading feature that was added in WP v5.5.
What It Does
Disable Lazy Load is a single-purpose plugin that turns off WordPress's native lazy loading for images, iframes, and embeds, which was introduced in core version 5.5. Once activated, images and other media load immediately on page render rather than waiting until they enter the viewport. There are no settings, configuration panels, or additional features bundled in.
Who It's For
This plugin is best for site owners experiencing broken lazy load behaviour, layout shifts, or CLS issues caused by WordPress's native lazy loading, particularly on sites where above-the-fold images must render instantly. It is well suited to photography portfolios, art galleries, product showcase catalogues, and real estate listings where the first viewport of imagery is critical to user experience and conversions.
Who Should Skip It
If you are satisfied with WordPress's built-in lazy loading, or you already use a caching and image optimization plugin that handles loading strategies, installing this plugin is redundant. Developers comfortable adding a single line of code to their theme's functions.php can achieve the same result without an extra plugin.
The Bottom Line
Disable Lazy Load does exactly one thing, and does it reliably, making it a reasonable choice for anyone whose site suffers from WordPress's default lazy loading without needing broader optimization tooling. Its tiny scope, lack of support infrastructure, and modest install base mean power users may prefer a more feature-rich performance plugin. For its narrow purpose, it is a low-risk install with a quality score of 78.91 out of 100.
Related Plugins
Pick this instead if you want broader image optimization including compression, WebP conversion, and finer control over lazy loading behaviour.
Choose this if you need to aggregate and defer scripts and CSS alongside disabling or replacing lazy loading as part of a wider performance tuning strategy.
Go with this when your priority is serving next-gen image formats and you want to disable native lazy load only because you are replacing it with a custom solution.
Pick this if your main concern is gallery presentation and you want lazy loading replaced with smarter thumbnail loading in lightbox contexts.
Choose this if iframe lazy loading is your specific problem and you want facades that replace YouTube embeds with lightweight placeholders.