blacktrident.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Cookiebot and others), adding 2.1 MB and 1.0 s of main-thread time.

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

11 images could be 555 KiB 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.

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

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

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

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

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

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

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

22 KiB could be saved by minifying JavaScript.

11 KiB JavaScript is shipped twice across bundles.

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.

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

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

Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Real visitors wait 219 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 121 ms to 222 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 1.9 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

Your homepage downloads 4.5 MB in 445 requests on a phone: scripts 1.8 MB (191), images 1.1 MB (35) and other files 1.1 MB (164). Under 2 MB keeps phones on slow connections fast.

hero-slider-crye2_mobile.jpg 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).

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

Certain ARIA roles must contain particular children: 4 elements on the page fail this check, rated critical by axe-core.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

ARIA role should be appropriate for the element: 32 elements on the page fail this check, rated minor by axe-core.

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 67 characters, so Google will cut it off around 60: “Black Trident Tactical Gear – Black Trident® - Special Purpose Gear”.

Your <h1> is empty.

The homepage links to 592 pages on blacktrident.com and 11 external pages.

There is no /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.

/en-us/collections/all-kydex-products-black-trident has no meta description, so Google writes the search snippet from whatever text it finds.

/en-us/collections/all-kydex-products-black-trident has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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.

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

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

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.

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

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

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.

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 Meta Pixel (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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