It's important to note that PSI is NOT saying the Credits Page itself is failing and is instead saying there is insufficient URL-level data and so it's dropping back to overall origin-level data:
Therefore, this page may be fine, and it may be other, heavier pages pulling down the aggregate origin-level score.
CrUX data (as shown in PSI) is a high-level summary and you should combine this with other analytics to see what pages users are visiting on our site most as those are the pages to concentrate on. The best way is to collect the Core Web Vitals data through a RUM solution so you can see exactly what pages are contributing what INP values to the overall score. It looks to me like you have a debugbear script on there so maybe you already have this data?
Alternatively Google Search Console can give a ranked listing of the pages impacting a Core Web Vitals group.
Large, complex pages with large DOMs or lots of complex CSS can indeed mean more work for the browser, but it's far from the only reason. JavaScript is often a cause too and there's lots on your site that requires a fair bit of processing (Consent Providers, Tag Managers, Ads). These are part and parcel of running a website for many, but that doesn't negate the fact they slow your website down.
There was a similar change in March, so does that give clues?
If your site has not changed, then it could be a result of something else changing (e.g. Heavier ads being displayed on the site?) Or the user population (e.g. if you have an influx of users on slower devices, perhaps due to a marketing campaign?). The latter should be easier to confirm with Google Analytics.
Hopefully that gives you some ideas about where to look next to explain this. I would also say that 239 ms, is just outside the 200 ms recommendation so is not a terrible score. Still it would be great to get under that threshold and understand why it fluctuates some months to help you do that!