4 ms·
Co-author of the blog post here. My mistake is to call it FCP. This local benchmark only shows the performance of: - parsing the javascript code - creating the
by georges_gomes 6y ago
Co-author of the blog post here.
My mistake is to call it FCP.
This local benchmark only shows the performance of:
- parsing the javascript code
- creating the DOM node
That was the only goal.
We should have network simulation for the next update of the blog post to show some additional color. Good idea :thumbsup:
Static + re-hydrating is actually built in Web Components (technically). "Only" tooling like Gatsby or Next.js is missing to make it more developer friendly.
- mshenfield 6y agoThanks for clarifying! That's a fair point about web components having the capacity to be statically rendered and re-hydrated.
- hoten 6y agoWould you consider comparing the results of a Lighthouse report?
- georges_gomes 6y agoSounds good. Like have some sort of generic page with components and look for lighthouse score. I'm adding to the list!
- hoten 6y agoSweet, thanks! Feel free to DM me if you need any help. twitter is in bio.