We are look'n for more speed!   How fast is your site?

When I see html sites pop on every page, I want it, I need it, NOW!

I know that if we all put our techniques together, we can make these sites move!

Our Site: websites-marketing.net

Load Time: 9.5s (Not fast Enough!)

Web Portal Framework - Dot Net Nuke

Steps Taken So Far:

1. web compression blowery.org
2. css compression flumpcakes.co.uk
3. compressed photos (Biggest issue..... Decent looking pictures kill load time!)
4. deleted blank spaces in default.aspx file
5. deleted blank spaces in skin file
6. css skin as appossed to tables
7. www.KeepAliveForever.com
8. caching set at high


What else can I do for speed? How fast does your site load?

Try mine out:

http://www.snapsis.com

I did everything you did, and one more thing that you can read about here:

http://blogs.snapsis.com/PermaLink,guid,e40942b7-06d2-4cfb-b8f3-aacb19af4323.aspx

I haven't re-enabled my blowery compression since moving to DNN 4.0, but I think it's still pretty fast.

Wow John,

That's impressive!!! So, you broke the 5 second mark! Definately the fastest I have heard of.

 

We now have a little homework to do... I'll get back to you!

 

 

Nice job John, I got your site @ 1.817 seconds on a 10Mbit line (Rockford, IL), and thaumaturge @ 2.23 seconds. So John gets the creative and speed awards. By the way, both of your server are about the same number of hops (SD & OK) from me.

www.factsonline.nl

My stuff : - Blowery - Table based design BUT no big container table. (so the site does not have to be loaded completely before rendering on client side) - Not much standard modules except HTML. - Not too much viewstate - Shared hosting but with much bandwidth

HI

Im working on a new site for big cleint and at the moment of writing i have the main page in about 2 seconds and almost every other page request in less than a second.( Some with up to 15 modules

we use viewstate http module,  compression and caching + custom caching for each custom build module and well it has its own server its own dedicated data server setup with bundles of room and memory and db space

Its not life yet unfortunately but i hope to show it off soon.

 

Sorry for the mess but I'm new at this forum and richtext didn't work..

http://www.factsonline.nl

-Blowery!

-Table based design but panes are not contained in "uber"table

-"Light" skin with not too many pictures.

-Shared hosting much bandwidth

-Heavy caching

would you mind posting the specifics on what you did at snapsis for turning up the caching and using the tabids as part of the cache key?   also how you did it for only anonymous users?

Are you changing core code? (not that I'm against that).

 

First, this is an EXCELLENT thread.  A must read for anyone who is serious about their DNN performance.

Second, for those of you who have posted what you've done so far, which step made the biggest impact on your performance? Obviously, doing them all will have the greatest impact, but if you were going to start from square one, what would you do first?

Thus far the only step I've taken is install ZipEnable in IIS...

The first and easiest thing to do is enable caching on all your modules that you can.

The next thing is optimize your website with a fast loading CSS based skin.

Use this site to see where/what you can optimize: http://www.websiteoptimization.com/services/analyze/

Enabling compression is a quick and easy next step.

And if you don't have a lot of traffic, then setup a service that will load a page on your site every 15 minutes so that the ASP.Net worker process doesn't unload your website.

I use http://www.host-tracker.com that not only calls a page on the site, but will also notify you when it is down (Free e-mail notification).

For the other question about what I did specifically.

I have my own NavMenu that is CSS driven and I made it cache an instance of the HTML that displays the menu on each tab so that it would not have to be built dynamically on each call.  So no, it is not a core change, but it is a replacement of the core navigation.

I'll get the code and post it, we might be able to cache the Solpart menu in the same way, but there is still a heavy hit for the size of the JS in such a robust DHTML menu.

 

Armand,

I have noticed you do have a viewstate module for sale on www.snowcovered.com but it says it is only for DNN 2.0 did you or will you make a version for DNN 3.x and up.

hi

No i havent made one for dnn3, the one we are using is from xepient.com

 

Really,

I have already tried this module from xepient.com. 

However, It did not fuction correctly with the blowery.org compression. 

I made a small modification to the core (one that I have been using since 2.11) to write the viewstate to the server memory. Works great with Blowery.
If there is any interest let me know, I will post it.