Route caching is an excellent feature, especially for apps with a large number of configurations and routes spread across the code. It\u2019s a group of routes packed in a single command to help reduce the tedious task of charting your routes manually. As a result, your website\u2019s pages will load a lot faster.<\/p>\n
Route caching allows Laravel to retrieve routes periodically from the pre-compiled cache rather than having to start from the ground up for each new user.<\/p>\n
Use this command to cache the routing data required:<\/p>\n
<\/p>\n
php artisan route:cache<\/code><\/pre>\n <\/p>\n
Keep in mind that the cache expires when the user leaves your site. It\u2019s also important to run that route cache command every time after making structural changes (e.g. routes files and config) to your website, as any modifications made afterward won\u2019t take effect.<\/p>\n
If you want to clear the route cache, run the following command:<\/p>\n
php artisan route:clear<\/code><\/pre>\n2. Optimize Composer<\/h3>\n
Laravel uses a separate tool called Composer to manage different dependencies. When you initially\u00a0install Composer, it loads dev dependencies into your system by default.<\/p>\n
These dependencies are useful for developing a website. But once your site is fully operational, they\u2019re no longer required, and in fact, they\u2019ll only slow it down.<\/p>\n
When utilizing Composer to install packages, use the\u00a0--no-dev<\/code>\u00a0and\u00a0-o<\/code>\u00a0parameters as follows to remove dev dependencies:<\/p>\ncomposer<\/span> install<\/span> --prefer-dist --no-dev -o<\/span><\/code><\/pre>\nThis command allows Composer to create a directory for optimizing the autoloader and boosting performance. It simply requests the official distribution to be retrieved and packaged, with no dev dependencies.<\/p>\n
Be careful not to eliminate any runtime dependencies. This could jeopardize your website\u2019s performance or even cause it to crash.<\/p>\n
3. Reduce Autoloaded Services<\/h3>\n
The goal of Laravel is to make the development process as breezy for devs as possible. When you launch Laravel, for example, it auto-loads a large volume of service providers listed in the\u00a0config\/app.php<\/strong>\u00a0file to help you get started with your project quickly.<\/p>\nWhile this is a beneficial step by Laravel, you won\u2019t need to use all of these services for building an application.<\/p>\n
Take the REST API for instance. You don\u2019t require services such as View Service Provider or Session Service Provider. In addition, many developers don\u2019t follow the default framework settings. You can simply disable services that are superfluous to your needs (e.g. Pagination Service Provider, Translation Service Provider, Auth Service Provider, etc).<\/p>\n
You\u2019ll be able to improve the speed of your Laravel applications by applying the same principle to other apps. Just make sure you don\u2019t remove any important services, and double-check everything before you drop the hammer.<\/p>\n
4. Use Artisan Commands and Cache Effectively<\/h3>\n
Artisan is a popular command-line tool that comes with Laravel. It makes it easy for developers to carry out recurring and complex tasks automatically. Website creators can also use it to conduct tests and generate commands.<\/p>\n
Using Artisan commands cleverly can amp up your app performance. Below, we\u2019ve listed several of the best caching commands you can utilize.<\/p>\n
Configuration Caching<\/h4>\n
Cache config is an excellent command to get a speed boost. It compiles all of your application\u2019s configuration values into one file so that the framework can load faster. All you need is to run:<\/p>\n
php artisan config:cache<\/code><\/pre>\nNote that you shouldn\u2019t execute the\u00a0config cache<\/strong>\u00a0command during local development. This is because configuration settings may need to be changed often throughout the development of your app.<\/p>\nTo clear the config cache, run this command:<\/p>\n
php artisan config:clear<\/code><\/pre>\nViews Caching<\/h4>\n
The view cache is another aspect of the application that contains a cache. The view cache stores generated Blade templates to increase the speed of your project. You can use the artisan command below to compile all views manually and optimize performance:<\/p>\n
php artisan view:cache<\/code><\/pre>\nRemember to clear the cache when you upload a new code; otherwise, Laravel will use your old views and you will spend lots of time trying to troubleshoot this. Run this command to clear the view cache:<\/p>\n
php artisan view:clear<\/code><\/pre>\nApplication Caching<\/h4>\n
This is the main cache in Laravel. It saves all the data that you cache manually in your app. Using Laravel\u2019s cache is a smart approach to speed up commonly accessed data and optimize Laravel performance. If you use tags or multiple cache storage, you can flush only certain elements of the cache.<\/p>\n
Here\u2019s the artisan command to clear the Laravel cache:<\/p>\n
php artisan cache:clear<\/code><\/pre>\nKeep in mind that this command won\u2019t delete any route, config, or view cache located in the \/bootstrap\/cache\/ folder.<\/p>\n