taos.com website review

146 files are served with short cache lifetimes, so returning visitors download them again (4.3 MB).

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.

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

About 1.7 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.

IBM Digital Analytics costs a phone 2.0 s of main-thread work and 2.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (IBM Digital Analytics, Clarity and o11.tech and others), adding 3.5 MB and 3.2 s of main-thread time.

Clarity costs a phone 518 ms of main-thread work and 28 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.

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

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

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

2 KiB could be saved by minifying JavaScript.

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

64 KiB could be saved by minifying CSS.

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

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.

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

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

Your largest element takes 20.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Two female programmers working on new project in the office…”.

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

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

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

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

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

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

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

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

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-24, real Chrome visitors' largest content (lcp) went from 4.8 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.8 MB in 356 requests on a phone: scripts 5.0 MB (148), images 1.2 MB (50) and other files 962 KiB (137). Under 2 MB keeps phones on slow connections fast.

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

Certain ARIA roles must be contained by particular parents: 12 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

<svg> elements with an img or image role must have alternative text: 3 elements on the page fail this check, rated serious by axe-core.

Some lists contain elements other than list items, which screen readers announce wrongly.

1 element hidden from screen readers can still receive keyboard focus.

1 link inside paragraphs relies on colour alone to stand out.

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

Heading levels should only increase by one: 3 elements on the page fail this check, rated moderate by axe-core.

Banner landmark should not be contained in another landmark: 1 element on the page fails 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.

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

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

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

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 22 pages on taos.com and 3 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.

There is no https://www.ibm.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.

Your homepage links to https://www.ibm.com/downloads/documents/us-en/17f55bd4e7b9f49c, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.ibm.com/downloads/documents/us-en/1227cc9dd54b9bb2 has no <title>, so Google invents the link text in results.

https://www.ibm.com/forms/mkt-53467 is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.ibm.com/forms/mkt-53467 and https://www.ibm.com/downloads/documents/us-en/1227cc9dd54b9bb2 have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.ibm.com/homepage, whose canonical is https://www.ibm.com/us-en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.ibm.com/forms/mkt-53467, https://www.ibm.com/downloads/documents/us-en/1227cc9dd54b9bb2 and https://www.ibm.com/thought-leadership/institute-business-value/c-suite-study/ceo have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.ibm.com/thought-leadership/institute-business-value/c-suite-study/ceo has 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 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.

2 images failed to load on a phone, for example https://id.rlcdn.com/464526.gif.

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

4 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

Large scripts ship without source maps.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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

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

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

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