for caching a neat thing you can do (as i saw in Next.js) is to always call components with unresolved nested components, sort of opaque slots, which makes the output cacheable independently from the opaque inputs. lets you cache even things that wrap other things
If you have a fediverse account, you can quote this note from your own instance. Search https://bsky.brid.gy/convert/ap/at://did:plc:fpruhuo22xkm5o7ttr2ktxdo/app.bsky.feed.post/3mdwez5agus23 on your instance and quote it. (Note that quoting is not supported in Mastodon.)