Storylist earns 65/100 (rounded from 64.9) for a clear proposition and exceptional design execution, with design execution scoring 94/100. Based on 8 crawled pages, its most material weaknesses are four navigation paths returning 404, a 5.5-second mobile load, and thin, repetitive homepage copy.
Reviewed by SiteList Engine · 10 of 13 dimensions · published Reviewed on September 28, 2026
Is this your site?
Claim itStorylist is a free SaaS marketing site for project management aimed at non-technical founders.
| Field | Value |
|---|---|
| Domain | storylist.dev |
| Category | Project management for non-tech founders |
| Pricing | Free; price range 0–0 USD |
| Pages crawled | 8 |
| Crawl date | 2026-09-28 |
Based on a crawl of 8 pages, Storylist has a clear audience and an unusually strong visual system, but the public experience is undermined by broken commercial paths and weak content structure. First impressions score 74/100 and audience messaging 68/100 because the proposition is specific, while proof points such as customer logos are limited. Design execution leads the table at 94/100; accessibility is also strong at 85/100.
The main constraints are functional and editorial. Usability scores 65/100 because /features, /pricing, /use-cases, and /blog return HTTP 404. Performance scores 58/100: the homepage takes 5.5 seconds to load its main content on mobile against Google's 2.5-second bar, with an oversized hero image identified as the biggest cause. Writing quality scores 32/100, with a 383-word paragraph, duplicated bullets, and generic, repetitive copy. Editorial QA is 28/100, while technical SEO is 65/100.
Storylist presents a clear proposition for non-tech founders who need to communicate project ideas to development teams. The audience signal is specific: the Use Cases section names ‘Non Tech Founder’, and the copy says the platform helps non-tech founders share their vision with developers. The commercial case is less developed. No named customer logos or case studies were found, and the pricing page returns 404, leaving a key buying question unresolved. Add named testimonials with roles and companies, publish a working pricing page, and use the site’s niche positioning consistently across the supporting pages.
Storylist names a credible audience, but its messaging does not yet answer the practical questions that move a visitor forward. The phrase ‘non-tech founders’ gives the homepage a defined segment, while ‘Get started free’ supplies a direct entry point. Cost remains only partly answered: the pricing page is a 404, despite references to ‘Free’ and ‘Hobby’ plans. Trust is also lightly supported; the crawl found no testimonials. Add a visible pricing table, a short getting-started sequence, and proof with names, roles, and companies. Replace self-oriented phrasing with direct statements of what the visitor can accomplish.
The homepage is visually compelling, but the core journey stops at broken destinations. The pricing, features, use-cases, and blog paths return HTTP 404, so visitors cannot review cost, capabilities, scenarios, or ongoing content. The ‘Get started free’ CTA points to /dashboard, which also resolves to a 404, making the stated conversion path unusable. The problem is structural rather than cosmetic: restore the four content routes and provide a working signup or dashboard entry point. If a page has moved, use a precise redirect and verify every navigation and CTA destination on mobile and desktop.
Storylist’s accessibility foundation is strong at 85/100, with no P0 failures, but several modest gaps make navigation and feedback less reliable for assistive-technology users. The homepage has no skip link and lacks main and footer landmarks, increasing the effort needed to move through the page. Links and form errors also rely on color-only cues, while the existing aria-live attribute is not applied to dynamic elements. Add a Skip to content link, complete the landmark structure, distinguish links beyond color, and ensure dynamic error updates are announced to assistive technologies. Keep the four empty alt attributes only where the images are genuinely decorative.
Design execution is Storylist’s clearest strength at 94/100. The interface uses CSS custom properties for colors, fonts, spacing, and radii, producing a consistent visual system rather than a collection of unrelated components. The crawl found one H1 per page, no skipped heading levels, a single primary hero CTA, consistent button and card treatment, visible focus states, and no horizontal scroll on mobile. The remaining issues are narrow contrast drifts: hero and pricing text measure 4.2:1 against white, and primary button text measures 2.8:1 against the brand background. Darken those combinations while preserving the established system.
Storylist’s homepage takes 5.5 seconds to load its main content on mobile, more than twice the 2.5-second bar cited in the draft. The LCP is the hero image: it is served at 2048px natural width while rendered at 1216px, with a 99.8KB file and no preload or fetchpriority attribute. The network log also records 16 blocking requests, including client.crisp.chat at 386KB, and PSI reports 271KB of unused CSS. Resize the hero asset or provide an appropriate srcset, prioritize it when above the fold, and defer non-critical third-party scripts and unused styles.
Writing quality is constrained by structure and repetition: the homepage contains one 383-word paragraph, duplicated bullets, and a generic vocabulary that obscures the product’s concrete value. ‘Effortlessly’ appears 3 times and ‘seamlessly’ twice; the same bullets reappear under ‘Simplify project collaboration and development goals’. The audience tags also run together as ‘non tech foundersolopreneurfreelance developer’. Break the wall of text into 5–7 focused paragraphs, replace duplicated bullets with distinct benefits, and use direct actions such as generating user stories only where those claims are already supported by the draft. Finish with a clear next step.
The main stability risk is discoverability: four important paths return 404, while the HTTP-to-HTTPS route takes two hops before reaching the www hostname. The crawl also found no XML sitemap and no abrupt historical collapse: Wayback data contains 27 samples across 2023–2026. That combination points to a structurally active site with fixable traffic exposure, not a disappearing domain. Restore or precisely redirect /features, /pricing, /use-cases, and /blog; consolidate the redirect chain to one hop; and generate an XML sitemap. Add the supported Organization schema only after the core routes are live so the markup describes durable destinations.
Editorial QA scores 28/100 because the published copy shows repetition, generic language, and missing content routes. The clearest process defect is the identical bullet set under ‘Simplify project collaboration’ and the preceding section. The homepage also uses ‘effortlessly’ 3 times, ‘seamlessly’ 2 times, and the reviewed copy contains no concrete examples and uses no supporting numbers. Four images lack alt text, and the text includes a space before the comma in ‘With Storylist ,’. Establish a pre-publish pass for duplicated blocks, punctuation, image alternatives, and claims; then rewrite around specific features, use cases, and benefits. Treat the 404 pages as a separate launch gate.
Technical SEO is functional in rendering but weakened by indexability and routing defects, scoring 65/100. The four navigation paths /features, /pricing, /use-cases, and /blog return 404, while HTTP to the canonical www HTTPS URL takes two hops. /robots.txt returns a Next.js 404 HTML page rather than plain-text directives, and /sitemap.xml is absent. Rendering parity is the counterweight: raw and rendered text match at 1:0 across crawled pages, TLS 1.3 is valid, and HSTS is enforced with max-age=63072000. Restore or redirect the broken routes, serve valid robots.txt and sitemap.xml files, and collapse the redirect chain.
Storylist is best suited to non-technical founders who want to manage projects with their development teams. The product promise is legible, but the broken conversion path prevents reliable evaluation or signup.
Its strongest asset is the interface work: design execution scores 94/100 and accessibility scores 85/100.
The buying path needs three direct fixes. Restore the four navigation paths that return HTTP 404, reduce the homepage's 5.5-second mobile load toward Google's 2.5-second bar, and replace the 383-word wall of text and duplicated bullets with specific, edited copy. These changes address the clearest functional, performance, and editorial weaknesses without changing the site's defined audience.
This 13-dimension review combines a crawl of 8 pages on 2026-09-28 with the public dimension score table and its one-line findings. It covers the 13 applicable dimensions in the SiteList framework.
Dimensions 12 · Decision-support surfaces and 13 · Review-content integrity were not applicable. Google Search Console was not connected and access was unavailable, so no Search Console enrichment is included. Read How SiteList scores for the scoring method and data notes.
Storylist targets non-technical founders who want to manage projects with their development teams.
The homepage takes 5.5 seconds to load its main content on mobile, compared with Google's 2.5-second bar.
The crawl found four dead navigation paths: /features, /pricing, /use-cases, and /blog. Each returns HTTP 404.
Restore the four dead navigation paths, reduce the homepage's 5.5-second mobile load, and replace the 383-word wall of text and duplicated bullets with specific, shorter copy.