@elad.rosenheim thanks for the reply. My continued confusion seems to involve a number of factors:
- Lack of a clearly published supported UA list: I requested the supported UA list, which had previously been provided for the legacy prerendering extension, and you provided it, but it’s difficult to find, because for reasons that are unclear to me, my thread was unlisted by statusbot, preventing it from being found on this forum.
- The aforementioned limitations with the demo site you’ve created. It frequently does show image previews for individual breed pages, which is what I understood to be an indication of successful pre-rendering, as for us, image previews are the most important pre-rendering factor for our users.
- Most importantly, the
getBrowserwarm up continues to be long, in the order of 5-10 seconds, which seems to cause timeouts with the Facebook crawler, which seems to power previews in FB posts, Messenger.com, WhatsApp, and Instagram DMs. This timeout results in a preview without the image, despite the pre-rendering extension eventually responding with one:
Incorrect result
Correct result
In Summary
I have attempted to communicate early & often with your team, providing as much information as I’m able to, being a helpful beta tester of this tool, and still felt blindsided by this announcement of a forced migration. Without a shared understanding of expected results for various scenarios, it’s led to responses that have felt confusing & dismissive to me. I hope you will take this feedback to heart.