Skip to content
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

Audits: Detect byte and time savings from bundled resources #1517

Closed
4 of 5 tasks
patrickhulce opened this issue Jan 24, 2017 · 4 comments
Closed
4 of 5 tasks

Audits: Detect byte and time savings from bundled resources #1517

patrickhulce opened this issue Jan 24, 2017 · 4 comments
Assignees
Milestone

Comments

@patrickhulce
Copy link
Collaborator

patrickhulce commented Jan 24, 2017

Across the byte efficiency audits time saved from data URI resources, stylesheets added from script is not accurately reflected. Ideally we'd be able to attribute these resources to the actual network record they come in on (the JavaScript or HTML file that included them), but at a minimum we can estimate the network throughput and time saved on average.

@ebidel
Copy link
Contributor

ebidel commented Jan 24, 2017

I've been thinking it would be really nice to work towards very visual infographic-type callouts in the report. High level aggregations, but also breakdowns as you drill into each of these audits. Something like:
https://pageweight.imgix.com/jobs/99166054-29d7-413a-a0c4-1d7c8e30a8e2.html?utm_source=share-link

I'm visual. Users are visual. The world loves visuals!

@brendankenny
Copy link
Member

see also May 2016 UX mocks. There are various Irish/Lewis mocks spread out in issues as well (cc @paulirish)

(no pie charts, tho :P)

@patrickhulce
Copy link
Collaborator Author

patrickhulce commented Jan 24, 2017

#1500 is related to first bullet on attribution of inline stylesheets

update: #1544 is tracking proper inline style attribution.

@patrickhulce
Copy link
Collaborator Author

Marking this as closed since the last remaining enhancement is now orthogonal to the original intent of the issue and is tracked separately in #1544.

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

No branches or pull requests

3 participants