a problem repeatedly occurred with https://www.chase.com Safari 26.2 How to discover -- ¿What is this problem? to try to fix.

The quickest way to find errors is to click the red "stop sign" icon (shown within the blue circle below):

That might not be the best example. When I loaded that site earlier there were many different ones. Most of the ones in the above example were caused by some apparently defective Javascript code:

blue-vendor, hmm. Probably an "advertising partner" or some other information-harvesting scheme, but whatever. Most sites are infested with them. Most sites don't care to investigate just what their advertising partners are doing, or why. All they care about is the 💰 they get from hosting them. Banking sites are just behind "news" 🙄 sites in that regard. Nearly all the "free" ones are practically unusable. If I want real news I gladly pay for it.

More to the point of your original concern though — many (most?) websites are going to incorporate code that references other webpages, which can in turn reference others, etc. How many such redirects are acceptable though. Three? Five? Sure. Ten, maybe. A hundred? Of course not. Webkit / Safari imposes a limit to how many such page reloads are acceptable, and when it reaches that limit Safari pulls the plug. Why?

Bear in mind one of Apple's primary concerns (besides their arguably over the top user privacy and related security standards compliance) is device efficiency. Their core business being portable devices, they make a very big deal about how long they go between charge cycles. If a website is poorly coded or so laden with slick advertisements or whatever Apple does not want to take the blame for them draining your battery. So whereas Firefox etc don't really care about that (they don't build the device) and Google cares even less (not their business model) Apple hard-coded limits into Safari. The website earns its place in a "wall of shame" illustrated by a "problem repeatedly occurred" and / or "this page was using significant energy" etc.

Ideally, their customers (you and I) will shame website developers into getting their act together, but I'm not holding my breath. Advertising makes the world go round, website coders get paid to grab eyeballs, so persuading website developers to fix their garbage code is a nearly impenetrable wall.

Clearly major marketers such as Amazon would never tolerate defective page code, but as long as banking customers put up with that **** things will never change.

Needless to say I don't use Chase.

Tried the Developer Console?

Mine shows lots and lots of errors, and there certainly seem to be an excessive amount of page reloads or redirects, but no "problem repeatedly occurred" yet.

It's no secret that Chase has not been keeping up with developer guidelines, and in my opinion their website is rather poorly designed. A serious retailer would go out of business, but banks refuse to die.

Grant Bennet-Alder wrote:

I don't recall ever seeing ads for anything but chase itself on this site. When it might be deposit accounts, banks seem to be encouraging Trust.

Third-party tracking activity wouldn’t surprise, even if there are no overt advertisements shown. Based on what John Galt posted, this does seem to be the case, too.

Any third-party password managers installed?

Which DNS services are you using? ISP? Cloudflare via private relay and ODoH?

Here’s a write-up on same-origin policy, which is showing in what John Galt posted: https://cseweb.ucsd.edu/~dstefan/pubs/stefan:2014:protecting-slides.pdf

🤷🏻‍♂️

There's only so much anyone can do to debug someone else's website. I'd keep pestering Chase. Tell them to actually test their site...?

Going way out on a limb... reboot your router?

Flush DNS cache?

This is quickly approaching voodoo territory though.

Click "Errors". Nothing?

Your Console isn't even showing any warnings. That's unexpected.

I think all you can do is keep looking. Ads are only one possibility. It may not have been the best one to suggest.

Earlier today I found many different errors, after randomly navigating various page elements. Attempting to debug other people's code is a time-consuming challenge. Sometimes you get lucky (a story I described here a few weeks ago).

Perhaps I went off in a wrong direction, in which case it's back to basics. Tried clearing history too? It was probably one of the first things you did, but you didn't explicitly say so.

Or perhaps it is a temporary affliction. Or maybe they'll fix it...

This is all the more reason I believe browsers in general are going away... eventually. They're a hacker's paradise and a perpetual security nightmare. It has always been the wild west, but browser e-commerce has devolved into an insane screaming money-grabbing bazaar too lucrative to resist.

Safari is way ahead of all the rest in confronting those challenges but it's an arms race with no end. We're far better off using curated apps. That's what the future holds... as long as Apple can survive the legal battles. If they can't, we're done. Nice while it lasted.