![]() |
|
#1
|
|||
|
|||
|
Is there a way to test html-pages at different speeds?
When I test them they're really fast, but I want to see what happens if one has 56k. |
|
#2
|
|||
|
|||
|
If you have Macromedia Dreamweaver, you could check the approximate time taken to open your page at different speeds.
|
|
#3
|
|||
|
|||
|
Yeah, but I prefer to see it. I've got large photo's in the background.
I first display a pattern and after a delay you see the photo. So first one thing shows and then the other. I want to check what's acceptable (in my opinion that is). |
|
#4
|
|||
|
|||
|
Try squeezing your cat-5 cable really hard, maybe you can slow down your connection that way.
|
|
#5
|
|||
|
|||
|
[url="http://www.websiteoptimization.com/services/analyze/"]Web Page Analyzer website speed test and analysis for faster downloads[/url:499o7nsfm3]
- [url="http://neo.dzygn.com/"]Mark[/url:499o7nsfm3] |
|
#6
|
|||
|
|||
|
<blockquote id="quote"><span class="smalltext" id="quote">quote:<hr id="quote">Try squeezing your cat-5 cable really hard, maybe you can slow down your connection that way.<hr id="quote"></blockquote id="quote"></span id="quote">
Haha! That's a classic! -- Regards, Tim Scarfe <tim@developer-x.com> http://www.developer-x.com |
|
#7
|
|||
|
|||
|
wimmasker, if you're not afraid of a little Unix system-level funging, there are a bunch of tools you can use to "rate limit" a connection to and/or from a box. On FreeBSD there is a package that works with IPF (dummynet) to do network analysis and rate limiting. On Linux, newer kernels support traffic flow and control via the iproute2 tools. My good friend Martin Brown has written one of the better tutorials on the topic:
http://linux-ip.net/articles/Traffic-Control-HOWTO/ How you would do something even remotely similar on Windows is well beyond me, but I wouldn't trust anything that isn't doing real emulation of a link (not just sending you packets at a slower rate), since the effects on TCP of fast backoff like that wouldn't match what happens in the "Real World" at all, and estimates based on file size are similarly bogus. OTOH, it might be cheaper/better to just get a modem and a throw-away dialup account (got one of those AOL toasters handy?). Regards. -- Alex Russell http://netWindows.org http://alex.netWindows.org |
|
#8
|
|||
|
|||
|
I think this is built into Windows infrastructure under the guise of QOS AKA "Quality Of Service". It's interface point is at an NT ACE/SID level though so useful but only if you have the infrastructure in place. It exposes a priority mapping system you can't just state actual figures.
Correct me if I'm wrong, my only experience of it is through ISA Server. You can probably find HTTP proxies that expose this functionality anyway. -- Regards, Tim Scarfe <tim@developer-x.com> http://www.developer-x.com |
|
#9
|
|||
|
|||
|
why not just look at the file size of the document? There shouldn't be many other variables in load time other than that (other than scripting, which is unpredictable as its done on the client end)
-Rob http://www.abstractia.com |
|
#10
|
|||
|
|||
|
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|