3 ms·
There are two main benefits to server-side rendering: - time to first paint is faster on CPU-constrained devices (e.g. low-end phones), and - interoperability
by bsimpson 11y ago
There are two main benefits to server-side rendering:
- time to first paint is faster on CPU-constrained devices (e.g. low-end phones), and
- interoperability with non-JS-powered UAs (like robots)
I believe a big part of the desire for server-side rendering is a fear that search performance may be penalized if a crawler doesn't speak JavaScript, or tries to crawl the page when it's not in a state a human user would consider stable. I know there's been work done on Googlebot to make it correctly interpret client-rendered pages. If you could confidently say "Using Web Components will not have a negative affect on your search ranking; Googlebot can crawl and understand Web Components at least as well as traditional HTML elements," it would allay many of the concerns about WC, especially with regard to server-side rendering.
- Touche 11y agoEven on high-end hardware it's hard to hit 200ms first paint doing purely client rendering. Even when using a CDN. Would love to be proven wrong here.
- i386 11y agoBy the time this standard gets into major browsers todays high end phone will be tomorrows low end phone. Even most web crawlers these days execute a bit of JavaScript.