Stored procedures are a tool just like anything else (triggers, views, etc) and should only be used where the tool fits. Taking every inline SQL statement that you have and converting it into a stored procedure is not the right direction.
Stored procedures are written using very rough logic and using cursors to loop through data sets which is going to be a hindrance when you are used to PHP's ability to handle logic.
The only project I have worked on that used SP was a large accounting system where hundreds of thousands of records had to be updated frequently with very little direct input from code. We basically just told it when to start and didn't have need to pass values to the SP (though it is possible to do so). This was, however, only one or two out of thousands of inline queries we used in the system. I am not saying this is the only place to use them, but I have built some very large systems and have not yet had the 'NEED' to use them elsewhere.
In my opinion it would be better to spend your time learning to write high-speed, low-drag queries inline and use EXPLAIN to verify that you have indexes set up correctly. I think that unless you have a VERY specific need for Stored Procedures you would find them very unfriendly for every day use.