3 ms·
This is the main issue for me with webcomponents, they are not SSR friendly.
by goeiedaggoeie 3y ago
This is the main issue for me with webcomponents, they are not SSR friendly.
- kaba0 3y agoDo you want SSR for SEO, or for fast first interaction? Because if the latter, then arguably some form of webcomponents might be theoretically better optimizable by browsers than DOM-element soups.
- nicoburns 3y ago> then arguably some form of webcomponents might be theoretically better optimizable by browsers than DOM-element soups. Arguably they might be less optimisable than regular web frameworks, as they make it difficult to coordinate between different components on the page.
- goeiedaggoeie 3y agoThis is a good point, but I would counter, perceived speed of rendering from a user perspective is more important than time to interact with the app/site (a reasonable time to interact is however very important. Good load order and only loading in the content and JS above the fold initially helps a ton. JS frameworks are huge and I am still saddened that proper tree shaking and optimization got left by the way side in how the modern web has evolved. I worked with google closure in advanced modes and the closure components for a few years and the compiler was absolutely astounding (and the components designed with the compiler in mind) in code splitting, tree shaking and minimization.
- kaba0 3y agoOh, google closure was absolutely ahead of its time!
- jmull 3y agoConsider the approach this article suggests. You want to have the tags and content appear in the web component (not rendered by JS) which makes it easily and immediately available to crawlers.
- toasted-subs 3y agoYou can pre-generate them on the client though.