productivity.com website review

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

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

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

About 106 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 380 ms faster on a phone.

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

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

2 third-party services load with your homepage (Google Maps and Adobe TypeKit), adding 165 KiB and 72 ms of main-thread time.

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

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

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

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.

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.

Your largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

Productivity_logo_horizontal_2C_TM.svg weighs 506 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.8 MB in 39 requests on a phone: media 1.2 MB (1), images 1.2 MB (18) and scripts 170 KiB (5). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Sales-All-2025-web-png-3_23_26-400x267.png at 390 px wide, shown at 20 px. Resized copies would save about 214 KiB.

2 images (219 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

12 tap targets are too small or too close together to hit reliably with a finger.

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.

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

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

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

Your title is 78 characters, so Google will cut it off around 60: “Metalworking CNC Machine Tools Supplier & Equipment Distributor | Productivity”.

14 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 282 pages on productivity.com and 31 external pages.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://productivity.com/events, whose canonical is https://productivity.com/company/events. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://productivity.com/blog has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

The homepage carries about 844 words of visible text.

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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