Native Lazyload

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

Directory rank vs rivals

wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you

How often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.

Share of active installs on each version of this plugin · 100% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

Refined from the date this plugin crossed into its current band.

No paid tier is visible, so we don't put a figure on revenue or sale value: that would be guessing. The install base is a real asset to an acquirer, just not one public data lets us price. A small install base leaves thin data to model from.

1. ★★★★★ othman19

   4.1y ago

   How can I unable the lazy loading of my popups ?

   Read on wp.org ↗
2. ★★★★★ NikosTsolakos

   4.5y ago

   Im really happy that Google is creating plugins for our projects BUT keep them up-to-date please… you’re the God of the internet, a trillion dollar company.

   Read on wp.org ↗
3. ★★★★★ bloup

   5.2y ago

   No benefits and may it is bad for SEO This topic was modified 4 years, 11 months ago by bloup. This topic was modified 4 years, 11 months ago by bloup.

   Read on wp.org ↗
4. ★★★★★ bloup

   5.6y ago

   I used lazyimages_without_scroll_events.js of puppeteer by Google and found that this plugin added a blank space at the bottom of page crawled by googlebot. I guess, bots can see this as a form of cloaking. The page weight is different between a page that is not being scrolled (googlebot) and a page that is scrolled (scrolling down on a smartphone). This topic was modified 5 years, 6 months ago by bloup. This topic was modified 5 years, 6 months ago by bloup.

   Read on wp.org ↗
5. ★★★★★ bloup

   5.7y ago

   This plugin adds loading=”lazy” and then, the browser lazy loads the image. I think that native lazy loading performed by the browser is the only viable solution for lazy loading. For many years, I tried to implement lazy loading on my websites. I faced many issues. Once images were not crawled. Once my website was penalized because of cloaking. Versions differed depending on the client. I am enough with javascript scripts that slow down the pageload and negatively impact the pagespeed insight. I think that for now and in the future, the native lazy loading is the only way to go for lazy loading. This topic was modified 5 years, 6 months ago by bloup.

   Read on wp.org ↗
6. ★★★★★ gkwebph

   6.0y ago

   Hey guys – Can you please fix this in the latest Safari. Thanks!

   Read on wp.org ↗
7. ★★★★★ havig

   6.5y ago

   First, did not break my site and it did lazyload most of the page images. It does not lazyload images if they are served from a different host. Example, unbounce, etc. I will add another caveat, all of my images and their versions are always carefully resized and highly compressed. Checked with lighthouse and my score took a hit downwards. 13 points down on performance score. I tested on my Staging area, uncached. FCP went from 2.1s to 4.2s, all of the other metrics, including time to interactive, CPU idle, speed index and First Meaningful Paint took a dive. I will chuck this to I was already hyperoptimized and lazy loading is not truly needed on my site/s. But I would advise others to try it out (not on their live site) and test speed with Google Lighthouse before and after.

   Read on wp.org ↗
8. ★★★★★ shawn caza

   6.5y ago

   Seems to work well. On browsers that don’t support lazy loading, it doesn’t seem to load the images as soon as I would like. As in there can be a bit of a delay between scrolling and the image appearing on screen. Not to bad though. Not going to worry about it as native image loading is the way of the future and will be implemented into more browsers.

   Read on wp.org ↗

Recent releases and news for this plugin

1. — Version 1.0.2 Fix broken images which are using data URI scheme (e.g. base64-encoded images). Props ieim . Fix images in IE 11 not being loaded until the user starts scrolling. Props Soean . Fix image loading script not working in IE1 1.0.2
2. — Version 1.0.1 Improve compatibility with other plugins by using more specific class and only adding it for JS fallback. Run lazy-load script on DOMContentLoaded when necessary to improve compatibility with plugins like Autoptimize. Do 1.0.1
3. — Version 1.0.0 Initial release 1.0.0

Automated install-time checks, tested on PHP 7.2.16 · WP 5.3

Translated into 19 languages, 18 at 90% or more

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

1. 2026-06-27 6K+ → 5K+ down after 2 days in tier
2. 2026-06-25 5K+ → 6K+ up after 1 days in tier
3. 2026-06-24 6K+ → 5K+ down after 327 days in tier
4. 2025-08-01 7K+ → 6K+ down after 263 days in tier
5. 2024-11-11 8K+ → 7K+ down after 271 days in tier
6. 2024-02-14 9K+ → 8K+ down after 215 days in tier
7. 2023-07-14 10K+ → 9K+ down

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

• Disable Lazy Load 10K+ installs · 4.3★ · 3 shared tags A
• Preloader 10K+ installs · 4.0★ · 2 shared tags B
• Custom Preloader 100+ installs · 4.0★ · 2 shared tags C
• D Disable Lazy Loading for IFRAMES 50+ installs · 3.6★ · 2 shared tags C
• Ipp Simple Loading 40+ installs · 4.1★ · 2 shared tags B
• F Full Page Load 20+ installs · 4.0★ · 2 shared tags D

Embed this report card

Drop a live Pulse card for Native Lazyload into a readme, a review or a deck. It updates itself.

Native Lazyload: 5K+ active installs, 3.0★ (31 reviews). Plugin Pulse (WP Mayor), as of 2026-08-29. https://plugins.wpmayor.com/plugin/native-lazyload