We noticed that login protected phewebs (r13, r14) feel noticeably slower than the open ones. The hypothesis is that we confirm the user's membership from Google on every API request. This should not be needed. We should check the membership once and then rely on session token, until the token expires and the user needs to login again. This is of course just a hypothesis and needs more investigating, but it would explain the difference in load speeds of the phewebs.
We noticed that login protected phewebs (r13, r14) feel noticeably slower than the open ones. The hypothesis is that we confirm the user's membership from Google on every API request. This should not be needed. We should check the membership once and then rely on session token, until the token expires and the user needs to login again. This is of course just a hypothesis and needs more investigating, but it would explain the difference in load speeds of the phewebs.