n8n Review: strong foundation, slow mobile (73/100)

Field	Value
Domain	n8n.io
Category	AI workflow automation and code-extensible business process automation
Pricing	Public prices evidenced: $20 Starter, $50 Pro and $800 Business; Business is self-hosted only.
Pages crawled	33
Crawl date	2026-10-08

n8n makes its audience legible quickly: technical teams, developers, and operators building AI agents and production automations.

The score is held back by execution on the mobile path. The mobile lab records 12.8 s LCP and 18.3 s TTI on a 10,169 KiB page, with mobile field data also reporting 425 ms INP and 0.69 CLS.

n8n makes its audience legible quickly: technical teams building AI agents and business-process automations. Proof includes 206,884 GitHub stars, a 4.7/5 G2 score, named enterprise users and quantified case studies. Vodafone savings and Trendyol usage add substance. Add a concise comparison against Zapier, Make and manual scripting.

n8n speaks clearly to developers, technical operators and small technical teams that want visual automation without surrendering code-level control. IT Ops, Sec Ops, Dev Ops and Sales make the audience concrete. “See and control,” debugging, secure deployments and self-hosting repeat the strongest product signal. Annual prices are explicit: $20 Starter, $50 Pro and $800 Business, with Business self-hosted only. The missing support concerns deployment trade-offs, migration effort and operational support after production adoption. Add a compact Cloud, self-hosted and Enterprise comparison beside pricing, with one concrete migration example.

A first-time visitor can identify n8n and reach pricing or signup, but the mobile journey is slowed by a 12.8-second LCP and 18.3 seconds to interactive. The homepage exposes Get Started and Pricing; pricing separates Starter, Pro, self-hosted and sales routes. Discoverability is stronger than decision support: a small-team visitor still interprets the hosted, self-hosted and enterprise split. The contact page also divides routes across teams. Reduce mobile payload and main-thread work, add a small-team recommendation beside plan choices, and place a routing guide above contact channels. This is a simulated walkthrough against crawl data, not live user testing.

n8n’s sampled pages perform well under automated checks, with a PSI accessibility score of 97, zero missing image alt attributes and zero unlabeled inputs. PSI fails the color-contrast audit on both homepage samples. The homepage DOM does not list a main landmark, and contact, pricing, features and support all report hasSkipLink false. Pricing contains one generic learn more link. Add a semantic main landmark and first-focusable skip link, replace the generic link with destination-specific text, and correct the affected contrast pairs to WCAG AA. Keyboard order, focus visibility, menus, dialogs, live regions and errors remain unverified.

Execution is held back by mobile weight, unsized images, contrast failure and weak heading hierarchy. Mobile records 12.8 s LCP, 6.2 s FCP, 18.3 s time to interactive and a 10,169 KiB payload; desktop carries 8,421 KiB and a 2.3 s LCP. PSI flags unsized images in both strategies, while the desktop contrast audit fails without exposing exact pairs. The homepage outline contains H2 and H3 headings but no H1. Add a descriptive hero H1, reserve image dimensions or aspect ratios, and extract failing contrast pairs before changing tokens. Re-run performance and stability checks.

The mobile critical path is n8n’s clearest performance weakness: the lab reports LCP 12,826.09 ms, FCP 6,226.04 ms and TTI 18,254.33 ms on a 10,169 KiB page. Field data reports LCP 3,807 ms, INP 425 ms and CLS 0.69. The page has 800 ms of estimated render-blocking savings and 227 KiB of unused JavaScript. Desktop weighs 8,421 KiB and uses 2.6 s of main-thread work. Prioritize the LCP resource, remove render-blocking work, reduce initial JavaScript and image payload, and reserve image dimensions.

n8n has 63,596 words across the crawl and useful specifics such as $20/mo billed annually, 2.5K workflow executions and 63% Common issues resolved in minutes. The homepage has no H1, and extraction reports one paragraph on most marketing pages: 1,262 words on the homepage, 1,362 on /features/ and 8,584 on /integrations/. Verify those counts before treating them as literal blocks. Sentence density is clearer: averages reach 31.2 words on /hosting and 29.6 on the license page. Add the H1, repair paragraph-boundary extraction, then split dense technical sentences into shorter units and lists.

n8n exposes monthly billing, an annual option marked Save 17% and a Starter plan, but the supplied pricing extract ends before the full comparison. The evidence confirms choices, not a defended recommendation for a first-time builder or a team scaling workflow executions. Proposed improvement: add a "Which plan is right for you?" path with audience guidance, trade-offs and execution-limit context. Keep annual-billed prices consistent and validate the comparison on mobile. The current extract does not support stronger claims about plan parity or the complete grid.

The confirmed QA issues are structural and mechanical, not evidence of an unedited AI pipeline. The homepage has no H1; average sentence length reaches 31.2 words on /hosting and 29.6 on the community-license page. Most marketing pages are flattened into one paragraph by extraction, so wall-of-text judgments should wait until boundaries are intact. Add and validate the H1, edit dense passages, repair extraction, then rerun structural QA and metadata checks.

n8n consolidates its host with a 301 redirect and returns a real 404 for nonexistent URLs. Its technical foundation is strong: robots.txt allows crawling apart from /cdn-cgi/, declares the sitemap, and the sampled homepage is 1,280 words in both raw and rendered forms. Cleanup remains: the sitemap reports 50,000 URLs and samples thank-you and utility/legal URLs; /intheloop/ and /intheloop both return 200; /oem/ canonicalizes to /n8n-for-platforms/. Align redirects, canonicals, internal links and sitemap entries, and add H1s to the homepage and contact page. /llms.txt is present at 200.

n8n is a strong fit for technical teams that want visual automation without giving up code-level control. The audience and product category are clear, and the technical SEO baseline is strong.nnThe main fix is performance: the mobile page is 10,169 KiB and records 12.8 s LCP and 18.3 s TTI. The next fixes are editorial and decision support: add the missing homepage H1, shorten long technical sentences, and turn the pricing surface into a more defensible comparison and recommendation.

This 13-dimension review uses a crawl of 33 pages completed on 2026-10-08, together with the supplied public dimension scores and summaries.