Projecttile earns 67/100 for a clear AI-powered Gantt timeline offer, strong accessibility evidence, and concrete product demonstrations. Its most material weaknesses are the 1/100 public docs and self-serve-help score and mobile LCP of 8.3–8.9 seconds in the available lab samples.
Reviewed by SiteList Engine · 12 of 13 dimensions · published Reviewed on October 24, 2026
Is this your site?
Claim itProjecttile is a web-based AI-powered Gantt timeline and cascading project scheduling tool.
| Field | Value |
|---|---|
| Domain | projecttile.app |
| Category | AI-powered Gantt timeline and cascading project scheduling |
| Platform | Web |
| Pricing | The supplied site facts do not establish a single pricing model or overall price range; the pricing page visibly shows Free at $0/month, Sole at $3/month, and Team at $8/month, with a monthly/yearly toggle. |
| Pages crawled | 7 |
| Crawl date | 2026-10-18 |
| SiteList score | 67/100 |
Projecttile earns 67/100 overall, with a clear product proposition and a useful interactive timeline surface. The product is legible as an AI-powered Gantt timeline tool with cascading dependencies, and the strongest measured dimensions are accessibility at 85/100, writing quality at 76.6/100, technical SEO at 77.5/100, and usability at 73.4/100.
The main gaps are practical rather than conceptual. Docs and self-serve help score 1/100, while design execution scores 52/100. Mobile performance is also a material constraint: LCP is 8.3–8.9 seconds across the homepage, pricing, and terms samples, compared with about 1.4–1.6 seconds on desktop. Audience and messaging score 60.9/100, suggesting that the initial offer is understandable but decision support needs more work. Risk and stability score 64.1/100, with canonical patterns and a 200 soft 404 identified as technical risks.
The result is a focused scheduling product with a credible core workflow, held back by support coverage, mobile speed, and visual refinement.
Projecttile makes its category clear quickly, but its audience signal is broader than its strongest mechanism. The title calls it an AI-powered Gantt timeline tool, while the meta description explains that a project outline becomes a live timeline whose downstream dates cascade when work changes. The about page names freelancers, teams, and personal projects; pricing translates those into Sole and Team paths. The crawl also shows product demonstrations for AI-generated sequences, drag-and-resize controls, read-only sharing, calendar feeds, and exports. That proof is feature-led: no attributable case study, testimonial, or review source appears in the supplied extract. Name one primary launch audience, then support the positioning with a customer outcome and an honest comparison against spreadsheets or heavier project tools.
Projecttile answers what the product is and what it costs, but leaves several pre-sign-up questions unresolved in the supplied evidence. The about page presents a three-step workflow—Describe the project, Make it yours, and Work the plan—and the captured UI shows Generate project via AI above a visible timeline. Pricing is direct: Free is $0 forever, Sole is $3/month for freelancers with multiple projects, and Team is $8/month for shared team projects. The crawl does not provide evidence for migration, support, cancellation, plan changes, or correction of an AI-generated plan. Add a compact decision FAQ and one named outcome story, while keeping the three-step workflow in the first viewport.
This is a simulated cognitive walkthrough against crawl data, not live user testing. Projecttile has a straightforward desktop path, but mobile navigation and load speed interrupt the same journey. The desktop homepage exposes Generate Project via AI, team cards, task controls, a project timeline, Pricing, and Get Started. On pricing, Free is $0 forever, Sole is $3/month, and Team is $8/month, with explicit start and upgrade actions. The captured mobile header shows Sign In and Get Started but no visible Pricing link or labeled menu. The homepage mobile run records 8.3 seconds LCP, while the consent banner covers lower timeline content. Add a labeled mobile pricing route, reduce the banner footprint, and address the slow first render.
Projecttile has a promising accessibility baseline, but the homepage needs structural and interaction fixes before a stronger claim is warranted. Sampled documents declare lang="en"; pricing, privacy, and terms expose header, nav, main, and footer landmarks with ordered headings. PSI reports accessibility scores of 91 for the homepage and 100 for pricing. Against that foundation, the homepage DOM reports no landmarks and no skip link, while PSI flags color contrast, heading order, and touch-target failures. The 390px capture also clips the Team carousel's next card at the right edge. Add semantic landmarks and a skip link, correct the heading and contrast findings, and verify keyboard access and carousel reachability.
Projecttile has a recognizable visual system, but mobile execution weakens the product surface. Rounded cards, pale-blue actions, pink emphasis, and a Poppins-led display treatment repeat across the workspace and pricing page; desktop layouts separate the generator, controls, timeline, and pricing cards clearly. The homepage reports 18 small interactive targets, including 30–32px header controls and a 316×36px generate button, while pricing reports 11, including 94×28px and 149×29px billing controls. The consent banner covers timeline and pricing content in the mobile captures. The homepage outline also has no H1 and jumps from H2 to H4. Raise target areas to at least 44px, reserve consent space, and repair the hierarchy.
Mobile performance is Projecttile's clearest measured speed constraint, while desktop is comparatively quick in the available lab data. Mobile LCP reaches 8.3–8.9 seconds across the homepage, pricing, and terms samples; desktop LCP is about 1.4–1.6 seconds. PSI estimates 1,500 ms of render-blocking savings on homepage and pricing mobile runs, plus 1,088–1,170 KiB of unused JavaScript. Network summaries show about 1.9 MB across 18 requests per sampled route. Tackle render-blocking work first, split non-critical workspace code, and right-size the 1,941×463 PNG logo rendered at 235×56. Field Core Web Vitals were unavailable, so validate after release with field monitoring.
Projecttile's strongest writing explains a real scheduling interaction, but the public homepage does not expose that product story in crawlable copy. The homepage contains 41 extracted words, no H1, and only the consent message, while the about page gives concrete language such as a lounge-chair upholstery timeline and downstream rescheduling after a task moves. Generic openings—Lightning fast!, Super simple!, and With a classy aesthetic!—are less distinctive than the later mechanics. The pricing page contains 137 words and makes the plan boundaries implicit. Across seven sampled routes, the same title and 209-character meta description repeat. Put the product promise and audience on the homepage, replace generic slogans with demonstrated mechanics, and give routes intent-specific metadata.
Projecttile's pricing page makes plan comparison easy to scan, but it does not explain the recommendation behind its highlighted plan. Three cards show monthly prices, a monthly/yearly toggle, and audience cues: Free for one project, Sole for freelancers with more than one client project, and Team for sharing with teammates. The desktop screenshot marks Sole as Most popular without stating why it is the default or when Free or Team is the better choice. The stacked mobile cards are readable, but the consent panel covers the transition between Free and Sole. Add a one-line chooser above the cards, explain the Sole recommendation and Team trade-off, and keep consent from obscuring plan content.
Projecttile's principal stability risks are indexability signals and mobile delivery, not a measured traffic decline. RDAP records the domain registration on 17 July 2026, and Wayback returned no CDX rows, so this is a new-site assessment without a reliable history. The sitemap lists pricing, about, terms, and privacy, yet all four canonicalize to the homepage. A guaranteed-nonexistent path also returns the application page with HTTP 200. Mobile LCP reaches 8.3 seconds on the homepage and 8.9 seconds on pricing, with more than 1 MiB of unused JavaScript on each. Set self-referencing canonicals, return a real 404, reduce mobile delivery cost, then connect GSC and analytics before making traffic claims.
Projecttile's sampled marketing and legal surface is deliberately written, but its search-facing editorial hygiene is not ready for publication at scale. The about page explains a 3–12-task AI planning example, while privacy and terms name data practices and third parties; internal anchors such as pricing, get started, terms & conditions, and privacy policy are descriptive. Against that, all seven sampled routes share one title and meta description, and non-home canonicals point to the root. The homepage has no H1 and only 41 extracted words. This is a seven-page marketing-surface result, not a corpus-wide editorial judgment: no blog, guide, resource, or article set was supplied. Assign route-specific metadata and rerun QA with any future editorial URLs.
An llms.txt endpoint returns status 200, but its body was not supplied for evaluation. Publish a quickstart, task-based guides, and an FAQ; link Help or Documentation from primary navigation or the footer, then point llms.txt to canonical pages.
Projecttile is crawlable and server-rendered, but canonical consolidation and an unknown-path 200 response are the main technical SEO fixes. Robots.txt allows crawling and declares the sitemap; the verified sitemap contains five URLs, HTTPS redirects in one hop, and the sampled graph has no orphans, maximum depth 2, and 33 internal edges. The four public sitemap pages pricing, about, terms, and privacy canonicalize to the homepage, while a guaranteed-nonexistent URL returns the application page with status 200. The homepage also records 8,276.5 ms mobile LCP, and pricing 8,856 ms. Set self-canonicals, establish a slash policy, return real 404s, and reduce mobile JavaScript and render-blocking work.
Projecttile is a sensible fit for freelancers, small teams, and personal-project planners who want a lightweight schedule that responds when dependencies move. Its strongest case is the combination of a specific Gantt workflow, cascading-dependency promise, visible timeline UI, and clear product writing.
Three fixes would materially improve the experience: add a public docs or self-serve-help path, reduce the 8.3–8.9-second mobile LCP range, and refine the visual system behind the 52/100 design-execution score. Technical SEO also needs attention where public pages canonicalize to the homepage and a 200 soft 404 can weaken indexability.
The core product is easy to recognize and evaluate. It is not yet equally strong at supporting a buyer after that first recognition moment.
This 13-dimension review is based on a seven-page crawl completed on 2026-10-18, product facts identified from homepage JSON-LD, the supplied public dimension score table, available lab performance data, and technical checks across the crawled surface. The crawl identified Projecttile as a web-based AI-powered Gantt timeline tool with cascading task dependencies.
The review excludes 13 · Review-content integrity, marked not_applicable. Google Search Console was not connected and access was unavailable, so this frame does not make Search Console claims. The pricing model and exact price range remain unknown in the supplied site facts, although the pricing page presents a three-plan comparison with a monthly/yearly toggle.
Read How SiteList scores for the review method and dimension definitions.
Projecttile is a web-based AI-powered Gantt timeline tool. It supports cascading task dependencies, milestone tracking, and timeline generation from plain English.
The supplied profile positions Projecttile for freelancers, small teams, and personal-project planners who need a lightweight schedule that updates when dependencies move.
The supplied site facts do not establish a single pricing model or overall price range; the pricing page visibly shows Free at $0/month, Sole at $3/month, and Team at $8/month, with a monthly/yearly toggle.
Mobile LCP measured 8.3–8.9 seconds across the homepage, pricing, and terms samples. Desktop LCP was about 1.4–1.6 seconds in the available lab data.
The supplied crawl records an llms.txt endpoint with status 200 and text/plain content type. Its body was not supplied for evaluation.