web3-storage
[research] Website perf should be excellent!
Review performance of web3 storage site (explore, measure, propose iterative improvements).
Original Request
Some things to investigate:
- Why is
magic-sdkpulling in 3MB of resources from https://assets.auth.magic.link across 19 requests - We need to trim down the 3MB of tailwind css.
- #61
- https://github.com/web3-storage/web3.storage/issues/195
- Logging in using Github takes a very long time with little feedback.
Requests to assets.auth.magic.link on staging
Requests to assets.auth.magic.link on nft.storage
@jdiogopeixoto can you get the css-purge / tailwind optimiser working on the website build to trim down that 3MB css bundle please.
Why is magic-sdk pulling in 3MB of resources from https://assets.auth.magic.link/ across 19 requests
I don't think we have any control over this because it's an external provider. On slightly optimistic news, it looks like the amount of transferred data is only around 740kb after gzip does it's thing.
Logging in using Github takes a very long time with little feedback.
I think this is just a problem in OAuth land. It currently takes about 7 seconds which is a little slower than average. That said, I think there were some recent improvements here.
We need to trim down the 3MB of tailwind css.
I think João fixed this already. I'm now only showing 57kb of CSS for web3.storage.
@drewdelano Continue perf review of site. As you find any areas of concern, let's ticket separately (using this ticket as the research tracking ticket we can close once review is done).
I continued to look, but everything seems to be working well now as far as I can tell
Please back this up with metrics. Let's track our lighthouse score, or any similar prefered measure that we can record in CI and ensure that we don't introduce regressions and work towards improving.
that we can record in CI and ensure that we don't introduce regressions and work towards improving.
@olizilla Does this ticket include adding this to the CI pipeline or just taking a baseline?
This ticket is a provocation to make our web perf excellent, and keep it excellent. It was deliberately open ended so that whoever picks it up gets to figure out a neat way of making that happen. Suggestions welcome!
In geneal, please approact all these issues with a "how can I leave this better than I found it?". Round trip times on a fully async team can be really slow. You can avoid getting blocked by making proposals and PRs to make the project better! They gonna be welcomed! Even if we need to change direction, they push the conversation forward more quickly.
FYI large performance concern related to rendering discovered and getting corrected in #1953 That will have a significant impact on performance across the site.