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
ostr.io Dec 10
Replying to @HenrikJoreteg
No need to implement SSR, it's the wrong approach, waste of developer's time and money eventually. SSR doesn't stop only on implementing it, later you will need to invest into rendering servers. As it was already mentioned prerendering is going to solve it
Reply Retweet Like
Henrik Joreteg Dec 10
Replying to @ostrio_service
I'm well aware of the technique, thanks. But it doesn't always work as well for sites with huge numbers of dynamic frequently changing pages. Say, for instance, the giant ecommerce platform I'm working with currently.
Reply Retweet Like
ostr.io Mar 17
Replying to @HenrikJoreteg
Why exactly it doesn’t work? This is perfect use case for prerendering service — a website with huge number of pages
Reply Retweet Like
Henrik Joreteg Mar 17
Replying to @ostrio_service
Millions of products, rapidly changing prices and availability.
Reply Retweet Like
ostr.io Mar 17
Replying to @HenrikJoreteg
Ok, got what you mean, to solve this, we have: 1. Flexible caching period for rendered pages (changing prices every 2 hours? Ok, set it to 2 hours) 2. Different prerendering endpoints — 3. Auto-prerendering upon cache expiration And many more features...
Reply Retweet Like
Henrik Joreteg Mar 17
Replying to @ostrio_service
Not saying it's not possible, I'm saying it's the wrong solution for this problem. I feel like you're trying to fit a solution to the problem instead of the other way around. 2 hours isn't frequently enough for one of the largest retailers in the world on Black Friday.
Reply Retweet Like
ostr.io Mar 17
Replying to @HenrikJoreteg
Well, we can work around it, what is acceptable time for your case? We can lower it to a minute for example. We always work with our users to solve and fit business tasks.
Reply Retweet Like
Henrik Joreteg Mar 17
Replying to @ostrio_service
Not interested, thanks
Reply Retweet Like
Paul Kinlan 12 Sep 18
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 12 Sep 18
Replying to @Paul_Kinlan
That's a real bummer, I did not know this. 😔
Reply Retweet Like
Paul Kinlan 12 Sep 18
Replying to @HenrikJoreteg
turns out running browsers at scale is hard :)
Reply Retweet Like
Paul Kinlan 12 Sep 18
Replying to @HenrikJoreteg
You can front it with puppeteer etc if you need to.
Reply Retweet Like
Henrik Joreteg 12 Sep 18
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 12 Sep 18
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 12 Sep 18
Replying to @Paul_Kinlan
It sounds like I'm going to be watching a talk video today.
Reply Retweet Like
Ant Stanley is medium sized in Japan 🇯🇵 12 Sep 18
Netlify has a nice integration with for this... redirects crawlers to a pre-rendered version of the site.
Reply Retweet Like
Carlos Villuendas 11 Sep 18
Replying to @HenrikJoreteg
Because of the fear to lose SEO traffic ?
Reply Retweet Like
Henrik Joreteg 11 Sep 18
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 11 Sep 18
Googlebot uses an ancient version of Chrome to run pages. Do your pages render in it under 3 seconds?
Reply Retweet Like
Henrik Joreteg 11 Sep 18
Replying to @fvsch @carlosvillu
Chrome 43 last I heard, and... yes.
Reply Retweet Like
Abdón Rodríguez 12 Sep 18
It's Chrome 41. :)
Reply Retweet Like