aspx vs asp (website load time)

Curcial Issue with load time after implementing aspx

[bilalseo]

Hello Dear Webmasters/Developers,

Today I'm here with some different issue, other than seo. Actually my client has been converted its website from asp to aspx and when I got its testing, it seems that the load time of the pages are higher than they had with asp. Could someone explain me is that true using aspx can cause increase in load time. As maximum load time could also cause search engines to avoid visiting or to rate a site in bad words with no worth at all. So my question is that how to optimize website load time (using any script or an online resource) or any other method to reduce website load time. One more question, is aspx codes are seo friendly, in my point of they are not search enigne friendly, but I'd like to have different opinions of different webmasters.

Thanks,

Bilal

[Response]

Bilalseo,
I am currently doing an .ASP to .ASPX conversion and have noticed a slight increase in load times. Not much and really only on pages that have complex class structures in the Code Behind, not really something you would notice if you weren't looking for it. Considering you are mentioning it and other's comments I've heard from QA testers, I will ask if the site you are looking at has been compiled? If not, you will experience poor performance without compiling the site.

ASP.NET is completely SEO friendly and actually has some nice features that make doing SEO work easier.

[edited by: Response at 6:43 pm (utc) on April 14, 2008]

[bilalseo]

Thanks response for your help and adding some great information. But I'm still surprised after seening increase in load time. Actually the site is under production phases. It seems that it may live in very few next days, so I'll be contacting QA for its quality assurance and code testing as well. What about White Box testing? I only faced problem while implementing meta tags. But now they work fine. Yes the site is not compilited yet, actually we testing the site as local, not live. Hope after getting it live, it would have some nice showing out there. Thanks for you help.

Thanks,

Bilal

[Ocean10000]

Tuning Asp.Net applications come up enough that I have a special paged booked marked on MSDN named "Chapter 6 — Improving ASP.NET Performance [msdn2.microsoft.com]" for it.

I think you might find it beneficial to read to help tune the Asp.Net applications and to get the full benefit out of asp.net conversion.

[bilalseo]

Thanks Ocean 10000 :) for your help. Do you think testing a site (.net) locally can be a cuased of decrease in website load time? or it could be the same if testing it live ?

I'll be looking forward to your reply in the matter, please.

Thanks,

Bilal

[Ocean10000]

Just a quick response.

When doing active development on a site, the changes being made will require asp.net to recompile the pages in the background. This will slow asp.net down until that recompile process is finishes. Also when developing a asp.net often time debugging code is left in slowing it down also. So when moving the site to production remember to make it so its no longer including the extra debugging information in the finial results.

Also in most of the conversion projects I have seen, a good percentage of the time the code is ported over, but does not use Asp.Net features which would be beneficial to the project and the speed of the pages. Thus the end result is a slower loading page then what it truly should be.

[centime]

Asp.net for me is better in every way than asp, and the pages load even faster.

But it wasn't always so, after converting from asp to asp.net, but i found the problem

Asp.net is a totally different concept from asp, c, php and all procedural languages,

my code was full of asp programming technique which asp.net tolerated an translated, but crucially, slowed it down, plus lots of crashing :)

I had to spend weeks weeding out the code, learning asp.net better

And , voila, the site was like quicksilver compared to before plus it rarely crashes

good luck

[bilalseo]

Great! I have found everyone participated. Thanks to all, you guys are doing great job overall. It seems that talent still alive.

Thanks to all you guys,

Bilal

[Ocean10000]

Scaling Strategies for ASP.NET Applications [msdn2.microsoft.com] <-- Is a new article just posted today, which also may help shed some light on load time issues you are experiencing.

[bilalseo]

Thanks Ocean 10000 for your great anticipation in respect of my first post, you are just like a person who has guts of entertainig people with valueable information.

Thanks,

Bilal

[Ocean10000]

Found another article that you may find usefull in tunning your asp.net application on Code Project.

10 ASP.NET Performance and Scalability Secrets [codeproject.com]

[bilalseo]

Ocean 10000 you are really a good a person I ever met. God Bless you in all way you deserve for...

thanks,

Bilal

[docluv]

Pre-Compile your site before you deploy it. This will remove the need for the batch and JIT compilations. The JIT happens because you need to reload the application if it has been dormant for a while. Pre-Compilation does not completely solve this issue, but it helps. The first time a page is accessed it will be compiled by the batch compiler on the server. Pre-Compiling will eliminate this all together. You will see a dramtic increase in your site load time with this.
It is also always a good thing to test and work out a proper caching strategy for your application.