Skip to content
This repository has been archived by the owner on Dec 27, 2020. It is now read-only.

performance: Avoid enormous network payloads #116

Open
ychoy opened this issue Jan 13, 2020 · 1 comment
Open

performance: Avoid enormous network payloads #116

ychoy opened this issue Jan 13, 2020 · 1 comment
Assignees

Comments

@ychoy
Copy link
Collaborator

ychoy commented Jan 13, 2020

According to this audit report from Chrome Dev Tools, this can be enhanced to improve performance:

Large network payloads cost users real money and are highly correlated with long load times. Learn more: https://web.dev/total-byte-weight?utm_source=lighthouse&utm_medium=devtools

URL Size
/4de5fac….jpg(census-2020.herokuapp.com) 1,804 KB
/0850b36….jpg(census-2020.herokuapp.com) 1,349 KB
/bundle.js(census-2020.herokuapp.com) 1,181 KB
/fd83f8b….jpg(census-2020.herokuapp.com) 1,092 KB
/71a5f84….jpg(census-2020.herokuapp.com) 819 KB
/34a2f27….jpg(census-2020.herokuapp.com) 725 KB
…en_US/base.js(www.youtube.com) 398 KB
/8f026a6….jpg(census-2020.herokuapp.com) 301 KB
…imgbin/player-co….png(s.ytimg.com) 131 KB
/edcbb0f….png(census-2020.herokuapp.com) 127 KB
@aelar13
Copy link
Collaborator

aelar13 commented Mar 4, 2020

I'm going to try to at least reduce the file size somewhat for the header graphics.

@aelar13 aelar13 self-assigned this Mar 4, 2020
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

2 participants