WordPress Web Builders vs Codes from scratch
Few days back I was explaining someone what could be the benefits of using custom fields instead of WEB Builders but sometimes it’s hard to explain if your client doesn’t want that. But as a developer it’s your duty to make them understand what is the best for business. people can say you are an idiot or you talks a lot or focus on my sayings but you stay bold, what is right, is right. 😀
Some web builders e.g. Gutenberg is coming default with WordPress, You can disable them by using some codes in functions.php
Drawbacks of web builders
- You can’t make complex designs
- Google page speed insights will be less compare to custom codes, however you can achieve that with a deep knowledge of css
- Bad impact on SEO
- Spam injections are easy (people will say, someone hacked my website, bad keywords are coming, bad adult ads’ are coming, stay positive, no one is hacking website, it’s spam bots which is sent over the server, people will say WordPress CMS is bad, but in reality the way of implementation is bad, they way you have coded and developed a website is bad, hard but true)
- not recommended for developers, it’s built for the people who doesn’t know coding or have no budget to hire developers (budgets are always a problem in developer’s life but keep some hope, eat one burger less and deliver your client the best)
- In each update they will have some conflicts as WordPress and Web Builders Work Separately (except Gutenberg web builder which comes with WordPress Installation as a default Web builder, tested in each release)
- WordPress Elementor Vulnerability Affects +7 Million Websites (that’s why my article is here)
- Visual Composer affects unmeasured websites
- WordPress update of 5.6 made almost all cry who didn’t follow WordPress Standards
- References- https://www.searchenginejournal.com/wordpress-elementor-vulnerability-affects-7-million/399520/amp/
Note- How to make a good, stable, functional website?
- code a WordPress theme as per the client’s need, from scratch or from the given design files (from psd, xd, ai, pdf etc.)
- use a plugin only if it’s necessary and you can’t code (can’t cook that piece of cake)
- don’t use any plugin which is core and basic building block of any template (for example web builders)
- can use your own custom fields or a plugin named as acf (because it’s a support plugin)
- use contact form 7 with google recaptcha/ captcha (must, to avoid spam emails)
- can use Yoast SEO (can write your own codes for custom fields too)
- some standard and tested plugins are yoast seo (for seo purposes), acf (for creating backend), contact form 7(for creating contact forms, bounce back emails, newsletters, subscriptions etc)
- can use/ install ssl certificates
What is a plugin?
A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress.
Some plugins are having 3rd party scripts which have references of their websites, so if their website is down, yours will be down too.
For example, I am using ‘Facebook comments script’ which acts as a plugin here, in future if Facebook is down, this comment section will be down too and people won’t be able to make any comments here.
I am not saying, all the plugins are bad in results but yeah, not for developers. Happy learning. 🙂