I am not very happy with the performance of DNN in general. 

Though the architecture is highly flexible, it comes at the price of performance.  For example, the use of skin provides flexibility but loading a dynamic skin takes more time than loading a regular aspx page and the user experience is not optimized. 

Seeing this problem, I am thinking if it is possible to modify the architecture a bit to boost the performance. 

But better solution is our target! It need more search procedure to do.

Any advices? Can i possiblely modify the architecture about skin mechanism, Because I maybe always run my website on one static skin, not any more skin in future?

Ultimate Blogging Module for DotNetNuke Platform
The professional provider of DotNetNuke support, skin design and custom module development.

sure,I choose DotNetNuke as your development platfor,taking the most advantage of the localization engine and the dynamic modules etc.

But I just do not need the skinning engine that dynamicly load into page,because the price is that   the user experience is very bad and our website just now static enough!

Ultimate Blogging Module for DotNetNuke Platform
The professional provider of DotNetNuke support, skin design and custom module development.

btw: did you read the skinning whitepaper, avaliable at Resources > Documentation page on this side. You will see, that skins are ASCX controls, that are only placed dynamically on the page. If you use caching and compression, I don't expect pages will load much slower than a static aspx.