If you can, you should avoid using ‘//’ in xpaths anywhere.
In many cases this is just laziness which results in a significant performance hit.
when you use ‘//’ the xsl engine has to scan the entire document to find ‘Page’ elmenets; if you know where they exist in the document you should specify that explicitly.
Thanks for the comment re. the double-slash. I’ve never used inline-xslt in anger before, I’ve always gone to straight custom XSLT files where I can do (for example):
/ns0:Root/ns0:child/ns0:value
However, when I put together a test project for this post, I discovered that that wasn’t accepted. A blog post I found suggested that the double slashes was the answer. I’ll bear the performance issue in mind in the future.