lathem.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Hotjar and others), adding 1.5 MB and 1.0 s of main-thread time.

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

About 188 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 790 ms faster on a phone.

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

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

Google Tag Manager costs a phone 387 ms of main-thread work and 374 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

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

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

Vimeo costs a phone 33 ms of main-thread work and 513 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.

11 images could be 98 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

7 KiB could be saved by minifying CSS.

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

Desktop scores 87 but mobile only 58. A gap that wide usually means heavy scripts and images that hit phones hardest.

10 KiB could be saved by minifying JavaScript.

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.

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

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

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

Your largest element takes 3.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PayClock makes employee time tracking and attendance manage…”. Most of its time is element render delay (7.9 s).

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

15 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-17, real Chrome visitors' tap response (inp) went from 96 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 2.2 MB in 102 requests on a phone: scripts 1.6 MB (37), images 275 KiB (20) and stylesheets 140 KiB (17). Under 2 MB keeps phones on slow connections fast.

6 images further down the page (172 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

26 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

5 links inside paragraphs rely on colour alone to stand out.

1 frame has no title, so screen-reader users cannot tell what it contains.

1 image has no alt text, which hurts accessibility and image search.

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

Headings skip levels (h1 → h3 and h3 → h5), which makes the page harder to scan with a screen reader.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Structured data found (Organization and Service) but with 2 problems, for example “Service: missing name”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.lathem.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at lathem.com/robots.txt, the first file search crawlers ask for.

2 links have no real href, so search engines can't follow them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 49 pages on lathem.com and 12 external pages.

There is no https://www.lathem.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.lathem.com/time-clocks/punch-time-clocks took over 3 s to send its HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17431161&tm=gtm002&Ver=2&mid=4eb46bf4-9a70-4a79-8d1c-dfc26cd28a51&bo=1&sid=f2fd5a70cda411f1903ae95495526aac&vid=f2fd7f30cda411f199f2cfbf82c8399a&vids=1&msclkid=N&pi=91.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

5 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

1 image is served at too low a resolution for sharp phone screens.

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

Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 402 words of visible text.

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

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

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