Developer forum

Hi Dmitrij,

You can find a few recommendations in the documents for installation and requirements. Is there anything in particular that you are looking for?

If you set up gzip compression (both static and dynamic) and correct caching headers then you'll get some major performance gains with little effort.

Some additional tips and tricks can be found in the web.config files for HTML5 Boilerplate and Web Developer Checklist for ASP.NET Performance.

Rebuilding fragmented indexes on the SQL Server database will also result in better performance.

The rest is more or less related to Dynamicweb configuration (cache, CDN, etc.) and the front end implementation (minify, combine, etc.).

You could setup some advanced caching or install someting like IISpeed, but for most sites this would be overkill... IMHO.

Usually, I just use PageSpeed Insights and WebPageTest in order to measure the performance of a site and then work from there trying to optimize the parts that are too slow.

You can even setup automated testing in your build process and monitoring on the server, so that you'll get warnings when something is causing problems. I don't have much experience with that though.

BR, Morten

Hi Morten,

Thanks for the input, Especially one with webconfig and web developer checlist. Is really usefull resource.

In addition to Minifying ofcourse it is worth mentioning some tools like Yslow or Net inspector tab in Firebug that is absolutely a must for measuring overall performance of the website, mostly optimising frontend.

But frontend has not that much of an influence on actual hosting IIS itself . When IIS and application is slow, frontend just adds up on that. In this case I was trying to start a discussion regarding general good dos and don'ts for IIS when hosting DW web-application by yourself.

For example we do Enable HTTP Compression in the IIS features. :)

But still great resources! :) thanks allot for sharing those, will definitely check them out :)

Cheers,

Dmitrij

Even if you enable gzip compression (never use deflate - kittens will die) you should check your network tab or pagespeed/yslow to see if all text based static files are compressed.

Often you need to register additional static file mime types, which usually requires changes in applicationHost.config. Some settings are by default not overridable in web.config, so any changes made there will have no effect unless you allow these overrides in applicationHost.config. Damn, I've wasted a lot of time looking into those issues :/

Please share any other tips and tricks that you know of - let's make the web faster :)