Get the real story via our bi-monthly newsletter

Search

    4
    0

rss

Send to a colleague

Home > Commentary > Trends Archive > Why your CMS is slow

Browse TrendWatch Blog

Recent Blog Entries

The Complete Archive

Trends by Vendor


TrendWatch by Channel

Web Content Management Trends

Enterprise Portals Trends

ECM Trends

Web Analytics Trends

Enterprise Search Trends

SharePoint Trends

Digital & Media Asset Management Trends

XML & Component Content Management Trends

E-mail Archiving & Management Trends

Enterprise Social Software & Collaboration Trends


Report Excerpt

The Web CMS Report 2009 looks at... IBM Workplace Web Content Management

"These naming gyrations are meaningful and we think represent somem underlying turbulence as IBM has struggled to ingest the product and synchronize it with other major company initiatives around collaboration and portals. WWCM is a bit player in a very big company. "

(p. 170)

More about The Web CMS Report 2009

Our customers say

"The Web CMS Report is worth every penny!
- - Gil Côté,
President and CTO, iStudio Canada Inc.

NEW at CMS Watch

The Enterprise Social Software & Collaboration Report 2009The Enterprise Social Software & Collaboration Report 2009: This newly updated research critically evaluates 27 Enterprise Social Software and Collaboration packages... Read more

The Enterprise Portals Report 2009The Enterprise Portals Report 2009: This newly updated research critically evaluates 12 Enterprise Portals products head-to-head... Read more

The Digital & Media Asset Management Report 2009The Digital & Media Asset Management Report 2009: This newly updated research critically evaluates 20 DAM suppliers head-to-head... Read more

 
 

TrendWatch Blog

Why your CMS is slow

27-Jan-2007   --  

MindTree Consulting's Pranshu Jain offers 8 reasons why a CMS might be frustratingly sluggish for content contributors. To his excellent compendium, I'll add a few more:

  1. Voluminous client-side code in the contributor UI
  2. Delays in content publish/push to staging or preview servers
  3. Simple lack of sufficient hardware and network resources
(As an aside, I had the pleasure of meeting Jain in Denmark, and regret only catching up to his blog now; if you care about Web architectures, it's highly nutritious reading.) Via Apoorv Durga.

- Submitted by: Tony Byrne, Analyst

All CMS Channel Trends

Join the conversation

Digg This! Search Technorati Tag it on Del.icio.us




Get a Free Sample

Wondering about CMS Watch research? Sign up to receive free samples of any of our products.




What we do

CMS Watch™ evaluates content-oriented technologies, publishing head-to-head comparative reviews of leading solutions. What makes us special?

  • Our critical analysis exposes product weaknesses as well as strengths
  • We deliver unrivaled technical depth and comprehensive project advice
  • Our research is led by international topic experts
  • We only work for buyers -- never for vendors

Contact us

CMS Watch

info@cmswatch.com

3470 Olney-Laytonsville Road Suite 131

Olney, MD USA 20832

1 800 325 6190 (customer service)

+1 617 763 5336 (int'l customer service)

Fax: +1 214 242 3048