Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Optimizing DNN speed via JS compression, CSS Sprites, etcOptimizing DNN speed via JS compression, CSS Sprites, etc
Previous
 
Next
New Post
12/4/2009 9:19 AM
 

I  have just setup DNN 5.01.01 within the last few months.  I've got a guy helping me that is neither a Microsoft, nor a .NET guy.  He had previously setup the same site (PHP based).  He analyzed the DNN site I setup, and the results were below.  I don't think optimizing these things would really guarantee me a lot of speed improvments... since DNN is probably lagging on DLL / application side.  But I'm not enough of a DNN guru to know for sure.  Can anyone comment of these "optimizations".

 

Here is what I see from the analysis- the Home is 266,440
bytes, and has 88 HTTP Requests. Here's the breakdown:
HTML: 1 file 21,665 bytes
HTML Images: 4 files 11,270 bytes
CSS Images: 69 files 95,952 bytes
5 files 100,997 bytes
CSS: 9 files 36,556 bytes

... It would be much better if the page had only 10-20 HTTP requests,
and only 100,000 bytes. The javascript can be compressed to maybe 30
or 40,000 bytes, and maybe reduced to 2 or 3 files.

Now, 69 of those HTTP Requests are CSS Images, totaling 95952 bytes,
and most of those files are the "skin"... If there was a way to use
"CSS sprites" then you can probably reduce this to 5-10 CSS images,
and 30-40,000 bytes.

Also, I noticed some of the CSS images that are loaded are not even
used on the page. It is actually most of the bytes of the CSS images.
Eliminate these and you save 13 HTTP Requests, 66071 bytes (69% of
the bytes of the CSS images).
These 13 CSS image files are:
http://www.stpatsmemphis.org/Portals/0/dnn_large_banner.png
http://www.stpatsmemphis.org/Portals/0/dnn_proedition.png
http://www.stpatsmemphis.org/Portals/0/dnn_adminguide.png
http://www.stpatsmemphis.org/Portals/0/conferences_title.gif
http://www.stpatsmemphis.org/Portals/0/marketplace_title.gif
http://www.stpatsmemphis.org/Portals/0/feeds_title.gif
http://www.stpatsmemphis.org/Portals/0/community_title.gif
http://www.stpatsmemphis.org/Portals/0/training_title.gif
http://www.stpatsmemphis.org/Portals/0/training_icon.gif
http://www.stpatsmemphis.org/Portals/0/community_icon.gif
http://www.stpatsmemphis.org/Portals/0/marketplace_icon.gif
http://www.stpatsmemphis.org/Portals/0/conferences_icon.gif
http://www.stpatsmemphis.org/images/eip_toolbar.gif

There are also 9 CSS files. There should be some way to combine these
into a max of 3 files. Actually, the last 3 CSS files are 79, 74, 73
byes each. When I look at them, the 74 byte CSS file actually has no
useful content, while the 73 byte file just "imports" another CSS file
with the statement:
@import url("css/variations/stylesheetwidget.css");

 
New Post
12/4/2009 11:45 PM
 

Easiest way would be to buy the Snapsis PageBlaster module.  Many DNN site owners use this module.

 
New Post
12/5/2009 6:29 AM
 

AFAIK, pageblaster does not support sprites, but combines a number of css/js files and compresses it.

Regarding css files downloaded but not used, these are all the images from the default home page. please make sure, not to reuse the original modules or make sure to delte all css in source code and references in modules settings. 


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/5/2009 9:27 PM
 

If you have access to IIS 6+, you can enable IIS compression and set up the parameters for the compression to a high level compression.

Using a @import statements in css files makes the browser fetch these files faster than declaring the different css files in the html file. If you really want to improve performance, you can compress and minify all the js and css files. Create 8 subdomains and distribue the files across the subdomains. You will be utilizing the fact that a modern browser can have up to 8 simultaneous open connections to the web server. You will have to hand code these changes.

I haven't looked closely at the pages DNN produces, but I am sure it can benefit from a few performance tricks. The view state might be an area to investigate. DNN pages seem to be heavy in bytes. I think it can make use of some trimming efforts and be leaner.

 


Free DNN 5.2 hosting at FreehostingWithSitebuilder.com
Lots of extra modules and skins - Your domain name or ours
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Optimizing DNN speed via JS compression, CSS Sprites, etcOptimizing DNN speed via JS compression, CSS Sprites, etc


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out