teamwork.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and VWO and others), adding 1.5 MB and 1.2 s of main-thread time.

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

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

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

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

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

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

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

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

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.

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

Your largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Most tools track work. We make it profitable.”.

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

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

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

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

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

Your homepage downloads 3.4 MB in 279 requests on a phone: scripts 1.9 MB (149), images 1.2 MB (49) and HTML 88 KiB (1). Under 2 MB keeps phones on slow connections fast.

1e2532e2d12c89c7cd3c3ff95f559e864af7fd5c.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example projects-layer-1.svg at 618 px wide, shown at 154 px. Resized copies would save about 43 KiB.

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

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

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

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

There are 2 <h1> headlines (“AI-POWERED PROFESSIONAL SERVICES AUTOMATION” and “AI-POWERED PROFESSIONAL SERVICES AUTOMATION”). One clear main headline is easier for people and search engines.

Your meta description is 181 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 199 pages on teamwork.com and 9 external pages.

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

1 link go through two or more redirects, for example https://reddit.com/r/teamworkdotcom.

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.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

teamwork.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 1,008 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 Google Tag Manager (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 12 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.