Page Load Stutter in Safari

Elements
1

Hello All,

I’m working on building out a website and am running into a stutter issue on load in Safari.

The website is for a company that buys and sells airplanes. Apart from the actual listings, there is an entire library of aircraft profiles, a blog, and a podcast.

The site is image heavy, so on pages with multiple images, I’m using .webp format, along with different sizes of the images. So, for example, on a top-level page for the library that offers multiple models to choose from, the images are sized at 902 x 600.

When I load a page in Safair and start scrolling immediately, I get half loaded or blank or unclickable buttons for 2-6 seconds, then everything shows up all at once and the page is then useable.

Screenshot 2026-05-05 at 9.22.34 AM
Screenshot 2026-05-05 at 9.22.34 AM1920×1292 134 KB

I obviously want visitors to have the best experience, and I use Safari heavily, so I’m hoping there’s something I can do to fix this.

Thanks in advance for any help you can share.

2

Hi @chet

Any chance you could share the project file via Elements Cloud?

3

Adding this comment for future readers.

Dan and I worked over private message using my project file and the issue appears to be an issue with my web host.

4

A combination of some images with no lazy loading enabled, no/insufficient caching, and slow server performance. A combination that seems to be causing that Safari stuttering at your current web host.

Actually the issue was a Contact Form that was turned into a Global and used across multiple pages with the Cloudflare Turnstile Spam Protection option enabled. We are investigating if it’s possible to place a Contact From in a Global that spans multiple pages with 1 Cloudflare Turnstile widget (seems like it might not be as it was throwing an error causing the page stuttering in Safari).

Actually, the issue seems to be with any of the Captcha options slowing down page rendering in Safari. This is something we are investigating. :magnifying_glass_tilted_left:

Anyway mystery solved. :slightly_smiling_face:

5

Many, many, many thanks to @differentdan for running this all the way to the ground.

We ruled out just about everything and he came through with the solution to get the site behaving as expected.