how is your website developed, i mean php or asp etc.. , cms based or own script, do you use caching, have you checked with google page speed , its show you whats wrong with with your website

it was developed in ASP using MSSQL db. It was working fine before. Only just this few days it was very slow. As I have said, If I connect to our server remotely and run there the web application it was running fast.

i dont have experience with asp,all what i can suggest is to check your server logs, monitor mssql queries

Neither do I. But I'm really curious because I don't have any problem running the web app locally. Only outside the WAN. Hoping someone could help me.

Thanks anyway Simoha.

Try testing it with one of the many page speed testing sites that exist. Look for one that gives a 'timeline waterfall' chart.

Then you can see aspects like DNS, response time for serving main page html, graphics serving response (if on cms) and embeded objects response (on external websites).

I use gtmetrix dot com but there are many other good ones. There is also a page speed module for the Firefox addon called Firebug. Well worth the download!

It has been there for four years and just last two weeks we suffered with the slowness of it.

What happens when you put up an ordinary, static page that's almost empty? Don't use an .asp page, use a regular .html file.

If it loads slow for that, it's not likely the database or ASP that's causing it. If it's fast, then you can engage the hosting company in a dialogue, something is wrong at the server.

If it's still slow with a static file, make 100% sure it's not something on your end. I was on a satellite connection once and rose to 1995 browsing speeds. I was freaking out - but it turns out my stepdaughter had spent all night watching movies and our connection was throttled back. :-) There are many [points between your keyboard and the server where things can go wrong.

Insure it's not "you." Scan for spyware, malware, download and use a different browser than you usually do, run internet connection speed tests, you know the drill.

Check with people who are geographically separate from you, on different bandwidth. Do they have the same problems?

I had a similar problem but noticed it was a DOS attack that made my site slow.

rocknbil: I've tried this one. We have 11 branches using this web application and they were all suffering.

dailypress: What do you mean by DOS attack? Did you solve your problem?

- check your server for server load. On linux I would use 'top', but on windows there must be something similiar that will tell you how much CPU is being used.

- try pinging your website just to see the travel time.

- try a traceroute. This will show you all the stops along the way to your server. If the slowdown is a point between you and the server (i.e. your web hosting company's router or something) this should show it.

If the ping and the traceroute show problems, it's probably the hosting company. If your CPU is high load, then it's probably your server, so start checking processes that are running.

Is this a standalone server or is it hosted off site?

Could this be an aspect of DNS poisoning?

Has your permanent ips been placed in some blacklist?

Is the cable plugged in? (Well, sometimes you have to start with Step One!)

Is the cable plugged in? (Well, sometimes you have to start with Step One!)

Another variant of this is the network card. Was it assumed to be 1 Ggb full-duplex but in checking the port on the switch it shows 10 Mhz Half-duplex. I'm assuming the server has two network cards - the one for outside could have this issue.

On some version of Windows Control Panel Applets they show the card set to something different than what the switch port reports.

dailypress: What do you mean by DOS attack? Did you solve your problem?

[webmasterworld.com...]

You may also want to see the following tools to analyze website speed:
Post ~ #25
GTMetrix
[webmasterworld.com...]

Sounds like a network bandwidth issue not a server issue.

Thanks for the response guys. Now it's working fine. Its only the internet connection from the ISP. Thanks again..

Thanks for sharing the resolution... helps others visiting this thread to know the answer!

welcome to WebmasterWorld, borgyborg!

as wheel suggested, a traceroute would have exposed which hop was causing the problem for you.