Without knowing all of what the site uses to generate the page ( do they use java, active-x, other scripting; do they have external links which use any or all of these, do they use one of the flavors of SQL and so on) it is pointless to guess.
A simple test to see if the problem is within the recipient’s ability to do anything about is to change DNS servers your computer uses. In the event you are not familiar with DNS, it is the tool that translates the friendly names we know, such as
http://luminous-landscape.com into the underlying IP numbers that are actually used by routers the world over to find addresses and to direct the recipient to the right location. As example, the IP address for the LL web site: 70.86.208.210
DNS is the mechanism which stores and translates both the friendly name and the underlying IP address. If your browser is slow to non responsive when going to one or more web sites, try using the underlying IP address instead. How, you might ask do you get the underlying address? Simple: a tool called ping.
Without going into a long description, use ping as follows: open a command prompt. Type the following, but without the quotation marks, and then hit the Enter key: “ping luminous-landscape.com”
Ping will reply with something like the following:
ping luminous-landscape.com
Pinging luminous-landscape.com [70.86.208.210] with 32 bytes of data:
Reply from 70.86.208.210: bytes=32 time=100ms TTL=51
Reply from 70.86.208.210: bytes=32 time=96ms TTL=51
Reply from 70.86.208.210: bytes=32 time=95ms TTL=51
Reply from 70.86.208.210: bytes=32 time=96ms TTL=51
Ping statistics for 70.86.208.210:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 95ms, Maximum = 100ms, Average = 96ms
By using this ping you can get the IP address. The reply times give you an idea of how fast the response time is. The numbers above are pretty average, bigger numbers imply longer response times.
So the first test is to try the slow site but try it using it’s IP address rather than it’s friendly name. If there is a notable response time difference between using the friendly name and the IP address, they you know that DNS is likely the problem.
BUT what you don’t know yet is if the problem is due to the DNS service your computer uses, or the DNS service that the web site uses. The way to test this is to change the DNS service that your computer uses.
Again, avoiding a long description, if you were to go into the network settings for your computer you will see it wants to know the ip address of your computer, the computer’s subnet, the address of the router (called the gateway) and the DNS servers.
Most everyone uses the DNS servers provided by their ISP. You can change these by simply adding other DNS address in the area indicated above.
You can find these by looking up DNS servers on the web. It is a good idea to use DNS servers that are fairly close to you. The further away the DNS server, the longer will be the response time.
Make the change and then re-test above. To perfect the test you’ll want to do one more thing after making the change, and this is to flush or reset the DNS information cached in your computer. To do this, go back to the command prompt and type the following without the quotation marks, and then hit the Enter key: “ipconfig /flushdns”
If the response time has decreased then you know the problem is due to your DNS server. If the problem is unchanged then it is likely due to issues with your browser or due to the ISP used by the web site.
One more thing, browsers hold a lot of information in their cache. Sometimes this information is the reason for a problem. If in doubt, go to your browser’s control section (in IE it’s Tools then Internet Options), and tell it to delete browsing history and cookies.
Edit: If changing the DNS numbers creates problems, simply remove the numbers and put the original numbers there or check the box that lets the computer find these numbers automatically.
Hope this helps….
