Skip to content
This repository has been archived by the owner on Jul 5, 2021. It is now read-only.

Website has bad performance (Was "Increase compression on images!") #100

Closed
GravisZro opened this issue Feb 22, 2016 · 5 comments
Closed

Comments

@GravisZro
Copy link

For love of God, please increase the compression on the websites images! 2MB for the front page background? SERIOUSLY?!

@dignifiedquire
Copy link
Contributor

This is sadly not the only perf issue with the site: WebPagetest Results
and below Chrome performance audit:

screen shot 2016-02-22 at 10 21 43
screen shot 2016-02-22 at 10 21 25

@dignifiedquire dignifiedquire changed the title Increase compression on images! Website has bad performance (Was "Increase compression on images!") Feb 22, 2016
@Kubuxu
Copy link
Contributor

Kubuxu commented Feb 22, 2016

There are many places where performance can be improved but making the image alone not weight 3MB would greatly decreases loading time.

Or consider placing static assets outside of /ipns/ because it is not being cached. Placing them under /ipfs/ would mean that they are cached.

@daviddias
Copy link
Contributor

We have come a long way :) http://www.webpagetest.org/result/170823_76_53e700e05b5b3d59f9db38cd857a31f0/

Seems we can speed things up a bid by using static asset caching http://www.webpagetest.org/result/170823_76_53e700e05b5b3d59f9db38cd857a31f0/1/performance_optimization/

@lgierth is this something you can do in the Gateway?

@Kubuxu
Copy link
Contributor

Kubuxu commented Aug 23, 2017

I think with 561 KB the ipfs.io is small enough.

@diasdavid the caching is not simple as it is served from IPNS/DNS, we have plans (and in past there were PRs for it) for it but it is more complex than it looks because we can't get good DNS TTL.

@daviddias
Copy link
Contributor

Ack! Thanks for bringing that up, @Kubuxu :)

Let's say that this is done then 🌟

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants