As a User, I want to be able to see a profile within 250 ms of second page load, preferably upon the first page load as well.
Currently, some profiles take several seconds to load, which could be improved with a cache. This is due to the decentralized nature of the dApp and several calls to the BCD indexer and Kepler. Because the tzprofiles.com domain is already being trusted by the user, could we use our own API and cache the results for much better and consistent performance?
For example, this profile takes 8 seconds to load completely:
sbihel
commented
3 years ago
As a User, I want to be able to see a profile within 250 ms of second page load, preferably upon the first page load as well.
Currently, some profiles take several seconds to load, which could be improved with a cache. This is due to the decentralized nature of the dApp and several calls to the BCD indexer and Kepler. Because the tzprofiles.com domain is already being trusted by the user, could we use our own API and cache the results for much better and consistent performance?
For example, this profile takes 8 seconds to load completely: