Does anyone know why the Qwik SDK’s <Content /> component bloats the page response so much?
When using it to render a simple footer (section model). The JSON from builder is only 30KB. The HTML, once rendered, is only 100KB. Yet the overall page response size is increased by well over 500KB. Combining this with the content rendered for the page itself and each page response is now well over 1MB in size for very simple content.
Please don’t ask me to provide an example, this happens for even the most basic content every time the component is used. Please just provide a full explanation as to why this happens and what the likelihood of it being resolved in the near future is.
This will enable Qwik developers to better assess whether using the drag-and-drop builder editor OR using Builder.io as a headless CMS better suits their project.
If I use Qwik API, the response is far far smaller, but then I miss out on certain features?
The builder marketing website talks a lot about “without performance trade-offs”, but this is exactly the kind of performance trade-off that the marketing content on the website hints at eliminating 
.