[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 255
  • Last Modified:

Speed up asp.net page loading times

Hi am I am new to asp.net and building a website, but pages are loading too slow. I have asked a few questions on how to speed things up, but want it faster. I have always used static html pages before.
It works quite fast on my pc but when uploaded there is a few seconds delay on each page.
The menu datatable is now stored in cache which is a little faster

The site is on a test server at http://advantau.w03.winhost      .com
I have put a space in to stop google picking it up
0
taz8020
Asked:
taz8020
  • 2
1 Solution
 
KBergerCommented:
Hi,

well, it all depends on what your pages actually do. But this also depends on how you actually deployed your application. Is it a web-application, or a web-site (different project-templates).
ASP.NET will compile the pages the first time they are accessed. Whenever the worker-process (w3wp.exe) gets recycled, ASP.NET will again compile the pages.
You can change that behaviour by building your application as precompiled.

However, from your posting I guess that your pages are slow in general.
Did you try a performance-profiles like JetBrains' excellent dotTrace? This will give you a clue about where the time is spent.
I had a quick look at your page.
There are many images. Are they cached on the client? Or will they be downloaded an every request? You should consider using output-caching. And you should - if possible - verify that the server sends appropriate headers concerning caching of elements (i.e. the client may cache all images for about 2 hours).
Another approach would be to minify CSS and JS files as well as GZipping your dynamic content (for instance using mbCompression-Library, just google it).

With fiddler I can see, that the images you display on the page are much bigger in reality, then on your page. This means, that you have to transfer more data then needed and then the browser has to resize them. You should consider bringing the images to the same size. When your display-size is for instance 48x48 pixels, do not load an image with 128x128 and then stuff it. This will reduce bandwidth and time-consumption.

So there is no one-fits-all answer.
Take a look at these tools : Fiddler2, dotTrace, mbCompression
Adjust the size of your images to the actual need. If this is not possible (I see that the images are located at another server), think about building reduced-size copies of these images on the application-server (although this has a bad smell).

Hope that helps you out a little,

-Kristof

0
 
taz8020Author Commented:
Hi KBerger, thanks for getting back to me. I will have a look at them now.
The images will be resized and be on the correct server when it goes live.
Just one thing though when i publish the site direct to the server in takes ages and deletes everything on there.
So as a work around I publish it to another directory on my computer and then upload just the relevant precompiled files using web copy. Do you think this is ok?
0
 
KBergerCommented:
Hi taz,

yes, I guess this is okay. However, you should make sure, that you only copy the files really needed for running the solution and maybe you should deactivate the feature of deleting before publishing. This can be found somewhere in the publish-Dialog.

You could also use YSlow to identify whether there is a performance-problem with your page from a user-perspective.

Regards,

Kristof
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now