retrue.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and omnisnippet1.com and others), adding 1.1 MB and 484 ms of main-thread time.

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

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

Shopify costs a phone 191 ms of main-thread work and 601 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.

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

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

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

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

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

2 KiB could be saved by minifying CSS.

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

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “RETRUE pickup truck towing RV trailer with air bag suspensi…”.

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

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

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

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

Your homepage downloads 3.8 MB in 345 requests on a phone: images 1.3 MB (23), scripts 1.3 MB (146) and other files 788 KiB (105). Under 2 MB keeps phones on slow connections fast.

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

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

12 elements hidden from screen readers can still receive keyboard focus.

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

ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

15 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

Structured data found (BreadcrumbList, Organization, WebSite and WholesaleStore) but with 1 problem, for example “Organization: sameAs is an empty list”.

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

The homepage links to 107 pages on retrue.com and 7 external pages.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /collections/ridehelper%E2%84%A2-air-suspension-kit-regular, whose canonical is /collections/ridehelper%e2%84%a2-air-suspension-kit-regular. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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

4 errors were logged to the browser console while the page loaded, for example “Invalid regular expression flags”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

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.

retrue.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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.

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 565 words of visible text.

DMARC is set to p=none, so mail pretending to be retrue.com is still delivered. Add a report address, check the reports, then move to quarantine.

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 Ads, Google Analytics, Google Tag Manager and Hotjar (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 16 cookies, 1 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 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.