Twitter | Search | |
Henrik Joreteg
- Sub 100kb main bundle - 90+ lighthouse perf score - Data-driven sitemap.xml with relevant crawlable URLs. - PWA deployed as static site (ridiculously scalable) Explain to me again why we should SSR and run a huge farm of node servers that renderToString?
Reply Retweet Like More
Carlos Villuendas Sep 11
Replying to @HenrikJoreteg
Because of the fear to lose SEO traffic ?
Reply Retweet Like
Henrik Joreteg Sep 11
Replying to @carlosvillu
Yeah, probably so, but I want the data to back this up. How far will a thorough sitemap and clientside rendering get you?
Reply Retweet Like
Florens Verschelde Sep 11
Googlebot uses an ancient version of Chrome to run pages. Do your pages render in it under 3 seconds?
Reply Retweet Like
Henrik Joreteg Sep 11
Replying to @fvsch @carlosvillu
Chrome 43 last I heard, and... yes.
Reply Retweet Like
Feross 🧙🏼‍♂️✨ Sep 11
Replying to @HenrikJoreteg
What is a data-driven sitemap.xml? Like only including popular pages vs. including everything? Or is there something else?
Reply Retweet Like
Tom Dale Sep 12
Reply Retweet Like
Paul Kinlan Sep 12
Replying to @HenrikJoreteg
Indexing is delayed for pure client side sides. Google indexer is two-pass, first run is without js, then week later it's with is (or there abouts)
Reply Retweet Like
Henrik Joreteg Sep 12
Replying to @feross
Say any dynamic data added by users or external systems during the course of using the app that you want indexed. Rather than generating HTML, updating a site map using the DB to let crawlers know where content will be available.
Reply Retweet Like
Henrik Joreteg Sep 12
Replying to @Paul_Kinlan
That's a real bummer, I did not know this. 😔
Reply Retweet Like
Paul Kinlan Sep 12
Replying to @HenrikJoreteg
You can front it with puppeteer etc if you need to.
Reply Retweet Like
Henrik Joreteg Sep 12
Replying to @Paul_Kinlan
Yeah, it's true. But doesn't that add a lot of server overhead? (For the project I have mind we'll probably end up doing SSR with Preact.) It would just be so nice if that wasn't necessary. Especially when it's so fast anyway.
Reply Retweet Like
Paul Kinlan Sep 12
Replying to @HenrikJoreteg
You would only front for the Google Bot (or other JS-less renderers) at that point. The IO talk this year called it 'Dynamic Rendering'.
Reply Retweet Like
Henrik Joreteg Sep 12
Replying to @Paul_Kinlan
It sounds like I'm going to be watching a talk video today.
Reply Retweet Like
Henrik Joreteg Sep 12
Replying to @tomdale @BrendanEich
This is great. Thanks for sharing.
Reply Retweet Like
Paul Kinlan Sep 12
Rendertron - but it's not fully endorsed (caveat emptor)
Reply Retweet Like
Ant Stanley Sep 12
Netlify has a nice integration with for this... redirects crawlers to a pre-rendered version of the site.
Reply Retweet Like
Henrik Joreteg Sep 12
You sure it only does this for crawlers? I thought it was all traffic. cc:
Reply Retweet Like
Ant Stanley Sep 12
Here's the feature... ... does filter on crawlers to deliver prerendered version of a SPA
Reply Retweet Like
Henrik Joreteg Sep 12
Hmm, it certainly seems that way... that actually makes it much cooler, IMO. I thought it was all or nothing and the cache length was a little concerning for really dynamic content, but I can live with that for crawlers.
Reply Retweet Like