Due to Clockit being a web app sometimes there can be issues with the browser that stops Clockit from loading properly. Please keep reading for some Firefox specific fixes below.

If you're using Firefox and having issues loading Clockit the first thing you should do is try loading Clockit up in a 'New Private Window' as this will tell us more about what the issue is.

To do this, click on the 3 vertical bars in the top right of the browser and then open new private window.

In the new private window type in app.clockit.co.nz (for NZ customers) or app.clockitsoftware.com.au (for Australian customers).

Then login as per usual.

If this loads correctly then you may have an issue with corrupt cache or a browser extension. Both can be fixed easily.

Cache

Firefox cache temporarily stores images, scripts, and other parts of websites you visit in order to speed up your browsing experience, sometimes the cache can corrupt and cause issues with websites and web apps.

To clear the cache, open up the Firefox browser and go to app.clockit.co.nz (for NZ customers) or app.clockitsoftware.com.au (for Australian customers) and click on the padlock next to the start of the URL, then click on Clear Cookies and Site Data

On the next page make sure Clockit is highlighted and click on the 'Remove' button.

Once complete, please restart the browser and login in too Clockit.

If you're still having problems move onto the next step below.

Browser extensions are small programs that add functionality to your browser, to see if it's an issue with a browser extension the easiest way is to go through and turn them all off and then reload the page.

To do this click on the 3 vertical lines at the top right of Firefox and then click on preferences.

At the bottom left of the preferences page click on 'Extensions & Themes'.

This page will list all of the extensions you have, use the blue toggle to turn them off.

Once done restart the browser and login in to Clockit.

If this has solved the issue then you will need to turn on the extensions one at a time to see which one is causing it, and then check the settings of that extension.