Data Collection Specialist for GovXRay.com

Listing 1 — Technical Audit TITLE: Senior web architecture & performance review — static SvelteKit site, fixed price $350, one week WHAT THIS IS A one-time, fixed-scope expert review. No long-term commitment, no meetings, everything written and async. You audit, you write a memo, you answer one round of follow-up questions. Done. THE PROJECT GovXRay.com is a public-interest, non-commercial site comparing the total per-capita cost of government (all levels combined) across 243 world metros. Current production is a Python/Dash app being replaced by a static SvelteKit site (adapter-static, 243 pre-rendered pages) served by nginx on a single EC2 instance, with Cloudflare planned in front. The site must survive viral traffic spikes (front-page-of-Reddit scale) on a hobby budget, and navigation must feel instant. Implementation capacity is not the bottleneck — judgment is. Your recommendations will be implemented; this is not a report that goes in a drawer. WHAT YOU GET ACCESS TO Read access to the private GitHub repo (SvelteKit frontend, FastAPI build-time backend, Python data pipeline, CI workflows, nginx config, deploy scripts), a 9 MB sample database, and the live site. No server access needed or given. SCOPE — WHAT YOUR MEMO MUST COVER (6-8 hours of your time) Traffic resilience: what breaks first under a 100x traffic spike in the current setup (single EC2 + nginx + static files), and the cheapest fix ranked by effort. Cloudflare free-tier configuration recommendations (cache rules, TTLs, what to bypass). Frontend performance: review the built output of the SvelteKit site (bundle composition, per-page JSON payloads, render path). The 5 highest-impact changes to get LCP under 1.5s on mid-range mobile. Architecture sanity: the repo mixes a legacy Python monolith, a data pipeline, and the new static site. Is the build/deploy chain sound? What is over-engineered, what is under-engineered, what is a time bomb? Be blunt. Delivery and caching: precompression, cache headers, asset hashing, cache busting on deploy — what is missing or wrong in the current nginx setup (config file provided in repo). Security quick pass (not a pentest): anything alarming visible in the repo or headers. DELIVERABLE A written memo (3-6 pages, English, markdown): findings + a prioritized top-10 recommendation list, each item with expected impact, rough effort, and concrete implementation notes (exact config snippets where relevant). Plus one written round of follow-up Q&A within the following week. TIMELINE AND PAYMENT Fixed price $350, one milestone, memo due within 7 days of getting repo access. TO APPLY (answer all 3 — applications without answers are ignored) Describe a traffic spike you personally survived or failed: what broke and what you changed. For a fully static 243-page site behind Cloudflare free tier, what is left to break under load? Name the two things you would check first. One link to a production site you influenced with measurably good Core Web Vitals, and your role.