I found that native Framer Frame image fills can be transferred during the initial page load even when the frames are several viewport heights below the fold.

In my project, four service-card image fills located roughly 2,900–7,100px below the top of the page are all requested and transferred before scrolling.

The four optimized AVIF transfers total approximately 969 KB:

• 211 KB

• 325 KB

• 346 KB

• 87 KB

The images are native Framer Frame fills. The rendered images have no lazy-loading hint, and I could not find a supported loading or priority control for the fill.

It would be useful if Framer could either automatically defer image fills that are clearly far below the initial viewport, or expose a supported loading priority such as Auto / Eager / Lazy.

I would prefer to keep using native Framer fills rather than restructure the design into custom image components or loading code solely to control network behavior.

Responsive replicas in my test reused the same URLs, so the issue is not duplicate responsive transfers; it is the initial loading of genuinely below-fold native fills.