Figma is hiring a Brand Designer to up-level its marketing websites "while staying accessible and performant". Today the homepage fails Google's Core Web Vitals for real visitors: the main content takes 3.8 s to appear and taps take 480 ms to respond. In the lab it downloads about 10 MB in 233 requests, 6.2 MB of it from the Vimeo player loading on first view, and the hero image is a CSS background inside a block that is rendered in the browser, so the browser cannot start fetching it until the JavaScript runs. Of the 1.8 MB of HTML, about 1.5 MB is inline page data.
First action
Swap the hero background for a prioritized <img> and lazy-load the first video, then re-run PageSpeed.
How to measure it
Homepage field LCP
- Now
- –
- Target
- Under 2.5 s
- By
- 60 days
Steps
Baseline
Field LCP and INP for the homepage and the top 20 campaign pages.
Web engineering lead 1 day
Hero as an image
Server-render the hero; <img> with fetchpriority=high and the right sizes.
Web engineering lead 3 days
Videos on demand
Poster frame first; load the Vimeo player on scroll or play.
Web engineering lead 3 days
Trim page data
Send only what the first screen needs; defer the rest.
Web engineering lead 1 week
Delay ad tags
Load marketing tags after the first interaction.
Marketing Engineer, AI Deployment 2 days
Set budgets
Size and request limits per section in the web design system.
Brand Designer, Web 1 week
Guard in the build
Fail or flag any page that goes over budget.
Web engineering lead 1 week
Measure
Sign-up rate from the homepage before and after.
VP of Growth Marketing 4 weeks
Why it works
Server-render the hero and serve its image as a normal <img> with high fetch priority. Show a poster frame for each video and load the Vimeo player only when the visitor scrolls to it or presses play. Trim the inline page data to what the first screen needs, and move ad tags after the first interaction. Write the limits into the web design system the new designer will own: a size budget per section and per page, and a check in the build that flags any page over it.
Most visitors decide within a few seconds whether to click "Get started for free". A faster first screen lifts sign-ups on the most-visited page and every campaign page built from the same components, and it shows performance as part of the craft the brand stands for.
Ready to use
ChecklistHomepage speed list
[ ] Hero rendered on the server [ ] Hero image as <img fetchpriority="high"> [ ] Poster frames for every video; player loads on scroll or play [ ] Inline page data cut to the first screen [ ] Ad and analytics tags after first interaction [ ] Size budget per section in the web design system [ ] Build check for pages over budget [ ] Field LCP under 2.5 s and INP under 200 ms in the Chrome UX Report
Risks and how to handle them
Videos lose impact as posters
Use animated posters (short, compressed loops) for the hero only.
Ad attribution drops
Keep conversion tags, delay the rest, and compare attributed sign-ups.
Evidence
- HiringBrand Designer, Web (posted October 8, 2026): the role will "up-level some of our most important surfaces—our marketing websites", "Design brand-forward web experiences for launches, campaigns, and events that feel novel and unexpected, while staying accessible and performant", "Evolve and contribute to our web design system, including templates and components", and use "research and data to run experiments and drive decisions".Source
- Google PageSpeed (Chrome UX Report)Real Chrome visitors to the figma.com homepage (28-day field data): 75th-percentile Largest Contentful Paint 3.8 s (good is 2.5 s or less) and Interaction to Next Paint 480 ms (good is 200 ms or less), so the homepage fails Core Web Vitals; layout shift is fine (0). Across the whole origin, which includes the app, LCP is 8.4 s.Source
- Google PageSpeedGoogle PageSpeed mobile lab test of the homepage (October 21, 2026): performance score 35-38; the page downloads 9.3-10.1 MB in 233 requests, including 5.4 MB of JavaScript (2.7 MB unused); third parties account for 7.7 MB from 26 hosts, of which the Vimeo player is 6.2 MB in 90 requests; Google Tag Manager blocks the main thread for about 0.6 s.Source
- Your websiteHomepage HTML (checked October 21, 2026): 1.8 MB, of which about 1.5 MB is inline page data; the hero image is a CSS background inside a block that is rendered in the browser rather than on the server; H1 "The full-stack creative canvas"; the menu describes Figma Sites (beta) as "Publish fully responsive websites" and links "Friends of Figma" user groups; the proof point "95% of the Fortune 500 uses Figma" is footnoted "Based on data from March 2025".Source