In this article, we are going to discuss Steps to follow the Codeigniter website optimizer. We are Web development, Software development, and Mobile application development company for many organizations that have created CMS, eCommerce, and Online Portal website development from us. We favor CodeIgniter, Wordpress, Opencart as it's fast and cost-effective. We are writing this case study to show you what steps were taken to improve website speed. These tips can be used for other platform Websites as well.
Check the Performance of the website using Google page speed or gtmetrix. you can find the website was languishing at the score.
Check the Performance of the website using Google page speed or gtmetrix. you can find the website with a good score.
What information you will need:
In order to optimize the speed of a website, you will need to have access to the FTP, Cpanel credentials of the website.
Website speed testing tools
1. Google Pagespeed Insights
2. Pingdom website speed test
Images need to be properly scaled and should reduce image size without affecting quality. it should not be resized using CSS.
Using Database cache we can tell the browser to use the previously downloaded content instead of downloading the contents from the server again and again. Also, you add following code in htacess
CSS & JS concatenation and minification
Combine and minify your CSS and JS contents. The benefit of combining contents is that the browser will make one request to the server instead of many. Also, you can add following code in htaccess
Content compression is an easy way to save bandwidth and speed up the Codeigniter website. Enable Gzip compression in Cpanel or In CodeIgniter, you can do it by simply setting the “compress_output” variable to true in config.php file.
$config['compress_output'] = TRUE;
You can also add following code in htaccess
There are 3 ways to compress content. Can follow any one simplest way
Database queries optimization
Database cache can be enabled by The sample syntax is given below. Simple turn db->cache_on before a query and turn db->cache_off after the query returns results.