The first thing to do is to realize that that code is never going to work.
giriRicevuti is a string parameter to your method, so the world outside cannot in any way change the value once the method is called (strings are immutable, so even a change to the outside world string will just produce a new reference and the string in the method will be unaffected).
So your test will only ever time the performance of the line:
if (giriRicevuti == "1/r")
Which has nothing at all to do with the speed at which data is received from your uProcessor.
There are a large number of problems here which you need to look at. Some of the most major are:
1) Data receive is not necessarily synchronous with the data transmitted by the uProcessor: Windows is not a real time system, and your task may not execute at any given time: if it "misses" a slot, it could conceivably not run for several seconds or even minutes.
2) All data received by the system is buffered, both in hardware and software so that data is not lost - this is great for normal applications, but will bugger your timing right up as you will never know when a bytes was received - the various buffers and windows messages may take significant time to be processed by your application.
The way I would do it is this:
Have a timer event which fires at an expected multiple of the rotation speed. So if you moter or rotating at around 100Hz, then I would set the time to 10HX, or possible less - 5Hz or even 1Hz, depending on how accurate you want to be.
Create two class level variables: and integer count, and a DateTime
Handle the serial port DataRecieved Event, and each time you receive a '1' followed by a '\r' (and remember that these may come is separate events, so you can't just check the data present this time) increment the count by one.
In the timer event, read the count, and zero it. Get the current time, calculate the timespan since the previous one, then save the current value for next time - DO NOT USE DateTime.Now more than once, or you will introduce a small (but significant) error.
You can now use the timespan and the count to work out the average rotation speed between timer events.