Website review, no card needed

tupl.com logo

tupl.com website review

Visit site (opens in a new tab)Reviewed 24 October 202615 issues · 70 checks

This review found 15 issues worth fixing on tupl.com, 3 of them high impact, across 70 checks. The most urgent: main-thread work: 4.9 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.5 s1.6 sJun 13Jul 181.7 s
Show as table
DateReal-visitor load time (LCP)
Jun 13, 20262.4 s
Jun 20, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of tupl.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tupl.com at 0.6 s0.6 s
  2. tupl.com at 1.2 s1.2 s
  3. tupl.com at 1.8 s1.8 s
  4. tupl.com at 2.4 s2.4 s
  5. tupl.com at 3.0 s3.0 s
  6. tupl.com at 3.6 s3.6 s
  7. tupl.com at 4.2 s4.2 s
  8. tupl.com at 4.8 s4.8 s

Speed

7 to fix72
  • Main-thread work: 4.9 s

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

  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    800 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (ContentSquare, Google Tag Manager and Cloudflare CDN and others), adding 589 KiB and 738 ms of main-thread time.

  • Reduce unused JavaScript

    300 ms · 260 KiB

    About 260 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.

  • ContentSquare adds 327 ms

    327 ms

    ContentSquare costs a phone 327 ms of main-thread work and 207 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.

  • Google Tag Manager adds 299 ms

    299 ms

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

  • Use efficient cache lifetimes

    214 KiB

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

  • 5 long tasks on the main thread

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

  • Improve image delivery

    80 KiB

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

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 34 ms

    34 ms

    Your server sent the HTML in 34 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix69
  • Largest Contentful Paint: 5.8 s

    5.8 s

    Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “THE PROVEN AI AUTOMATION SYSTEM”.

  • Time to Interactive: 7.5 s

    7.5 s

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

  • Speed Index: 5.5 s

    5.5 s

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

  • Not enough real-visitor data yet

    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.

4 checks passed
  • Largest content (LCP) got 22% faster for real visitors

    -22%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 166 ms

    166 ms

    Scripts block the page for only 166 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix90
  • 1 image far larger than shown

    325 KiB

    1 image is downloaded at several times the size a phone draws it, for example ai-care-dash.svg at 1,452 px wide, shown at 206 px. Resized copies would save about 325 KiB.

  • About 0.3 g of CO₂ per visit

    0.33 g

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

3 checks passed
  • Page weight: 1.2 MB in 43 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 43 requests on a phone: scripts 620 KiB (13), images 522 KiB (20) and HTML 28 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

2 to fixGoogle 10098
  • All page content should be contained by landmarks (8 elements)

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100
  • 47 internal links, 5 external

    The homepage links to 47 pages on tupl.com and 5 external pages.

8 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “TuplOS is the AI-native hyperautomation platform for enterprise operations, trusted by T-Mobile, NTT Docomo, Deloitte, …”.

  • One H1 headline

    Your main headline reads: “OperationsMade Simplewith AI”.

  • Title: 39 characters

    Your title is a healthy 39 characters: “Tupl — AI Hyperautomation in Operations”.

  • Canonical URL set

    The canonical URL is https://tupl.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://tupl.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (878 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://tupl.com/llms.txt (5 KiB, 34 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    47 of 52 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,026 words of copy

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get a Demo →” and “Go to Get Started”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Get a Demo →” and “Contact Us”.

  • Social proof on the page

    Social proof on the homepage: 5 testimonial or review blocks, 42 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 8 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at tupl.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 15 issues on tupl.com, including 10 speed issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25