when working in a page builder is it better for performance to use a widget that has a bunch of elements or to add each element individually?
when working in a page builder is it better for performance to use a widget that has a bunch of elements or to add each element individually?
[ad_1]
For example, if you need an image, title and description is it better to add an image box that includes an image, title and description or is it better to add each element separately?
Chances are the image box is already setup so all the elements are responsive, which can save you time. Sure there’s a little more code, but I really don’t think there would be a noticeable impact on performance if you did it differently.
Never use an image that has text ‘in’ the image – it’s worthless from an SEO point of view, and often won’t work in responsive design, and limits your design options (eg if you decide to use a different font, you have to regenerate all your images).
It’s going to depend on a number of things but *in general* you can assume that a widget will have been at least a little bit optimized and may be completely fine tuned.
As u/evanvolmn says, at the very least a widget is more likely to be well-tuned for responsive display — not just for the three canonical sizes but for when someone grabs a corner of the browser window and “plays the accordion.”
That said! For some builders some of the widgets could be pretty old and out of best-practice. That said, the incremental performance hit of a single widget is still probably going to be low vs a hand-tuned composite.
Though also note that at least for some of the newer builders there are now flex and grid modules that let you really roll your own… if you’ve mastered flex and grid, of course, *and* as long as you don’t use a 4mb image in a 400px space.
That last bit is also important: it really depends on who’s going to be working on the site once you’re done. You can composite a cool Staff box with multiple, layered flex, for instance. But if the company’s office manager is going to be tasked with keeping the staff page up to date the builder’s widget is going to have a distinct, self-contained, and clearly labeled UI, and they’ll *almost certainly* be easier to duplicate, delete, and drag them around as new staff is added.
Better off to build it manually, because the pre-built stuff won’t always have the best code compared to something made from scratch.
Chances are the image box is already setup so all the elements are responsive, which can save you time. Sure there’s a little more code, but I really don’t think there would be a noticeable impact on performance if you did it differently.
Never use an image that has text ‘in’ the image – it’s worthless from an SEO point of view, and often won’t work in responsive design, and limits your design options (eg if you decide to use a different font, you have to regenerate all your images).
It’s going to depend on a number of things but *in general* you can assume that a widget will have been at least a little bit optimized and may be completely fine tuned.
As u/evanvolmn says, at the very least a widget is more likely to be well-tuned for responsive display — not just for the three canonical sizes but for when someone grabs a corner of the browser window and “plays the accordion.”
That said! For some builders some of the widgets could be pretty old and out of best-practice. That said, the incremental performance hit of a single widget is still probably going to be low vs a hand-tuned composite.
Though also note that at least for some of the newer builders there are now flex and grid modules that let you really roll your own… if you’ve mastered flex and grid, of course, *and* as long as you don’t use a 4mb image in a 400px space.
That last bit is also important: it really depends on who’s going to be working on the site once you’re done. You can composite a cool Staff box with multiple, layered flex, for instance. But if the company’s office manager is going to be tasked with keeping the staff page up to date the builder’s widget is going to have a distinct, self-contained, and clearly labeled UI, and they’ll *almost certainly* be easier to duplicate, delete, and drag them around as new staff is added.
Better off to build it manually, because the pre-built stuff won’t always have the best code compared to something made from scratch.