When started using WordPress for many of my projects, I heard so many things about it, which most of them are not correct at all. They are just Myths people say about WordPress.
- Slow Database
Database downtime due to failures == poor database administration. WordPress only connects to the database, and adds / edits entries in the database tables. Nothing more. If you have a failure, it’s due to 1 of 3 things:
- Poor custom code
- Poor database administration
- Poor database configuration
Hack attempts happen against almost ALL popular CMS’s. If you are actually being breached, the core WordPress isn’t at fault, one of these are more likely:
- Unsecured ports to services such as database, ssh, etc..etc..etc..
- Easily guessed / brute forced passwords
- Poor custom code that doesn’t sanitize / strip js, html, php, etc from comments or posts
- Poor custom code that doesn’t check extension against content.. i.e. uploading blah.php.jpg and it being executed as php when directly called
- oor file attributes / permissions (chmod 777 to all files is derpy)
- poorly secured environment, e.g. not forbidding su_exec, exec from php, etc..
- Website/Blog loading is slow
If your WordPress is slow, try removing un-used plugins, scripts, and includes. I have seen way too many sites that load everything on all pages, when the js file is only used one 1 page. This is silly, and will lead to overhead.
- Learn to utilize gzip compression, and caching of non-dynamic content. This will re-leave some of the loading overhead
- Load your js includes at the BOTTOM of the page, not the top, that way the initial page loads faster, i.e. images, text, content etc.
- Optimize your database table, memory, and indexes.
- Optimize your Apache by removing unused modules, and tuning memory, workers and threads.
- Absolute URLs..
The only time absolute URLs are used is with poorly coded themes, and images that have been uploaded. The only time you would experience any issue with this, is when you change the domain name, a simply 1 line SQL statement can fix this ” select *.* from * and update “WWW.domain2.com” where “WWW.domain1.com” ” or something similar. Other than that, all other links within the WordPress environment are populated from database settings.