fix: Try to use a better performance API

packages/utils/src/time.ts

@@ -135,14 +135,27 @@ export const browserPerformanceTimeOrigin = ((): number | undefined => {
   if (!performance) {
     return undefined;
   }
-  if (performance.timeOrigin) {
+  // If performance APIs are over an hour skewed don't use them
+  const THRESHOLD = 3600 * 1000;
+  // eslint-disable-next-line deprecation/deprecation
+  const navigationStart = performance.timing && performance.timing.navigationStart;
+  const hasNavigationStart = typeof navigationStart === 'number';
+  // Unfortunately browsers may report an inaccurate time origin data, which results in poor results in performance
+  // data. We treat time origin data as reliable if they are either within a reasonable threshold of the current time,
+
+  const timeOriginIsReliable = performance.timeOrigin && Math.abs(performance.timeOrigin + performance.now() - Date.now()) < THRESHOLD;
+  if (performance.timeOrigin && timeOriginIsReliable) {
     return performance.timeOrigin;
   }
   // While performance.timing.navigationStart is deprecated in favor of performance.timeOrigin, performance.timeOrigin
   // is not as widely supported. Namely, performance.timeOrigin is undefined in Safari as of writing.
   // Also as of writing, performance.timing is not available in Web Workers in mainstream browsers, so it is not always
   // a valid fallback. In the absence of an initial time provided by the browser, fallback to the current time from the
   // Date API.
-  // eslint-disable-next-line deprecation/deprecation
-  return (performance.timing && performance.timing.navigationStart) || Date.now();
+  const navigationStartIsReliable = Math.abs(navigationStart + performance.now() - Date.now()) < THRESHOLD;
+  if (hasNavigationStart && navigationStartIsReliable) {
+    return navigationStart;
+  }
+  // Either both timeOrigin and navigationStart are skewed or neither is available, fallback to Date.
+  return Date.now();
 })();