wajax.com website review

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

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

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

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

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

6 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and StackAdapt and others), adding 595 KiB and 434 ms of main-thread time.

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

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

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

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.

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

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

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

Real visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Wajax industrial equipment technicians on-site”. Most of its time is resource load delay (2.9 s).

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

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

Your homepage downloads 2.7 MB in 69 requests on a phone: images 1.5 MB (17), scripts 834 KiB (28) and fonts 384 KiB (9). Under 2 MB keeps phones on slow connections fast.

6 images (785 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.

5 images further down the page (731 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.77 g of CO₂e: 92.6 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: 8 elements on the page fail this check, rated moderate by axe-core.

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “Organization: missing name”.

The homepage links to 166 pages on wajax.com and 22 external pages.

There is no https://www.wajax.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.wajax.com/ehs, https://www.wajax.com/ehs/community, https://www.wajax.com/ehs/diversity-and-equal-opportunity, https://www.wajax.com/ehs/environmental-responsibility, https://www.wajax.com/ehs/governance and https://www.wajax.com/wajax-in-action and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.wajax.com/about and https://www.wajax.com/locations have no <h1> headline, so visitors and search engines get no clear main topic.

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

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 ()”.

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 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.

The homepage carries about 548 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 (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 13 cookies (measured from a US location before any click).

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