treasure.ai website review

6 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 13.4 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Facebook and others), adding 1.8 MB and 1.8 s of main-thread time.

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

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

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

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

Hotjar costs a phone 273 ms of main-thread work and 67 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.

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

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

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 31.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Move at the Speed of Now. Turn customer data into campaigns…”.

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

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

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

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

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

For real visitors the layout shifts by 0.17 (75th percentile). Good is under 0.1.

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

Over the last 25 four-week periods to 2026-10-17, 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).

The layout shifts by 0.187 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Your homepage downloads 6.0 MB in 133 requests on a phone: images 3.4 MB (35), scripts 2.1 MB (41) and fonts 410 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example logo3d-red.png at 906 px wide, shown at 171 px. Resized copies would save about 38 KiB.

1 image (56 KiB) is 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.

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

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 68 characters, so Google will cut it off around 60: “Treasure AI | Agentic Experience Platform (AEP) for Modern Marketers”.

There are 2 <h1> headlines (“Move at the Speed of Now.” and “The Treasure AI advantage”). One clear main headline is easier for people and search engines.

Your meta description is 248 characters; Google truncates after about 160, so the end of your pitch is cut.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 134 pages on treasure.ai and 13 external pages.

Your robots.txt lets Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

https://www.treasure.ai/security has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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.

The homepage carries about 480 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 5 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 17 cookies, 1 of them by other companies (measured from a US location before any click).

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