About the conference
CSS loading optimizations like Critical CSS are often one of the main tools to optimise for the first meaningful paint metric. This directly impacts the user experience as it lets the browser paint pixels on the screen with minimum data possible.
There are multiple parts to this problem such as:
- Detecting what all markup and CSS to load.
- How to lazy load the rest of the stylsheets.
- What strategy to use to evaluate critical CSS.
- How to do this without impacting time to first byte.
This conference is curated by Prateek Bhatnagar, frontend architect at Uber. Previously, Prateek was senior software engineer (frontend), collaborating with NextJS to help push the bar of performance on web using wrapper frameworks.
Speakers from Quintype, Publicis Sapient, Zivame and Miranj will share their experiences with implementing Critical CSS. See the Submissions and Schedule for details.
Key takeaways from this conference
- Evaluate a variety of options for improving important web vitals.
- Knowledge about tools and frameworks which are providing these optimizations out of the box.
- Awareness about popular techniques around dead code elimination.
Contact information: For inquiries about participating in the conference, post a comment at https://hasgeek.com/jsfoo/css-loading-and-critical-css/comments
For more updates, follow JSFoo on Twitter
AS
Amogh Sahasrabhojanee
@ags1773
Inlining CSS from react component library to improve web vitals
Submitted Aug 20, 2021
We at Quintype have built a react framework which does isomorphic rendering. We also have a component library called Arrow which provides pre-styled customizable react components. For example some rows from here are being used here.
The problem:
On integrating Arrow components in our app, the pages were having quite poor web vitals. One of the reasons being the component CSS wasn’t being inlined during SSR
Solution:
Inline some of the CSS. We don’t know which components would be used above the fold at build time, since that can be customized from the CMS. However we do know this at runtime - the CMS sends it as a config. So we generated seperate CSS files for every library component, created seperate bundles for every row component in our app and changed the SSR logic to inline the styles of the 1st row component.
This isn’t really critical css but it improved our scores - CLS has become close to 0
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}