tuple.app website review

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

3 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

About 236 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

6 third-party services load with your homepage (Google Tag Manager, reddit and LinkedIn Ads and others), adding 210 KiB and 480 ms of main-thread time.

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

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

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

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

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.

2 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

Your homepage downloads 5.8 MB in 72 requests on a phone: media 2.5 MB (4), images 1.7 MB (10) and fonts 752 KiB (4). Under 2 MB keeps phones on slow connections fast.

macos.Chdnb56C.jpg weighs 1.5 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example macos.Chdnb56C.jpg at 3,200 px wide, shown at 350 px. Resized copies would save about 1.3 MB.

3 images (1.6 MB) are 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.64 g of CO₂e: 197.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

There are 3 <h1> headlines (“Tuple”, “Screen sharing for people who build software.” and “Tuple”). One clear main headline is easier for people and search engines.

The homepage links to 32 pages on tuple.app and 19 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 /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.

/gcal and /ical use the same meta description. A description written for each page earns more clicks.

/bug-bounty has no <h1> headline, so visitors and search engines get no clear main topic.

/jobs 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 14 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 link go through two or more redirects, for example https://tuple.app/community-slack.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

tuple.app 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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 722 words of visible text.

DMARC is set to p=none, so mail pretending to be tuple.app is still delivered. Reports are on, so moving to quarantine is the next step.

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 Tag Manager, LinkedIn Insight and Reddit Pixel (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 3 cookies (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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.