WordPress maintenance or security needs? Reach out!
TLDWP

Plugin: native-lazyload (Used by 1,344 domains)

Security snapshot

Across 1,344 native-lazyload WordPress sites indexed by TLDWP, compared to the all-WordPress average.

Grade A 1% Grade B 2% Grade C 4% Grade D 12% Grade F 80%
Fail the header check (F)80%vs 82.6% avg
Leak usernames44%vs 38.6% avg
Expose a sensitive file2.1%vs 1.8% avg
Use HTTPS97%vs 96.3% avg

What stands out

TLDWP currently associates 1,344 indexed WordPress sites with native-lazyload, equivalent to 0% of the current WordPress dataset.

The largest measured difference is username enumeration: 43.8% versus 38.6% overall (+5.2 percentage points).

Header-grade F is 80.3% vs 82.6% overall (-2.3 pp); HTTPS adoption is 97.4% vs 96.3% overall (+1.1 pp); Sensitive-file exposure is 2.1% vs 1.8% overall (+0.3 pp).

These are observational associations among sites where TLDWP detected native-lazyload, not evidence that the technology, provider, or domain attribute caused a security outcome. See the overall WordPress security baseline.

Infrastructure patterns

Infrastructure detected alongside native-lazyload. Percentages are within sites where that specific signal was detectable; the baseline compares the same signal across detected WordPress sites overall.

Co-occurrence describes technologies observed on the same sites. Detection coverage varies by signal, and an association does not imply that one technology caused or selected another.

Native Lazyload

Lazy-loads media using the native browser feature. Learn more about the new loading attribute or view the WordPress core ticket where inclusion of a similar implementation in WordPress core itself is being discussed. If the loading attribute is not supported by the browser, the plugin falls back to a JavaScript solution based on IntersectionObserver.…

Domain Version Exposures Headers Last Checked
h*i*u*n*s*i*e*k*k*k*.com (WP 7.0.4) F Sep 10, 2026
f*n*e*.jp (WP 7.0.4) D Sep 10, 2026
m*m*a*h.com (WP 7.1) F Sep 10, 2026
a*a*u*i*l*.jp (WP 6.0.14) F Sep 10, 2026
j*t*u*y*p*t.fi D Sep 10, 2026
k*o*e*a*m*v*n*.com (WP 5.8.15) F Sep 10, 2026
a*m*x.com F Sep 10, 2026
x*h*r*a.vn D Sep 10, 2026
b*o*-*l*x*o*p*n*a*o*.de (WP 7.1) F Sep 10, 2026
k*a*w*b*o*u*i*n*.com (WP 6.9.7) C Sep 10, 2026
o*e*c*l*u*e.com (WP 7.1) F Sep 10, 2026
k*a*i*l*w*r*u*.com (WP 7.1) F Sep 10, 2026
n*y*t*s.net (WP 7.1) F Sep 10, 2026
e*u*a*s*u*o*.c*m.br (WP 7.0.4) F Sep 10, 2026
h*a*g*i*t*u*n*t*r*.com (WP 5.7.17) C Sep 10, 2026
k*n*a*s*l*b*a*d*n*e.com F Sep 10, 2026
k*n*a*s*-*n*u*u*i*t*u.com (WP 5.8.15) F Sep 10, 2026
e*u*r*s*h*l*e.com (WP 5.5.3) F Sep 10, 2026
g*m*0.jp (WP 6.5.10) F Sep 10, 2026
e*r*y.com B Sep 10, 2026
o*y*o*t*o*d.com F Sep 10, 2026
c*l*r*e*.fi (WP 7.1) F Sep 10, 2026
t*m*k*.com F Sep 10, 2026
r*v*e*c*m.com (WP 6.6.7) F Sep 10, 2026
a*f*l*a.com (WP 6.4.10) F Sep 10, 2026
l*l*e*a*.no (WP 6.2) C Sep 10, 2026
h*n*m*t*-*e*n*t*u.c*.jp (WP 6.3.8) F Sep 10, 2026
p*a*l*w*i*e.tokyo F Sep 10, 2026
w*s*e*g*i*d*f*r*f*s*e*.c*.uk D Sep 9, 2026
k*h*n*-*a*i.com (WP 7.1) F Sep 9, 2026
s*e*s*2*.com (WP 7.1) C Sep 9, 2026
k*r*e*m*s*c.com F Sep 9, 2026
r*e*d*n*s.jp F Sep 9, 2026
s*l*n*-*e*l*r*x*s.de (WP 6.9.7) F Sep 9, 2026
a*y*g*-*.com F Sep 9, 2026
t*k*s*a.com C Sep 9, 2026
k*i*a*n*.net (WP 6.7.1) F Sep 9, 2026
t*k*s*.com C Sep 9, 2026
t*k*k.com C Sep 9, 2026
d*e*b*.com F Sep 9, 2026
g*a*k*u*l*a*b.com F Sep 9, 2026
r*o*o*e.com (WP 6.2.11) F Sep 9, 2026
r*o*o*e*g*m.com (WP 6.2.11) F Sep 9, 2026
t*u*u*j*b*k*.com (WP 6.9.7) F Sep 9, 2026
m*n*t*-*e*k*t*u*n.tokyo (WP 6.9.7) F Sep 9, 2026
h*r*s*i*a*n*k*e*.com (WP 5.7.17) F Sep 9, 2026
k*b*-*u*u*a.com F Sep 9, 2026
k*b*-*o*e*k*n.com (WP 5.8.15) F Sep 9, 2026
t*e*-*n*e*s*e*e*i.dk (WP 7.0.4) F Sep 9, 2026
t*k.fr C Sep 9, 2026
f*c*o*d*i*y.com (WP 7.0.4) F Sep 9, 2026
t*u*i*o*p*o.com (WP 6.0.14) F Sep 9, 2026
o*i*e*-*a*.com F Sep 9, 2026
h*r*k*w*-*n*o*.com (WP 7.1) F Sep 9, 2026
o*g*k*r*r*n.com (WP 6.2.2) F Sep 9, 2026
h*p*o*i*u.com (WP 7.1) B Sep 9, 2026
p*a*e*b.fi (WP 5.8.15) D Sep 9, 2026
m*x*c*n*e*t.ru F Sep 9, 2026
o*e*p*e*s*r*.com (WP 5.8.15) F Sep 9, 2026
s*a*e*w*d*.com F Sep 9, 2026
r*e*e*i*c.com D Sep 9, 2026
s*-*h*g*t*z*k*n.com (WP 5.5.20) F Sep 9, 2026
c*l*a*o*a*e*n*e*l*h*c.ca (WP 6.9.5) F Sep 9, 2026
s*z*i*a*o*k*.com F Sep 9, 2026
h*m*x*r.com (WP 6.6.5) D Sep 9, 2026
r*d*w*e*l.com (WP 6.9.4) F Sep 9, 2026
k*k*o*s*i*o*y*.com (WP 6.2.11) F Sep 9, 2026
k*k*o*-*k*n*.com (WP 6.2.11) F Sep 9, 2026
b*s*e*-*e*n*n.blog D Sep 8, 2026
e*r*n*r*.ru (WP 5.7.17) F Sep 8, 2026
k*i*o*t*k*.com D Sep 8, 2026
h*l*a*i*l*.com (WP 6.7.7) F Sep 8, 2026
i*a*i.space (WP 5.7.12) F Sep 8, 2026
b*a*e*o*o*i*s.com (WP 6.5.10) F Sep 8, 2026
h*k*n*-*i*i*g.com (WP 7.1) F Sep 8, 2026
w*l*w*r*.org (WP 6.8.8) F Sep 8, 2026
s*p*i*.lv (WP 7.1) A Sep 8, 2026
o*c*i*c.com A Sep 8, 2026
m*d*c*r*o*e.com F Sep 8, 2026
c*e*n*n*.net (WP 6.9.7) F Sep 8, 2026
h*g*r*s*i*s*o*o.com F Sep 8, 2026
m*d*c*l*s*r*c*.com (WP 6.2.11) F Sep 8, 2026
t*u*h*r*o*.com (WP 7.1) F Sep 8, 2026
m*d*a*e*i*c*n*i*d*v*r*e.com C Sep 8, 2026
m*d*a*e*i*w*u*e*d*v*r*e.com C Sep 8, 2026
m*d*a*e*a*i*o*d*v*r*e.com C Sep 8, 2026
s*u*a*s*o*o*e*e*.com (WP 5.5.20) F Sep 8, 2026
g*o*p*-*o*t*i*e.fr D Sep 8, 2026
d*m*i.ru (WP 6.8.8) F Sep 8, 2026
k*t*d*c*i*t*r*e*i*e.com F Sep 8, 2026
a*n*v*r*a*y*c*e*r.com F Sep 8, 2026
s*o.nl F Sep 8, 2026
s*u*-*a*s.com F Sep 8, 2026
f*s*i*a*l*t*r*t*r*d*i*c*e*e*.pl (WP 6.2.11) F Sep 8, 2026
b*a*d*a*k*r.com (WP 6.9) F Sep 8, 2026
d*v*d*a*h*r*y.com (WP 6.8) F Sep 8, 2026
k*y*o*d*a*.jp (WP 7.1) B Sep 8, 2026
m*d*a*k*j*r*k*u*i.com (WP 7.0.4) D Sep 8, 2026
s*n*o*a*u*.com (WP 5.9.16) F Sep 8, 2026
k*s*i*a*a*i*i*e*a*o.com (WP 7.0.4) F Sep 8, 2026