16
February 18, 2010 Eric Goldsmith A world of content on every web site

A World of Content on Every Web Site

Embed Size (px)

DESCRIPTION

Companion slides for a webinar on Web performance: http://streamingmedia.com/webevents/details.asp?eventid=223A World of Content on Every Web Site: Solving the Performance Challenges of Media, Entertainment, and Portal Sites For the average Internet user, a Web site is a single destination that delivers information or entertainment in various forms — video streams, photos, localized weather, feature stories. Providing a rich Web site experience today involves using content and components from 3rd parties such as ads, community forums or even blogs. In addition, Content Delivery Networks (CDNs) host images and video, improving the overall load time of Web pages. But when Web performance issues arise identifying the root cause quickly can be difficult.

Citation preview

Page 1: A World of Content on Every Web Site

February 18, 2010Eric Goldsmith

A world of content on every web site

Page 2: A World of Content on Every Web Site

Page 2

Anatomy of a Web page

Behind a Web page is a complex array of components

Many individual objects are loaded for each page

Page 3: A World of Content on Every Web Site

Page 3

Anatomy of a Web page

The key to faster pages is measuring and understanding the component objects

Source: webpagetest.org

Page 4: A World of Content on Every Web Site

Page 4

Page construction and delivery impact load time

Your pages could be slowed down by poor construction:Too many objects

Objects that are too large

Objects loading in non-optimal order

Overly complex scripts

Or poor delivery:Not using a Content Delivery Network (CDN)

Inadequate content caching

Page 5: A World of Content on Every Web Site

Page 5

Fix what you control …

These books should be on the shelf of every Web developer and performance engineer

All the ‘hows’ and ‘whys’ of Web site performance

Page 6: A World of Content on Every Web Site

Page 6

Fix what you control …

And the use of one or more of these tools should be a routine part of your development workflow:

Webpagetest – www.webpagetest.org

YSlow – developer.yahoo.com/yslow

PageSpeed – code.google.com/speed/page-speed

KITE – kite.keynote.com

Page 7: A World of Content on Every Web Site

Page 7

… manage what you don’t

How much of the content of your Web site it not within your direct control?

Advertising

Partner content

Widgets

Tracking / Analytics

Content Delivery Networks (CDNs)

Hmm, how much of my site is that stuff?

Page 8: A World of Content on Every Web Site

Page 8

How much content is from 3rd parties?

An informal look at top Web sites revealed that 40 – 90% of page content came from 3rd parties

The more 3rd party content, the more you’re relying on someone else for your site’s performance

And the more important it is to monitor performance

Page 9: A World of Content on Every Web Site

Page 9

Performance monitoring

Production Web site performance should be monitored… At regular intervals

Several times an hour

From various geographic locationsMonitor from where your users are

With sufficient granularityEnough data points to be statistically significant

Object-level monitoring to help with troubleshooting

Page 10: A World of Content on Every Web Site

Page 10

Getting a handle on 3rd party performance

What happened?

One issue or two?

My content or 3rd party?

Who owns resolution?

Page 11: A World of Content on Every Web Site

Page 11

Getting a handle on 3rd party performance

The traditional troubleshooting approach…Analysts pour over various charts & metrics

Time consuming and tedious

Something new…Object domains mapped to categories. For example:

O&O (Owned and Operated)

CDN (3rd-party Content Delivery Networks)

3rdParty (All other content, including ads, etc)

Page 12: A World of Content on Every Web Site

Page 12

Getting a handle on 3rd party performance

More actionable information:two separate issues

area of ownership clear(er)

Page 13: A World of Content on Every Web Site

Page 13

Getting a handle on 3rd party performance

Viewing performance by domain/object categoryData segregation and visualization technique to speed problem identification and resolution

Available commercially in several toolsFor example, Keynote’s Virtual Pages

Page 14: A World of Content on Every Web Site

Page 14

Tips for managing 3rd party performance

Mitigate impact to your pagesLoad 3rd party ads, widgets, modules, etc. asynchronously (i.e. not blocking page content) to minimize the impact to your page

Monitor performance with external tool(s)Independent of you or your 3rd party content providers

Give 3rd party content providers access to the data/reports

Ensure a defined support/escalation pathe.g. who to call, hours of support, etc.

Page 15: A World of Content on Every Web Site

Page 15

Tips for managing 3rd party performance

For Service Level Agreements (SLAs), be sure to define:How performance is measured

e.g. tool, test frequency, geographic location, data aggregation (mean, median, percentile), etc.

Define what constitutes a failuree.g. more than 3 failed tests in any 1 hour period from > 2 locations

Who’s responsible for the cost and staffing of monitoring

Define financial impact of failure to meet SLA

Page 16: A World of Content on Every Web Site

Page 16

Thank you

Contact [email protected]

www.ericgoldsmith.com