Can be said, that each time start with monolith, because it easier. If you grow, you can set up required microservices, which is highly optimized for current task.

Problem with microservices, when you are starting is communication, separation and you dont clearly see, which function should that microservice really do. Because usually each service must have access to database layer, then you dont know if databases should be separated or not.

Problem with monolith is basically harder horizontal scaling, but you can, in these days, scale vertically, server configurations are pretty powerful these days. Then if your website will work, you can start thinking of microservices.

So starts small, if project grows, just try to separate services.