I couldn't begin to tell you that until you know why it is slow either. Without analyzing code and benchmarking servers and network paths, fixing it, or even telling you IF it can be fixed by you would be a bit like trying to shoot a chain link fence. You need to identify the exact bottleneck...all I can do is point out some tools to help you with that.
1. What exactally would I be looking for with ySlow?
2. If I create a file called banner.php that had the code for the website banner and included it on every single page where the banner is, and did that for quite a few other includes, would that slow it down?
1. What exactally would I be looking for with ySlow?
2. If I create a file called banner.php that had the code for the website banner and included it on every single page where the banner is, and did that for quite a few other includes, would that slow it down?
In and of itself, doing an include should have essentially no performance impact. The only way it would be a concern would be if the file being included does something itself which is in some way a performance problem.
"Please give us a simple answer, so that we don't have to think, because if we think, we might find answers that don't fit the way we want the world to be."
~ Terry Pratchett in Nation
yslow analyzes the completed page and provides suggestions for improving performance.
Go back to the start. You said Http redirects were causing slowness, how did you come to the conclusion that it was redirects? What kind of redirects are you referring to? If you are referring to what NogDog was explaining, I agree page includes should not have an impact assuming all included references are on the same server.
Reply With Quote
Originally Posted by comptech520
Bookmarks