-
Notifications
You must be signed in to change notification settings - Fork 151
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The videos in the report are way to big, making the page use 100MB of traffic to load and almost crashing Firefox.
I suggest you either remove the 30FPS vs AFMF or the 60FPS vs AFMF comparison, reduce the video size to 720p maximum and decrease the video lenghs.
Also consider re-encoding them to save even more space.
The raws were 4K and 500MB each. There's so much you can re-encode a video and still be able to show its details. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking care of the Youtube videos.
Imo, the embeds could be a bit smaller (side by side maybe?).
The much bigger problem however is still the page size...
Doing a quick profile, it takes 35MB of traffic to load, compared to 7MB for the December and 8MB for the November report.
Taken care of, rejected media from the draft I included by mistake. |
Co-authored-by: Schplee <[email protected]>
Co-authored-by: Schplee <[email protected]>
No description provided.