Fixing SecureConnectionStart bigger than zero condition

[saulo0710]

While conducting pageview performance analysis on our webpages, we noticed that several pageviews events carried many null values in their information. Further investigating, we came across the condition
in the timing context table calculations requiring secure_connection_start to be bigger than 0.
Apparently, on a user first access to a page the performanceTiming event carries a value for secure_connection_start timing, but on later access this value is set to 0. As a consequence we had approximately only 50% of pageview events with load performance information.
Removing the condition of the value being bigger than 0 should fix this problem.