From a performance point of view: Don't try to improve performance with such bagatelles. If you use short tags or not, if you render your output inside a PHP block or you use multiple, if you use one space more or less: It doesn't matter. You will or won't save a few ms, but it's more important to think about the drawbacks.
The real deal is to improve performance where it's profitable. That is in the most cases:
- unperformant database interaction
- unnecessary iterations
- non-existing caching concepts
- misconfigured webservers
The PHP-Community seems to go a little bit insanse on alleged performance improvements lately and ask questions like: "Can I use a space here (OMG PERFORMANCE)?" or "Is it a performance killer to instantiate many objects?" - okay the first one is a bit exaggerated, but I've seen the second one a couple of times.
In your example both scripts produce the same output and I would just for that example prefer the first one because it's simply more readable. If you're processing templates for example, where you occasionally need to substitute small snippets of PHP in large amounts of HTML, method two would be prefered.
Generally one should care about their code and it's readability and then about optimization and performance. You should never ever trade performance for readability/code quality (luckily most of the times these two go hand in hand), especially not in irrelevant cases such as shorter syntaxes.