what do you think about my script profiler result ?

That's because all the heavy categories in the CPU module are disabled. The remaining ones then scale to fit the chart and the visual aid line there only says that, if it where just usercode and "others" it would be 10k fps. I'm guessing Rendering and the rest will take up the remaining 13.97 ms of the frame

@Joe-Censored: I wouldn't say Profiling early, especially to learn about how your code performs is a bad thing. Quite the contrary, I advocate for using the Profiler as more than just a debugging tool once everything goes south and the release date has to be moved because the performance is bad, now that all the content is in. Some things you can always keep an eye out for is GC Allocations in your main loop. Outside of your main-menu or scene loading, I'd strive to keep that as far down to 0 (if not at 0) as possible.

In that regard, this particular frame is fine but looking at the memory chart, there are quite some allocations there. You might want to look at this tutorial topic.

That said, there is such a thing as over-optimizing as well as getting bothered by the wrong stats. As discussed, your script code seems to have very little impact on your performance, at least directly. If you want to gauge how you are doing with regards to your overall performance towards a potential release, you should create a performance Budget. For that:
1. Identify the platforms you want to release on
2. Out of those, identify the lowest hardware configuration and get your hands on it.
3. Decide whether you want to aim for 60 of 30 fps
you can technically skip Step 1&2 for now but you should always test your budget on the slowest target device.
Now you have a target of either 16ms(60FPS) or 33ms(30fps) and can divide that time amongst the different systems of the engine and your game, e.g. along the lines of the profiler categories and then split underneath that to all the different parts of it that you know you want to have. Assign some eyeball values on each category or system and make sure you stay within the maximum total ms. Now you can always check that you, on average, stay within the margins you set out for yourself. If not, see if you can afford to change your budget or if you want to optimize the category in which you are falling behind.

Keep in mind, that you can't really tell what the performance of a system will be until you know what the maximum load on that system will be. You might want to create load tests with mock assets that are ugly pixel and vertex messes but on paper (in terms of texture sizes, vertices, bones, animations, shaders) roughly equal to what you want to have in the end.

With this, you can gauge your performance of subsystems even early on in development. It's a bit more complex than just looking at one frame in the profiler though and not something we can do for you based on nearly no input about the project.