Web-HTTP/HTML protocol
Since this protocol sees and records all request separately…I have consultants who are saying the following below since this content is being cached for us by Akamai…my feeling is this is still part of the end users experience regardless of where it comes from and should be part of the transaction measurement.

Is it right to exclude these Non HTML resource requests? To me it is just a way to make sure the page loads fast for them while performance testing.

"Only those requests which are critical to the action have been included inside the transaction.
Requests which are related to the NON HTML resources getting downloaded like jsp/css and redirection are not included in transactions."