Forum Moderators: open
I am currently rebuilding our Intranet site and am running into a speed issue. The ASP pages I am building are mostly includes, which tie webpages made in word together. Each Department Director gets various sections, and so they create the section in word, and the includes pull it all together.
My question is, how can I make the include process load faster, or at least "seem" faster to the user.
Thanks.
Are these static includes we're talking about? Or do they include ASP code?
Chip-
Is the code taking too long to process or is the HTML taking too long to download?
I spent some time last night looking into ways to clean up webpages made in word, and I think I have a few things to try using. The "real" problem I guess is the amount of code that word creates and that the server must then include.
When I say it is "slow" I mean the page takes forever to load (15 seconds for straight text). Which for my users is considered "unacceptable". The pages have no pictures just tables of links.
As far as cleaning up Word files, Dreamweaver has a tool for doing that - "Clean up Word HTML". It strips out a lot of the overblown class info that Word builds in for formatting.
Do your users do a lot of formatting (bolded words, headings, etc.)? If not, saving the files in text format would let the web page and style sheet do the formatting and eliminate the Word HTML completely.
The users at the moment use lots of fonts (aweful choices at that) but the main purpose of each of the documents they create is as a table of links to the reports that they have created.
I'm thinking of going to start them off with saving them as web page filtered, which should help some, and after that run it through Textism (http://textism.com/wordcleaner/)
the server is IIS (grr)
Don't blame IIS, you cretin. It isn't the webserver that's causing the problem. Its the fact that you are placing massive files on the server. The same problem will occur on any web server.
The quickest fix for you is to enable HTTP compression. That will roughly halve the download time for your users.
As others have said, the real cause of the problem is that you are using the wrong tool for the job.
Microsoft Word is designed for printing documents to paper. It is a very good tool for that job.
If you try and use it for something it was not designed to do (ie Web Publishing), you're going to run in to trouble.
I would consider changing the design and introduce an out of process utility that watched the folder where your users are storing documents. If the utility notices a change event then the parsing can be done at that time and the clean code could be stored elsewhere in an even smaller file that interacts with the asp files.
Then write yourself a com object to open and grap the clean code file from your asp page.
30K file is really not that big
Yes, but he's including 4-5 of these 30K files in one page.
So his users are having to download a 120K-150K document.
With a 56Kbps modem (5KB/sec) this will take 24 - 30 seconds.
Its not the server that is slowing things down, its just that he's serving massive files.
I've seen LAN based apps serving up 500-800K webpages with faster response times that webworker is indicating.
Fair point though. From the speeds he was getting> iwas assuming modem usage.
It would help if webworker could find out where the problem is occuring.
What happens when you try an access these documents on the localhost?
Are they as slow on the localhost as they are across the network?
What happens to the processor usage?
Thanks for everything guys
