VisuallyComplete, RUMFirstPaint, StartRender and SpeedIndex for mobile tests

Support
1

Hello everyone,

On my private instance, I get some values by calling jsonResult.php.
“Visually Complete”

[quote]jsonResult->data->median->firstView->visualComplete
jsonResult->data->median->repeatView->visualComplete[/quote]
“RUM First Paint”

[quote]jsonResult->data->median->firstView->firstPaint
jsonResult->data->median->repeatView->firstPaint[/quote]
“Start Render”

[quote]jsonResult->data->median->firstView->render
jsonResult->data->median->repeatView->render[/quote]
“Speed Index”

[quote]jsonResult->data->median->firstView->SpeedIndex
jsonResult->data->median->repeatView->SpeedIndex
[/quote]
It seems webpagetest

  1. always provides these 4 values as 0 for apple devices tests
  2. sometimes provides some of these 4 values as 0 for android devices test

I’m not sure what’s the reason…
If it’s a bug, is it possible to provide both these 4 values for mobile devices? Or, what is the reason I got 0 as results?

On the attachment, I made screenshots of android tests results and iphone tests results. some columns(ex:RUM First Paint) are not shown when the value is 0.

Thanks,
[attachment=528]

2

Do you have links to the actual test results? There are 2 iPhone agents. The old (soon to be decomissioned) Blaze agent running iOS 5 and the new agent that shares the same code as the android agent (the iPhone 5c running iOS 9).

iOS doesn’t support the RUM first paint metric - though it’s probably a bug that it reports 0 instead of -1

Speed Index, Visually Complete and Start render will only exist if video capture is enabled (and may not be reported with the old iOS agent). Also probably a bug if they report 0 instead of -1 when they are missing.

3

Sorry, I see it’s a private instance - most of the comments still apply, just not the request for a link or the specifics about the iOS agent.

I’d highly recommend moving iOS to the new node agent in git. It’s still a little rough and being worked on but it’s orders of magnitude better than the blaze agent.

4

Thanks for your reminding on video capture, but the reason seems not that.
I check there is “video=1” in my url request

I want to metion that I had put “–processvideo yes” in my command, hope it’s not the reason.

I think the agent I’m running is the new agent code that you recommended:

Is my setting correct?

And another issue I also want to ask (I guess it has some relations with the video capture):
sometimes, the screen shots of ios devices can’t shown up, I checked on the host, and there is no screen shot pictures there. Any ideas why?
thanks,
[attachment=529]
[hr]
“–processvideo yes” is not the reason, it doesn’t help even I remove this parameter

5

It turns out git pull again can solve everything :slight_smile:

6

To say iOS support is in a state of flux would be an understatement (particularly around video capture). I’ve been working on it heavily for the past few weeks and most of the kinks are worked out but there are still a lot of painful issues (the most painful of which is that OSX will only record video from one device at a time which makes scaling really expensive).

I’m planning on poking at using VNC to do video capture as an option which would remove the whole OSX requirement and allow for a lot more devices per host. Right now I have it set up so that 2 devices can share a single host reasonably well with them blocking each other only at the actual testing part where video is recorded (video processing, device prep, etc can happen while the other device is testing).

7

It sounds really a huge improvement, thanks for your hard working!