|
Posted by tatata9999 on October 20, 2007, 10:38 pm
Please log in for more thread options > Gazing into my crystal ball I observed tatata9...@gmail.com writing
>
>
>
>
>
> > The first generation of web site search engine hands-down is google.
> > A majority of these web
> > sites are static page -driven html pages.
>
> > Now, I would think more and more web-based applications are coming
> > into the fray, my recent
> > experience with google's webbot (indexing engine, a part of the
> > google's search service) tells
> > me that its indexing algorithm does not consider a database-driven web
> > application as part of
> > a qualified 'web site'. Minicking it as a html site is like a man
> > trying to dress in skirt,
> > oh, my poor Scotsman... Hence, I believe a service that would evaluate
> > and index web apps
> > (database-driven, xml-based or what not) vs. the plain HTML -driven
> > web sites would be
> > valuable to both consumers and businesses. Or maybe there's already
> > such a service out there?
>
> Google does database driven sites very well. I manage two sites that
> are completely database driven. Google for mass confession and Holy
> Family Catholic Community is 6th, and Google for Glendale Tires and
> Glendale Tire Company is 5th at nextBlock.com . Not too shabby I would
> say.
>
> There are a few tricks to getting good SERPs in database driven sites:
> A. Fast pages, so fast queries to the server
> 1. Open and close record sets right away. Try not to loop through an
> open record set if possible.
> 2. Put CSS in an external stylesheet.
> 3. Put javascript in an external script.
> 4. Optimize images
> 5. Don't depend on the browser to resize images.
> B. Mark up documents well - use semantic markup.
> C. Validate markup generated by your script. Valid markup seems to do a
> lot better than tag soup.
>
> --
> Adrienne Boswell at Home
> Arbpen Web Site Design Serviceshttp://www.cavalcade-of-coding.info
> Please respond to the group so others can share- Hide quoted text -
>
> - Show quoted text -
Thanks, Adrienne. That's good to know.
My web app is fast, on average, it takes about 240 milliseconds to
serve a page request which may involve multiple queries. Yes, I read
about using include file for js, so, I just did. As for CSS, I've
even eliminated them for now for speed sake. As for images, I have
only a few tiny ones. One thing I want to do away is a bit too many
tables. Please take a look at my app to see what I mean, http://www.mytata.net
when you have a chance. So, in sum, the speed of the app is a major
design consideration.
Don
| 
XML Sitemap