Home/ Questions/Q 230673
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T19:52:08+00:00

I am using WSS 3.0 in a hosted/shared (read: can make no server-side changes)

  • 0

I am using WSS 3.0 in a hosted/shared (read: can make no server-side changes) environment. Unfortunately, between SP and IIS, almost nothing is getting cached, so page loads can be terribly slow.

We have a bunch of custom image, JS, CSS, etc files that are currently just in a /img, /js, and /css directories, all of which are grabbed each and every time the page loads (server is returning “Cache-Control private,max-age=0”).

Since I can’t do anything with IIS, and can’t enable any caching server-side on SP, do I have any other options? I’ve read in a few places that if your files are located in the layouts directory that they will be cached, but using SP Designer I don’t seem to have access to the /___layouts directory, unless I’m missing something….

Thoughts?? Thank you!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Since you are running in a hosted/shared environment I would work directly with the ISP on this one. There are many ways to cache things and the ISP could very well prevent you from doing most of them.

    Ask them the following questions…

    1. Have you set output caching on the Page Layouts directory for anon and or authenticated profiles, or at the Site level or at the Site Collection level (overview on how to here)? If not, can you?
    2. Do you have IIS set to compress static files (its not caching, but, will help)?
    3. How much RAM is available to me in this shared environment?

    If you have enough RAM, look into caching your custom web parts.
    You could also host your custom images, css, javascript etc on a 3rd party CDN (Akami, Amazon Web Services), that doesn’t help with your theme and core js/css files.

    • 0