gistfile1.txt

I both agree and disagree, if that's possible...

- - - - - -

Agree: it's odd to talk about the page fold, where numerous usability studies prove that users scroll, 
the web is a vertical medium, pages are long and the fold isn't a thing.

Disagree: it's odd to assume that what appears in that first viewport onto a page isn't higher-impact 
for a user than the rest of the page. It sets tone, usually navigation / wayfinding, titles and introduces 
what you're doing. It's your first impression.

- - - - - -

Agree: it's odd to consider 'above the fold' as the measure for where/how one inlines / prioritises CSS load. 
Because there is no fold.

Disagree: it's odd to consider that inlining or prioritising CSS in some way (be that 'critical', 'skeleton', 
'core' etc) is a bad idea, given that it can help perceptions of speed.

- - - - - -

Agree: this is a conversation that is in part prompted by those of us pushing RWD / device-agnostic builds 
looking for yet more performance / perceived speed gains for page loading

Disagree: the conflicting advice (users scroll, there's no fold, but the a first impression is important 
and there will be some first-viewport priorities) has been around for a long time before RWD came around.
So I'm not sure about setting it up as 'responsive design telling us' :)

- - - - - -

In summary; 'the fold' is just an unfortunate use of term. And the conversation around it / viewports / 
critical css is way too nuanced for twitter limits!

B xo