Master the moving partsthe+moving... · 6 COMPANY CONFIDENTIAL –DO NOT DISTRIBUTE #Perform2015...

1 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #Perform2015

Best practices for synthetic monitoring SaaS data analysis

Master the moving parts:


• Why does performance matter?

• Key Issues & Best Practices - What we see in the field

• Specific examples of key issues

• How do we look at data

Agenda

3 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #Perform2015COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE3

Performance in ContextWhat matters most


• Google is not the goal

• There is a point when fast is fast enough

• Optimize only what impacts the customer and drives business outcomes

How Fast is Fast Enough?


Don’t buy a tool…enable a process that impacts your customer’s experience


Lots of data but need to knowwhat it means

Need to understand how we compare to the competition

Need to understand root causesof performance problems

Once I know what it means I need to make it actionable


Tool Data Insight Customer Impacting Action


Where Should I Focus?

CustomerExperience

ContentCreation

Internalteams

Agencies

ContentMgmt

Systems

TechnicalImplementation

Local LoadBalancing

(multi)

ISP Selectionand

Optimization

Routing(BGP)

Local LoadBalancing

DNS/network

ServerInfrastructure

Compression

Capacity

ApplicationCode

JVM

DB systems

Internal/ExternalHosting

Third PartyIntegration

WebServices

PaymentSystems

HybridContent

ContentDelivery

CloudServices

CDN

RouteOptimization

Hosting

Cloud

Shared/dedicated

Multi-dataCenter

Outsourced

Front EndAppDev

HTML

JS

AJAX

Flash/Flex

Tracking&

Analytics

A/BTesting

CampaignTracking

Omniture/Google

Analytics

ContainerTags

Floodlight/Dart


Key Issues & Best Practices


Internal Fragmentation


ResponsiveDesign


Third Party Explosion


SPA Applications


• Enabling gzip compression

• Using persistent connections

• Image size control

• Lack of JS/CSS consolidation/minification

• Poor cache control settings

The Basics


Troubleshooting Key Issues


Key Questions• What was the overall user impact?

• High/Medium/Low

• Was this my problem?

• Application Layer/Internal

• Was this a 2nd or 3rd party problem?

• Content that is required for core site functionality or peripheral?

• Is this a point in time operational issue or is it an ongoing problem?


Application issues:The slow time to first paint (7.8s) is tied to a slow and variable application callThe registrationPage.html call is generally slow and increasingly variable in performance


• You can see the impact that variability of this call would have in these extreme cases

Application Issues:


• In this example we see an extremely slow static request loading from a secondary SSL domain (unnecessarily), which is directly blocking the render of the page due to the extra SSL connection time of the new domain –unnecessarily adding ~300ms of time in the case

Slow Static Content:


• In this example we see that an extremely slow 3rd

party request to kickfactory.com is directly impacting the onload event, and as a result delaying any JS dependent on Onload and

3rd Party Issues:


• Here is an example of significant browser processing directly impacting both the initial render of the page (tied to onclicktracking, as well as dommanipulation) along with blocking the onload event at the bottom of the page

Browser Processing Issues:


How we look at data


How am I doing?


Design Drilldown


Competitive Context

Master the moving partsthe+moving... · 6 COMPANY CONFIDENTIAL –DO NOT DISTRIBUTE #Perform2015...

Documents

Transcript of Master the moving partsthe+moving... · 6 COMPANY CONFIDENTIAL –DO NOT DISTRIBUTE #Perform2015...