Hi there!
I hope that someone could help me to understand a situation with prerender and HubDb.
We developed a Multilevel dynamic pages website
3 level with child tables.
We are trying to improve the perofrmance with the Prerender but it seems that after the first page, the second depth of the child tables we cannot prerender the page.
We remove every request.query_dict and other unsupported variables.
In the debugOnly we could see this after the first depth level of dynamic page (images attached)
Hi, @Gabrisan Thanks for reaching out and for including those details. Hey, @DanielSanchez@piersg@stefen, have you tackled a challenge like this in previous client work?
@Gabrisan@Jaycee_Lewis Can’t say i’ve dealt with this before. But if there isn’t any official support for this, have you considered using your own bot to load each url every so many hours?
Ciao Stefen, thanks for the answer,
To be honest, I’m a little bit confused, what did you mean with “using your own bot to load each url every so many hours”?
Unfortunately there’s no documentation about HubDb and Prerender.
For what can I see, it seems that the prerender doesn’t work with child tables. (so the second and the third depth of child).
But I cannot find any suggestion
Gabriele
@Gabrisan I’m assuming if you load the page once it should be pre-rendered. So, to automate that you could configure your own crawler to load each page in the hubdb table every so often and they would all be prerendered.
Hi Stefen
Mmm, you mean to load each sub dynamic page and then check if them are prerentered?
That’s work for the same session, second load is much quicly that the first.
But not for the first load, as if i change browser, the load time is higher.
Insted, the full rendered page (include the first level of dynamic page), is loaded quickly also if I change the browser.
You can see here. First level of dynamic page(no advice under the prerender)
@Gabrisan it’s a shot in the dark so maybe it still won’t prerender. Seems odd that HubSpot wouldn’t save the rendered file after it’s been compiled though. Have you tried reaching out to support?
Ciao Jaycee Thank you! Wish to resolve this, because almost the whole website was build it with the dynamic pages and we have problem with Core Web Vitals and TTFB!
Gabriele
I contacted the support, and pre-render is disabled for HubDB pages. Here it is:
“We have disabled pre-rendering hubdb dynamic pages because of lagging – hubdb tables with larger number of rows may cause a high volume of pages be re-rendered. We disabled pe-rendering them and disabled serving the pre-rendered content of them before we can get the lagging issue resolved.”
Hi @gsantos1
Thanks! I didn’t see you previous message
Great to know that! Hope they will fix the lagging problem soon! They say more about it?
They should also be update the documentation because it’s a very big problem.
Thanks again!
Gabri
I mentioned on ticket the lack of information on the docs regarding HubDB and prerendering. I agree, there should be an alert about that, this is hitting hard on performance for dynamic pages.
I’m waiting for a ticket update now, let’s see, I will keep you updated here on this topic.
Thanks for reaching out and for including those details. Hey, 
