News for hackers. Stuff that matters.
Re:Google AMP – A 70% drop in our conversion rate by technion on Wednesday August 08, 2018 @08:52PM (#17720936)
The recommendation you describe is a violation of the AMP standard, which strictly disallows this for performance reasons.
Re:Google AMP – A 70% drop in our conversion rate by minitech on Wednesday August 08, 2018 @11:56PM (#17721552)
Sorry, I was commenting generally. Don’t know about AMP. How does that make sense, though? What performance reasons could there possibly be for inlining CSS that doesn’t apply to any element in a page?
Re:Google AMP – A 70% drop in our conversion rate by technion on Thursday August 09, 2018 @05:40AM (#17722771)
Likewise, I'm sorry, I didn't mean "you have to inline CSS that doesn't apply".

However, if you have non-render blocking CSS, or CSS that's used for below the fold or generally lower down the page content, "only render critical CSS inline" is usually coupled with "and then have the rest of your CSS in an external stylesheet". Which you are not allowed to do.

Accordingly, it's ALL inline, all the time.

Re:Google AMP – A 70% drop in our conversion rate by londons_explore on Thursday August 09, 2018 @06:09AM (#17722911)
When surver push of resources gets better supported by browsers, I bet AMP will be updated to change this restriction.