tridentgum.com website review

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

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

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

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

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

4 third-party services load with your homepage (Google Tag Manager, Cookiebot and Google Fonts and others), adding 1.6 MB and 93 ms of main-thread time.

sanity.io costs a phone 0 ms of main-thread work and 1.1 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.

Cookiebot costs a phone 43 ms of main-thread work and 362 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.

1 file is served with short cache lifetimes, so returning visitors download them again (36 KiB).

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

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.

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

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

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

Real visitors wait 208 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' largest content (lcp) went from 2.8 s to 3.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

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

1 image 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 171 ms to 182 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 images are downloaded at several times the size a phone draws them, for example 8557b590c947fae385c733a464eb44334504e32f-2932x2138.png at 3,840 px wide, shown at 200 px. Resized copies would save about 581 KiB.

Your homepage downloads 2.3 MB in 94 requests on a phone: images 1.1 MB (8), scripts 1,001 KiB (47) and stylesheets 78 KiB (19). Under 2 MB keeps phones on slow connections fast.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is only 25 characters: “TriDifferent | Trident US”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 51 characters: “TriDifferent with Refreshingly long-lasting flavors”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 30 pages on tridentgum.com and 12 external pages.

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.

The HTML your server sends has 264 of the 528 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://www.tridentgum.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.tridentgum.com/products, https://www.tridentgum.com/legal-notice, https://www.tridentgum.com/contact-us, https://www.tridentgum.com/privacy-policy, https://www.tridentgum.com/cookies-policy and https://www.tridentgum.com/supply-chain-act have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.tridentgum.com/products and https://www.tridentgum.com/faq have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.tridentgum.com/products, https://www.tridentgum.com/faq, https://www.tridentgum.com/contact-us and https://www.tridentgum.com/cookies-policy have 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 14 pages linked from your homepage and read each the way a search engine does.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

Before a visitor clicks anything, the page loads Google Tag Manager (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.

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