You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got very strange result.
The performance result for mobile are better than desktop (i never saw this), and they seems inverted comparing with online Google Insight.
I ran lighthouse localy (the package from google, without sitespeed.io), and the order is ok and like the online pagespeed insight.
So it really seems, like it is inverted on the plugin in sitespeed.io !?
Is it a bug ?
I didn't inverted, because formfactor on snapshot done by lighthouse is well on format desktop for desktop profile/connectivity and well on format mobile for mobile profile/connectivity.
Thanks!
The text was updated successfully, but these errors were encountered:
Got it! There is no bug in the lighthouse plugin for sitespeed.io.
With the lightouse stand-alone I was using for desktop the profile lr-deskop. And online Google Page Insight seems too.
So the solution would be to allow using the lr-desktop and lr-mobile with this lighthouse plugin.
I have opened an issue asking for this improvement: #47
It will solve this issue, and provide better result in coherence with online Google Pagespeed Insight.
Hello,
I got very strange result.
The performance result for mobile are better than desktop (i never saw this), and they seems inverted comparing with online Google Insight.
Here is the config for mobile:
And for desktop:
The json config:
The desktop result:
The mobile result:
Online pagespeed insight desktop:
Online pagespeed insight mobile:
I ran lighthouse localy (the package from google, without sitespeed.io), and the order is ok and like the online pagespeed insight.
So it really seems, like it is inverted on the plugin in sitespeed.io !?
Is it a bug ?
I didn't inverted, because formfactor on snapshot done by lighthouse is well on format desktop for desktop profile/connectivity and well on format mobile for mobile profile/connectivity.
Thanks!
The text was updated successfully, but these errors were encountered: