Vibeshots
← Sites

Razorpay Sprint 26

razorpay.com
Razorpay Sprint 26 website, live site

Live capture at 1440px, 2026-10-24

How it’s built

Layout
A tall event page begins with a saturated blue hero showing a large white wireframe architectural structure in extreme perspective and a dark hanging event panel. A pill-shaped scroll invitation overlays the lower hero. Beneath it, a thin segmented topic bar precedes a huge event title at left and compact introduction at right; a mosaic of interface/product images begins below.
Type
Large light sans event title, small uppercase segmented labels, compact sentence-case introduction and tracked pill text. Exact faces and metrics unknown.
Color and surface
Bright blue hero, white wireframe structure, black and dark-gray panels below, white type, colorful product thumbnails.
Components
Perspective hero imagery, overlay scroll cue, segmented topic navigation, asymmetric title/introduction row, lower image mosaic.

What makes it work

  • Perspective-led hero
  • Topic strip between hero and intro
  • Asymmetric title/summary row leading to a varied image mosaic
On a new subjectFor a regional public-health summit, use a dramatic perspective image of an abstract civic structure, then a narrow topic strip, a large summit title paired with a concise summary, and a varied mosaic of program and community images. Replace payment and technology content with accurate health-program information.

Measured

Fonts loadedInter_tight, Geist_mono, Tasa_Regular, Tasa
H148px / 500 / -0.9px
Body text20px
Page background#1a1a1a
Text color#ffffff
Page height1,000px

Computed CSS at 1440px, 2026-10-24.

Live behavior

Today
Electric blue full-screen scene with white wireframe-like figure and floating black graphic panels, small corner identity and dark rounded scroll prompt. Type is spare white sans; visual scene dominates.
Responsive
Tablet and phone show a much tighter crop of the scene with corner identity and bottom prompt.
Scroll
Desktop t0 shows a black loading overlay; t2 shows the blue scene. Scroll frame shows a different view, but compare reported scroll position before attributing change to scroll. No hover state saved. Fresh reduced-motion phone frame remains in loading phase, so no preference conclusion.

More like this