Speed of Web Pages and Embedded Views

Am I crazy or does using embedded views slow down the loading of a web page?

Some background: I have been experimenting on web pages using views for naviagtion links, short list of look up information, like an index of articles, for a listing of major pages for a site map, etc. All of these views have 50 or less documents in them. So I am not using an embedded view of a lot of docs.

Also the views are not complicated, nor have long formulas, etc. They usually present one or two fields from a doc, and they usually have a formula that creates the html code for a link. Nothing more.

It seems that once I started using embedded views, my web pages slowed down tremendously. Is this true?

An associated question might then be, to get around the limit of one embedded view per page, I have heard I can use iframes. IS this a good technique for multiple embedded views, and would several iframes refering to views slow things down?

Again I am not talking about long lists of docs nor comlicated views.

I am trying to find a way to handle lists of data, like web pages on a site for a site map, links like in the left margin of this page, or a list of categories of books available on a site. Since I want to put one or of these lists onto pages that may already need to have an embedded view, I am worried about the speed of loading.

Thanks for any help.

Al

Subject: Speed of Web Pages and Embedded Views

I’ve not seen this to be a problem, but really have not tested the performance. As far as an alternative, why not just put the html for the links into a single column in the view and do an @DBColumn or @DBLookup into a computed text field? I have some web forms with lots of these to pull in child doc info and performance seems fine.

Jerry T

Subject: RE: Speed of Web Pages and Embedded Views

Thanks for the response.

It sounds as if your method would solve a lot of my problems.

I’ll try it and test the speed.

Thanks again.

Al