2018-04-10
1909
#css#node
Benjamin Johnson
351
Apr 10, 2018 ⋅ 6 min read

How CSS works: Parsing & painting CSS in the critical rendering path

Benjamin Johnson Software engineer. Learning every day, one mistake at a time. You can find me online at benjaminjohnson.me.

Recent posts:

Build Full-Stack App React Goxygen

Build a full-stack app with React and Goxygen

We show how to use Goxgen to scaffold a full-stack React app. See how to integrate React with Go and modify Goxygen to suit your project requirements.

Clara Ekekenta
Dec 6, 2023 ⋅ 8 min read
Express Js Adoption Guide Overview Examples Alternatives

Express.js adoption guide: Overview, examples, and alternatives

Express.js is a Node.js framework for creating maintainable and fast backend web applications in JavaScript. In the fast-paced world of […]

Antonello Zanini
Dec 6, 2023 ⋅ 17 min read
Nesting web components in vanilla JavaScript

Nesting web components in vanilla JavaScript

Web components are underrated for the performance and ergonomic benefits they provide in vanilla JS. Learn how to nest them in this post.

Mark Conroy
Dec 5, 2023 ⋅ 10 min read
Meet LogRocket Galileo — Your New AI-Powered Product Analyst

Meet Galileo — your new AI-powered product analyst

LogRocket’s Galileo AI watches every user session in your app to surface the most impactful areas of user struggle and key behavior patterns.

Matt Arbesfeld
Dec 5, 2023 ⋅ 3 min read
View all posts

3 Replies to "How CSS works: Parsing & painting CSS in the critical rendering path"

  1. that 50% statistic you mentioned at the beginning of the article isn’t actually present in the article you sited… you didn’t make this up, did you?

    1. If you download the full report, you’ll find this statistic in the second sentence of the first paragraph: “Yet 53% of mobile site visitors leave a page that takes longer than three seconds to load.”

Leave a Reply