Yes, but...
As Martin Ender (among others) has pointed out, there is oftentimes volumes of literature already written about such topics. It's simply not possible to fit all (or even a useful subset) of that information into a single usable post.
Therefore, a question such as "Tips for time-optimization in Python/C/Java/Rust/etc." would (and IMHO should) be closed as "too broad."
There are a few things that could be done to narrow the scope of such a question:
You could make it into a question about a specific piece of code (in the same way that these sorts of golfing tips questions are on-topic), but this might be better suited to Code Review.
You could make it into a question about a specific language feature, or at least a feature which has optimization characteristics specific to the given language (e.g. "When to use static vs. dynamic dispatch to get best preformance in Rust"). This might be better suited to Stack Overflow, but it would probably be on-topic and useful here as well.
It might be possible to make a question that was language-agnostic (or at least generalized to a certain category of languages), but even this would need some specialization.
If a person wanted to ask a question like that in PPCG, it was probably because they were trying to solve a challenge on PPCG, and had a specific problem that they wanted to solve. The best thing to do is to identify this problem and ask about it specifically, rather than asking an unhelpful and overly broad question that probably won't even provide an answer useful to the OP.