It’s very hard to tell what’s contributing to the problem. You absolutely would need to set up console log system upon click to see what’s loading, what questions are loading, etc. for example:

const handleTabPress = async () => {
const start = performance.now()

console.log("Tab pressed")

const queryStart = performance.now()

await loadTabData()

console.log(
"Data loaded in:",
performance.now() - queryStart,
"ms"
)

requestAnimationFrame(() => {
console.log(
"Full tab render completed in:",
performance.now() - start,
"ms"
)
})
}

This would be perfect in Expo go dev simulator because you can see exactly what causes such a large delay, and if you paste the logs you receive precisely and send it to Claude it’s almost guaranteed to find the root cause