actux.com website review

About 454 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

Your mobile performance score is 40 (desktop: 59). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Facebook, TikTok and openai.com and others), adding 802 KiB and 963 ms of main-thread time.

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

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

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

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

Facebook costs a phone 289 ms of main-thread work and 229 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.

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

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

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

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

10 KiB could be saved by minifying CSS.

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 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Gentleman’s Guru presents a distinguished array of timeless…”.

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

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

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

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

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

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

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

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

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

1 image has no alt text, which hurts accessibility and image search.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

50 links have no real href, so search engines can't follow them.

There are 3 <h1> headlines (“American Comodore Tuxedo – Actux”, “” and “”). One clear main headline is easier for people and search engines.

The homepage links to 492 pages on actux.com and 11 external pages.

We fetched 15 pages linked from your homepage (of 186 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 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 503 ()”.

Large scripts ship without source maps.

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

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

1 link from your homepage to your own site is broken, for example https://www.gentlemansguru.com/cdn-cgi/l/email-protection (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

2 links go through two or more redirects, for example https://www.facebook.com/sharer.php?u=https://www.gentlemansguru.com/american-comodore-actux/.

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

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

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

The homepage carries about 765 words of visible text.

actux.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

actux.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

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.

actux.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 Tag Manager and Klaviyo (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 8 cookies (measured from a US location before any click).

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