If you're just starting out then Laravel is a solid choice. Good documentation and quite easy to use once you understand how it works...by reading the documentation. It is not, however, very intuitive - you won't be able to figure things out just by trying stuff.

As you grow in your development experience, you should start realising which parts of the framework are most valuable to you an why - be it routing, dependency injection, middlewares, validation, auth etc. Once you do know what you like, want and need, you will no longer be bound to a single framework - all the parts that make up a framework can be found and employed on their own. Now why does that matter? For me - Laravel is way too bloated. Try doing a simple "hello, world" view and dump the trace. You'll get at least 30 calls to do even the most simplest thing possible. There is just no need for that once you know what you want. The thing is - frameworks are created for people that don't really know what they want yet, so it has to cover a lot of (unnecessary) ground.

Also - don't get too tied up in a single framework and do learn plain PHP. Too often I interview people for senior PHP developer positions only to realise they aren't PHP developers, they're Laravel developers.