More

    Six-second Page Loads: What’s Taking So Long?

    New Relic has learned a lot from looking at the Real User Monitoring data that’s been coming in fast and furious over the last month. Based on the Javascript library created by Google’s Steve Souders, RUM shows what performance issues actual users are experiencing on a site, right now. This slideshow highlights some of their initial findings.

    Six-second Page Loads: What's Taking So Long? - slide 1

    Click through for highlights from New Relic's recent look at Real User Monitoring.

    Six-second Page Loads: What's Taking So Long? - slide 2

    The average person visits 88 websites each day, senses a delay only one second after click, and spends 10 minutes each day waiting for the Web.

    Six-second Page Loads: What's Taking So Long? - slide 3

    When a customer clicks, where is that time going?

    Six-second Page Loads: What's Taking So Long? - slide 4

    Ten percent of the transaction time, an average of .6 seconds, is caused by the server. The right app monitoring tools can pinpoint and diagnose issues, such as bad coding or slow servers.

    Six-second Page Loads: What's Taking So Long? - slide 5

    Twenty-three percent of the transaction time, an average of 1.4 seconds, is caused by the network. Is it the ISP, cable operator, infrastructure provider, the code? Optimization is harder but some monitoring tools can help.

    Six-second Page Loads: What's Taking So Long? - slide 6

    Sixty-seven percent of the transaction time, an average of 4 seconds, is caused by the browser. Clean up the code, minimize the size of resources, and call a CDN provider for help.

    Get the Free Newsletter!

    Subscribe to Daily Tech Insider for top news, trends, and analysis.

    Latest Articles