expando.ai website review

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

8 third-party services load with your homepage (Framer CDN, Hubspot and Google Tag Manager and others), adding 3.2 MB and 970 ms of main-thread time.

Framer CDN costs a phone 825 ms of main-thread work and 2.6 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.

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

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

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

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

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

ESM>CDN costs a phone 13 ms of main-thread work and 363 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 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

145 KiB JavaScript is shipped twice across bundles.

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

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.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.3 MB in 123 requests on a phone: images 1.9 MB (56), scripts 1,017 KiB (49) and other files 209 KiB (11). Under 2 MB keeps phones on slow connections fast.

16 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example TVnBMBuoniWUdzDBhYMlWk7wcw.svg at 1,343 px wide, shown at 358 px. Resized copies would save about 42 KiB.

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

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

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

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

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

Structured data found (FAQPage, Organization and Product) but with 1 problem, for example “Product: no offers (price) block”.

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

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

The homepage links to 62 pages on expando.ai and 33 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.

We fetched 13 pages linked from your homepage and read each the way a search engine does.

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

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

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.

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

expando.ai 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.

expando.ai'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.

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 1,272 words of visible text.

DMARC is set to p=none, so mail pretending to be expando.ai 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 Tag Manager, HubSpot and Microsoft Clarity (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 9 cookies, 5 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.