search

netlify / prerender

Automatically rendering JS-driven pages for crawlers and social sharing
MIT License
98 stars 12 forks source link

timeouts in our chrome-based prerender service but not prerender.io #9

Open fool opened 6 years ago

fool commented 6 years ago

This is a placeholder for the next time we improve the prerender service. Please do not spend any effort on it now until it is reprioritized!

We've seen some URL's that timeout (thus rendering empty on first share) when scraped by facebook via netlify's prerendering that do not similarly timeout on prerender.io. While there is no public statement I can find on this, it seems from others' experiments that taking >10s to prerender causes facebook to give up. Here's one such assertion: https://github.com/prerender/prerender/issues/319#issuecomment-228784070

Customer report can be found here:

https://netlify.slack.com/archives/C8ZATQKS8/p1521148446000095

...with a URL that exhibits the behavior. At such time as this gets priority, that customer will be happy to create another copy of that URL that we can test with that is not in production use so we can switch back and forth between prerender.io and our prerendering to debug.

biilmann commented 6 years ago

Do we know from their logs how long it takes to prerender this URL in prerender.io?

tommedema commented 4 years ago

See #31, this seems to be affecting us for all our links

github-actions[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had activity in 1 year. It will be closed in 7 days if no further activity occurs. Thanks!

tommedema commented 3 years ago

still an issue, see also #31

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had activity in 1 year. It will be closed in 7 days if no further activity occurs. Thanks!

tommedema commented 2 years ago

still an issue, see also https://github.com/netlify/prerender/issues/31