-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Performance] Photo optimization #444
Comments
@mwpark2014 is the link of the jpeg to the 404 error page? |
I'm actually not sure, since that example is originally from @zoobot |
now looking at it, its from the 404 error page. I can mock up something for the 404 with an svg and text. That would eliminate the need to load a photo. The 404 should be the least intensive page that loads. Will create a separate issue for that. But WebP is the move especially for the amount of images that will be present from the tree details, and in the future user uploads from selfies. |
Thanks, good idea to have no photo on 404. |
@ri0nardo It is a link for the 404 I think... Someone added that on a redesign or on adding a 404 page for the first time. @Tijani-zainab And specify we should be using webp or svg? |
IMO, let's delegate someone to look into this task and not have other developers worry about it. Let's try to avoid premature optimization. Most photos aren't loaded on page load iirc, so I wouldn't be too sure that switching to webp is worthwhile. It's also relatively easy to go back at some point and swap out all .svg|png|jpeg|etc for webp in the future when the time comes |
These pages, including the 404(NotFound) are wrapped in Suspense but not lazy loaded... import About from '@/pages/About/About'; |
#476 |
I want to save this for a new person that came last week that wanted to do frontend work. Perfect task for anyone new |
I agree that this is very pleasing to the eye :D |
Hello @zoobot Oh, I could do that. |
Non-trivial project for optimizing photos. Need someone to investigate and drive
At least some of these should be considered doing within the server or CDN layer
If scope ends up being large, please break down into smaller tasks / git issues!
The text was updated successfully, but these errors were encountered: