trello.com website review

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

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

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

8 third-party services load with your homepage (atl-paas.net, Google CDN and Google Tag Manager and others), adding 3.3 MB and 1.8 s of main-thread time.

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

Google CDN costs a phone 482 ms of main-thread work and 1.1 MB 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.

atl-paas.net costs a phone 506 ms of main-thread work and 867 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 461 ms of main-thread work and 805 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 220 ms. During a long task the page ignores taps.

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

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

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

Polyfills for old browsers add 20 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.

2 KiB could be saved by minifying CSS.

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.

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

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

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

Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

Your homepage downloads 6.9 MB in 136 requests on a phone: scripts 3.1 MB (35), media 1.6 MB (2) and images 984 KiB (25). Under 2 MB keeps phones on slow connections fast.

5 images (321 KiB) 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.95 g of CO₂e: 234.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.

2 links inside paragraphs rely on colour alone to stand out.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

Elements with visible text labels do not have matching accessible names. (3 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://a594014.sitemaphosting7.com/4704043/sitemap_4704043.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 63 pages on trello.com and 24 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://trello.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.

/ and https://trello.com/home all use the title “Capture, organize, and tackle your to-dos from anywhere”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://trello.com/power-ups and https://trello.com/templates use the same meta description. A description written for each page earns more clicks.

https://trello.com/home, https://trello.com/power-ups, https://trello.com/templates and https://trello.com/integrations have no <h1> headline, so visitors and search engines get no clear main topic.

https://trello.com/power-ups and https://trello.com/templates have 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 31 found) and read each the way a search engine does.

1 third-party cookie is 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 “The source list for the Content Security Policy directive 'connect-src' contains an invalid source: 'https://trello.com/gateway/api/ais/a…”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

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

Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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 1,180 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (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 9 cookies (measured from a US location before any click).

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