Internal Review — Socialgist Web Team
To fix the current site's poor scannability caused by its heavy reliance on scroll animations, there's also work in progress directly in Webflow — Webflow Staging Site below is a snapshot of that in-progress work. Alongside it, we've also prepared three redesign options (A/B/C) — each with all animation removed and the tracking tags (GA4 / GTM / Salesforce Pardot) fully migrated. A/B/C have each been updated since they were first shared; Option C was most recently updated to a new version on 2026-08-05. Start with the snapshot of the current site as your baseline, then compare each option against it.
11-axis rubric (axes 1–10 at 1–5 each, 50 total; axis 11 “response speed” added this pass, 1–5). Every cell re-checked live — desktop 1440px and mobile 390px via a real browser with a real viewport (not a resized window), plus network timing via curl. Highest score per axis in orange.
| Axis | Current | Staging | A | B | C |
|---|---|---|---|---|---|
| 1. 5-second test | 1 | 2 | 2 | 4 | 5 |
| 2. Value proposition clarity | 2 | 1 | 2 | 4 | 5 |
| 3. Social proof | 1 | 4 | 2 | 5 | 5 |
| 4. CTA strategy | 2 | 4 | 4 | 4 | 5 |
| 5. Scannability | 1 | 4 | 2 | 4 | 4 |
| 6. Evidence concreteness | 1 | 3 | 4 | 4 | 5 |
| 7. Use-case / "what can I build" | 1 | 2 | 2 | 4 | 5 |
| 8. Information architecture / flow | 2 | 3 | 4 | 4 | 5 |
| 9. Visual hierarchy & credibility | 2 | 1 | 3 | 4 | 5 |
| 10. Mobile experience | 1 | 1 | 3 | 4 | 4 |
| Subtotal / 50 | 14 | 25 | 28 | 41 | 48 |
| 11. Response speed (time to visible content) | 1 | 3 | 4 | 4 | 4 |
| Total / 55 | 15 | 28 | 32 | 45 | 52 |
Ranking: C (52) > B (45) > A (32) > Staging (28) > current (15). A moved up (25→32) mainly from the stats band and feature-copy update it now shares with B/C. Staging moved because this pass found real, previously-untested problems (see below) — not because anything on Staging got worse.
Axis 11 methodology: curl timing (3 runs, cache-disabled, network layer only — the initial HTML document, not full asset-inclusive paint) against socialgist-gules.vercel.app: current avg TTFB 138ms / 68KB, Staging 158ms / 54KB, A 147ms / 33KB, B 137ms / 37KB, C 138ms / 36KB. Raw TTFB is within noise across Staging/A/B/C. The score instead reflects two things this number alone doesn't show: whether visible content depends on a separate external script (current only — the core problem this whole project exists to fix), and document weight (Staging is heaviest of the redesigned options). To compare against a real production baseline once it exists, re-run this same check against staging.socialgist.ai.
Why the Webflow Staging Site can't ship as-is (found in this pass, live browser, both viewports):
Snapshot of the live site as-is (animations included). The baseline for comparison. Homepage only — sub-page links connect to the production site.
View → 02Snapshot of the animation-removal work in progress directly in Webflow, taken from the staging site. Kept verbatim, including any in-progress typos. Homepage only — sub-page links connect to the production site.
View → 03The current structure kept intact, with only the animation removed. Homepage plus all sub-pages migrated.
View → 04Every message compressed into about 3.6 screens, prioritizing scannability above all. Homepage plus all sub-pages migrated.
View → 05 RecommendedUpdated 2026-08-05: repositioned as data infrastructure for AI products, intelligence platforms and risk/social-listening solutions (not a finished analytics tool) — corrected proof metrics, compact B-style value/use-case cards, plus new delivery-methods and trust sections. Homepage only; sub-pages not yet updated to match.
View →