tpmechanical.com website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.4 s faster on a phone.

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

6 images could be 4.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.

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

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

4 third-party services load with your homepage (Google Tag Manager, Vimeo and userway.org and others), adding 1.8 MB and 302 ms of main-thread time.

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

Vimeo costs a phone 114 ms of main-thread work and 1.5 MB 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.

Polyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Delivering Excellence & Innovation”.

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

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

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

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

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

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

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

Your homepage downloads 11.1 MB in 138 requests on a phone: images 8.6 MB (30), scripts 1.9 MB (41) and fonts 297 KiB (4). Under 2 MB keeps phones on slow connections fast.

Primary-Logo_RGB_Inverse_TP-Mechanical-scaled.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example Primary-Logo_RGB_Inverse_TP-Mechanical-scaled.png at 2,560 px wide, shown at 227 px. Resized copies would save about 47 KiB.

1 image (50 KiB) is 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 3.15 g of CO₂e: 377.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

All page content should be contained by landmarks: 24 elements on the page fail this check, rated moderate by axe-core.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

The homepage links to 48 pages on tpmechanical.com and 13 external pages.

There is no https://www.tpmechanical.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.tpmechanical.com/project/big-walnut-elementary-central-energy-plant, https://www.tpmechanical.com/project/greene-county-career-center, https://www.tpmechanical.com/2026/10/15/service-team-delivers-chiller-replacement-through-teamwork-and-problem-solving, https://www.tpmechanical.com/2026/10/12/one-partner-for-your-mechanical-systems and https://www.tpmechanical.com/2026/08/07/built-from-the-ground-up-how-tp-mechanical-develops-careers-through-real-world-experience have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.tpmechanical.com/contractors, whose canonical is https://www.tpmechanical.com/divisions/contractors. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.tpmechanical.com/about-tp, https://www.tpmechanical.com/project/big-walnut-elementary-central-energy-plant, https://www.tpmechanical.com/project/greene-county-career-center, https://www.tpmechanical.com/projects and https://www.tpmechanical.com/privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage has only about 224 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.