Questions about duplicating an existing site

[turboguy]

Yes, those are the plugins that were used to build the existing site. There are a lot of plugins that do basically the same thing and I am sure if someone has enough skills they could use fewer plugins but most wordpress sites use 6-12 plugins since it is much quicker and easier to just install a plugin to do what you want.

[Harold Mansfield]

why would one need site origin and wp bakery ? they both page builders is this the way the developers made it? I know that as good as wp bakery is is quite slow, site origin is alot faster but with less features although if you know what you are doing you can get away with most site building issues with some clever template editing. Just weird they would have a combo of these two plugins?

Yeah that is redundant, but more common than you think. Many DIY'ers and WordPress "designers" use plug ins to compensate for not knowing how to do it any other way or to save time and do the project on the cheap.

[turboguy]

I have used SiteOrigin's page builder but have never used wp bakery. They do seem like two plugins which do much the same thing and using both doesn't seem to make much sense.

[jeffscott]

Aside from professional developers you will need the help from the website analyst or SEO in which will guide the programmers for what will be the effect of their process.

[gimli]

Yes, those are the plugins that were used to build the existing site. There are a lot of plugins that do basically the same thing and I am sure if someone has enough skills they could use fewer plugins but most wordpress sites use 6-12 plugins since it is much quicker and easier to just install a plugin to do what you want.

This is why most WordPress sites are slow and the general WordPress community spend most of their time looking for speed plugins. Every plugin you use has its own javascript and css files creating mre external http request and also causing render blocking. Whilst i agree you can get away with a few plugins 12 , 10 is way too much. I understand that not every webmaster can code what all plugins do, myself included but i find it ironic that most webmaster would install another plugin to alleviate the problem of plugins. Even cache plugins cause render blocking. The only way around this is to combine you scc and js files which in my experience almost always case conflict especially js. Or use a cdn or virtual private serer that allows for keep alive connections.

[Harold Mansfield]

This is why most WordPress sites are slow and the general WordPress community spend most of their time looking for speed plugins.

I have to disagree a bit. These days old WordPress sites are slow, or those that no one is maintaining. Core WordPress is actually pretty snappy these days. It's inexperienced admins who screw it up with a bunch of junk.

...but i find it ironic that most webmaster would install another plugin to alleviate the problem of plugins. Even cache plugins cause render blocking. The only way around this is to combine you scc and js files which in my experience almost always case conflict especially js. Or use a cdn or virtual private serer that allows for keep alive connections.

Actually many consumer level hosts recommend using a cache plug in. I deal with various hosting companies throughout the month, and most of my clients have shared of VPS hosting. Just about every host I deal with recommends one cache plug in or another as having best results for working with their servers.

But overall I do agree. A lot of people use plugins to make up for not having any basic HTML or CSS skills. It's also common for me to log into dashboards and see a graveyard of plug ins running that haven't been updated in 2 years, running old frameworks, running plugins for things that WordPress now does naturally and so on.

[gimli]

Hahaha, love that "Graveyard of plugins" I've seen it a lot too, you know they should make a plugin to tell you are using plugins that do the same thing.

I've seen Yoast do that with Google XML sitemaps. It's also good if you are in that industry to stop conflicts that may make your plugin look like it's buggy and also kill the competition a bit.

The dialog is something along the lines of: We've noticed you are using google XML sitemaps this may conflict with yoast.... then options to turn off yoast or turn off Google XML sitemaps.

Maybe there's a competition-type law in place here because if I were yoast I would just say disable XML sitemaps but clearly, they offer both options for a reason.