timetac.com website review

62 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.7 s.

The page has 4,036 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

A phone's processor spends 4.0 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Your mobile performance score is 55 (desktop: 70). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (YouTube, Google Tag Manager and Cookiebot and others), adding 1.6 MB and 780 ms of main-thread time.

About 890 KiB of JavaScript is downloaded but never used on this page.

YouTube costs a phone 432 ms of main-thread work and 985 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google Tag Manager costs a phone 277 ms of main-thread work and 366 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

8 long tasks block the main thread while loading, the longest for 182 ms. During a long task the page ignores taps.

About 134 KiB of CSS is downloaded but never applied on this page.

2 files are served with short cache lifetimes, so returning visitors download them again (34 KiB).

3 images could be 28 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 18 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying JavaScript.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

The page becomes fully interactive after 18.9 s. Good is under 3.8 s.

Visually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.

Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “One place for billable hours, leave, and overtime. Finally.”.

Real visitors wait 907 ms for your server to start answering (75th percentile). Good is under 800 ms.

The first text or image appears after 2.7 s on a phone. Good is under 1.8 s.

Scripts block taps and scrolling for 441 ms in total while the page loads. Good is under 200 ms.

The layout shifts by 0.188 while loading, so content jumps under the reader's thumb. Good is under 0.1.

7 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 138 ms to 141 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.7 MB in 170 requests on a phone: scripts 1.8 MB (46), images 299 KiB (39) and fonts 243 KiB (5). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 92.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

3 visible links have no text or label, so screen readers cannot say where they go.

The homepage links to 94 pages on timetac.com and 21 external pages.

We fetched 15 pages linked from your homepage (of 50 found) and read each the way a search engine does.

5 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 1,005 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 2 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.