These slides accompanied the SOASTA Webinar found here: "http://www.soasta.com/knowledge-center/webinars/how-real-user-monitoring-reduces-3rd-party-content-risk/"
2. T O D A Y W E W I L L C O V E R …
• The impact of third-party resources on your site
• How to measure third-parties effectively
• Defining SLAs
• Reporting on third-party performance
3. – S T E V E S O U D E R S ’ W E B P E R F O R M A N C E G O L D E N R U L E
“80% of time is spent on the front-end.”
4. W H A T Y O U S E E
• <JavaScript>, stylesheets
• Images & other media
• Display ads
• Product reviews and
recommendations
• Personalization and placement
• Social media widgets
5. Pay no attention to the man behind
the curtain!
W H A T Y O U
D O N ’ T S E E
• Web analytics & marketing
• Tracking & targeting
• User experience measurement
(CEM & RUM)
• Tag management
6. • Top 25 retail sites from Alexa
• Examined Home page for each site using
WebPagetest.org
• Focused on the number of third-party domains
3 R D P A R T Y S T U D Y
8. • Primary Domain: Within the control of the site owner
such as origin, image domains (CDN included)
• 3rd Party Domain: Hosted by a provider outside of the
control of the site owner
3 R D P A R T Y S T U D Y
9. 17
7
3
7
1
5
3 2 3 4
2 3
5
2 2 1 1
5
3 3
1
5
2 1 2
8 19
4
36
31
68
28
6
11
16
42
38
48
4
31 31 30
37
20
41
86
23
35
10
31
Domains
Alexa Ranking
Primary domains 3rd Party domains
3 R D P A R T Y S T U D Y - U N I Q U E D O M A I N S P E R
P A G E
Domains:
Median - 32
Min - 25
Max - 87
10. 3 R D P A R T Y S T U D Y
Compared to the HTTPArchive (All Sites) - average
number of domains is 17!!
12. Front-end single point of failure occurs when a
document loads, but is blocked by a resource that
fails (in this case third-party) causing the entire site
to stop loading
(simulation)
13. F R O N T - E N D S I N G L E P O I N T O F
F A I L U R E
14. 1 5 O F 2 5 L A R G E S T O N L I N E R E T A I L E R S
H A V E A F R O N T - E N D S I N G L E P O I N T O F
F A I L U R E
48%
12%
40%
Critical Non-Critical None
60% have a 3rd
party front-end
SPOF
15. T E S T I N G Y O U R S E L F F O R 3 R D P A R T Y
F R O N T - E N D S P O F
• SPOF-O-MATIC & WebPagetest
D E M O
16. O B J E C T L E V E L R U M
• Advances in browser technology make it possible to
collect performance at the object level from end users
• “Resource Timing” - supported in mainstream browsers
such as Chrome, IE, Android, Opera
17. R E S O U R C E T I M I N G
For each request, it is possible to capture timing below
http://www.w3.org/TR/resource-timing/
18. R E S O U R C E T I M I N G
• With one exception: Cross-origin requests (such as
third-party content)
• Request Start and End only by default
• Unless: Timing-Allow-Origin:* response header is
added <- Encourage your partners to add this!
19. O B J E C T L E V E L R U M
• What does this give us?
• Unprecedented visibility into
true third-party performance
experienced by real people
D E M O
20. S E T T I N G A N D E N F O R C I N G S L A S
• Understand what your current SLA is with the third party, if
it exists at all
• Negotiate for descriptive language in the SLA, which
reflects the use of RUM
• Establish a baseline from your users and work with your
provider
• Report often!
21. S L A E X A M P L E
• Response time measured using resource timing from
Chrome browsers in the United States should not
exceed a median (50th percentile) of 100ms or a 95th
percentile of 500ms for a population of more than 500
users in a 24 hour period
D E M O
22. F R E E P E R F O R M A N C E
A S S E S S M E N T
How much does 1 second of delay impact your revenue?
Give us two weeks to show you:
• What 1 second of delay means to your bottom line
• How fast your customers need you to be
• The top bottlenecks that are slowing you down
23. A T T R I B U T I O N S
https://www.flickr.com/photos/tom-margie/3087915161/in/photostream/
- Wizard of Oz
http://caniuse.com/resource-timing
Blechhhy (Own work) [GFDL (http://www.gnu.org/copyleft/fdl.html) or
CC-BY-SA-3.0 (http://creativecommons.org/licenses/by-sa/3.0)], via
Wikimedia Commons - Frustrated