clickup.com website review

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

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

About 852 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.2 s faster on a phone.

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

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

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

About 3.9 MB of JavaScript is downloaded but never used on this page.

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

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

7 third-party services load with your homepage (Optanon, Google Tag Manager and Quora Ads and others), adding 774 KiB and 874 ms of main-thread time.

Optanon costs a phone 568 ms of main-thread work and 237 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 costs a phone 283 ms of main-thread work and 314 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 140 KiB JavaScript that modern phones do not need.

31 KiB could be saved by minifying JavaScript.

10 KiB JavaScript is shipped twice across bundles.

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.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “One Workspace built to think and work”.

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

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

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

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

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

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

Your homepage downloads 15.6 MB in 236 requests on a phone: scripts 7.7 MB (96), other files 3.4 MB (85) and images 2.0 MB (42). Under 2 MB keeps phones on slow connections fast.

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

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

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

2 tap targets are too small or too close together to hit reliably with a finger.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

Alternative text of images should not be repeated as text: 50 elements on the page fail this check, rated minor by axe-core.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Your title is 68 characters, so Google will cut it off around 60: “ClickUp™ | Maximize productivity • Software, AI, and humans converge”.

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

There are 3 <h1> headlines (“One Workspace built to think and work”, “Software toreplace all software” and “One Workspace built to think and work”). One clear main headline is easier for people and search engines.

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

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 18 pages on clickup.com and 1 external page.

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.

The HTML your server sends has 387 of the 755 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

/features/sprints 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.

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=17492975&tm=gtm002&Ver=2&mid=ba030ef7-3c5f-437c-81a8-a529934afbe4&bo=2&sid=fcd52ef0d48511f192d5f398271cbaf1&vid=fcd555d0d48511f1819e2157b2453e9f&vids=1&msclkid=N&pi=91.

4 errors were logged to the browser console while the page loaded, for example “"undefined" is not valid JSON”.

Large scripts ship without source maps.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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

clickup.com'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.

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.

The homepage carries about 755 words of visible text.

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 Amplitude, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel 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 38 cookies (measured from a US location before any click).

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