If I got your issue correctly then, there is a work around of doing this, you just either need to know/find out which HTTP requests are made for displaying Graph or which requests are made after Login and displaying navigation links in Left. Once this is known, just move those requests (cut-paste) to a different Controller (you can use Simple Controller for this), and when you execute the script, listener will show you the Response time for the Graph requests (new Controller) separately.
It is easy to know which requests are made for Displaying graph if Graph section is a separate page which is being displayed after login; for example: if your application under test is like
1. Login.aspx: Login page required for login
2. Home.aspx: Homepage with Left Navigation links
3. GraphContainer.aspx: page containing graph which is displayed inside Homepage
If structure is like this then it is easy for you to separate the requests and then adding them to separate Controllers in JMeter, even without adding new controller you can tell the response time for the graph requests in this kind of application structure. If not then apply another work around, jot down the request or sequence number of request (this is a feature in JMeter 2.13 that it displays sequence number before request URL) which are send before displaying graph, once that request or sequence number is known, all major requests after that will be related to Graph feature only.
This complete work around will work positively, as I too have tried it for couple of performance tests where a same action provide multiple results or I need to separate response time like in your scenario.