engineeredcabs.com website review

20 images could be 3.2 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.

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

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

14 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

8 third-party services load with your homepage (Google Tag Manager, Hotjar and brandcdn.com and others), adding 376 KiB and 360 ms of main-thread time.

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

3 long tasks block the main thread while loading, the longest for 151 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).

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

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.

3 KiB could be saved by minifying CSS.

Your largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SAFETY. COMFORT. PRODUCTIVITY. Crenlo is the technology lea…”.

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

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

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

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

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

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

Your homepage downloads 25.7 MB in 95 requests on a phone: media 19.6 MB (3), images 5.4 MB (41) and scripts 412 KiB (12). Under 2 MB keeps phones on slow connections fast.

11 images are downloaded at several times the size a phone draws them, for example cross-functional.png at 851 px wide, shown at 175 px. Resized copies would save about 815 KiB.

12 images (825 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.

4 images further down the page (791 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 7.29 g of CO₂e: 875.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

11 buttons have no accessible name, so screen readers announce just “button”.

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

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

5 images have no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Your title is only 13 characters: “Home - Crenlo”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 63 characters: “We deliver #engineeredcabs for off-highway vehicle applications”. 70 to 160 characters is enough to sell the click.

There are 3 <h1> headlines (“Safety. Comfort. Productivity.”, “Engineer. Excellence.” and “Design. build. deliver.”). One clear main headline is easier for people and search engines.

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

The homepage links to 49 pages on engineeredcabs.com and 1 external page.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

/contact, /suppliers and /sustainability have no <h1> headline, so visitors and search engines get no clear main topic.

/difference/complex-fabrication has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

21 of 30 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.

3 errors were logged to the browser console while the page loaded, for example “Error with Permissions-Policy header: Parse of permissions policy failed because of errors reported by structured heade…”.

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

http://engineeredcabs.com does not redirect to https, so some visitors land on the insecure version.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

engineeredcabs.com is registered until Dec 2026. Make sure auto-renew is on and the card on file is current.

engineeredcabs.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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 230 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 form on the homepage, so every lead has to click through to another page first.

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

DMARC is set to p=none, so mail pretending to be engineeredcabs.com is still delivered. Reports are on, so moving to quarantine is the next step.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

engineeredcabs.com has no MX record, so it receives no email. SPF -all and DMARC reject still matter: they stop others sending mail as you.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Hotjar and The Trade Desk (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 6 cookies (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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.