This is a known issue to where the out-of-the-box settings of UFT are causing a conflict with what's currently supported when using Apple Safari. Basically, Safari doesn't support the load time property, so its load time value for Page and Frame test objects will always be 0. The problem is, in Page checkpoints, the load time property is enabled by default (which it shouldn't be), so your workaround is to disable the load time property.