Meteor Crater · Homepage refresh ·

Panorama + Discovery

View options

Pair panoramic discovery with a clear path to planning a visit and buying tickets.

● ● ●DESKTOP · 1200 × 820Scroll inside the page ↓

Explore the homepage using the numbered discovery points, navigation, and visit details. Use the presentation controls to switch between Desktop and Mobile. Grayscale illustrations represent future photography and media.

A clearer invitation to discover Meteor Crater

The problem we’re solving

The homepage needs to turn curiosity about the crater into a confident decision to visit. The refresh must preserve its sense of wonder and interactive discovery while making the experience, essential visitor information, and ticket path clear—especially on mobile.

70.92%

of sessions started on the homepage

44,913 of 63,331 sessions
56.34%

of active users were on mobile

Sitewide device mix
7,876

Visitor Info pageviews

Second in the page-title report

GA4 · September 22–October 19, 2026 · Previously reviewed reports. Mobile share is sitewide; these figures guide priorities rather than prove the proposed design will improve conversion.

Put the crater first.

Establish the destination and its appeal immediately, with a clear invitation to explore or buy tickets.

Keep visit essentials close.

Preserve persistent ticket, visitor-information, and phone access on mobile, with hours and ticket messaging on desktop.

Invite exploration.

Let visitors discover the crater and meteorite story at their own pace, with a clear route back to planning a visit.

Design decisions behind the wireframe
01 · Evidence → priorityMake the opening a complete invitation.

70.92% of sessions started on the homepage. Context, a purchase route, and optional discovery are available immediately. No animation must finish first.

02 · Evidence → device emphasisUse the mobile action bar we already have.

Mobile represents 56.34% of active users and 71.77% of recorded revenue, sitewide. Tickets remains the bar’s primary action; Visitor Info and Call Us keep their places. No extra floating ticket control.

03 · Evidence → useful contentGive planning questions a clear route.

Visitor Info recorded 7,876 views, second in the page-title report. A compact planning section answers key questions without duplicating the desktop sticky hours/ticket strip.

04 · Hypothesis to validateShow the visit before promoting the calendar.

Experiences now precede events. This is a content-priority hypothesis, not a GA4-proven sequence. Test whether visitors understand what they can do and find admission details.

05 · Confirmed requirement → interactionKeep discovery optional and tangible.

Both current hotspot modules are retained. Mobile pairs image markers with labeled controls and inline detail. No explicit hotspot event names were found; existing usage is not established.

06 · Measurement limitDon’t call this a proven conversion uplift.

Homepage engagement was 10s per active user; this is not exit time. 991 purchase events across 269 users needs reconciliation. The 0.9% homepage-entry key-event rate is not purchase conversion.

GA4 baseline: September 22–October 19, 2026 · All Users · previously inspected reports. No fresh analytics pull. Device metrics are sitewide; recorded revenue is subject to tracking validation.

Screen inventory, interaction rules, and non-happy states
Region / calloutPurpose + primary actionStates and handoff rules
01 · Hero + crater discoveryExplain the destination; Buy Tickets on desktop / mobile persistent bar. Explore is secondary.Default and one expanded point; Close restores trigger focus. Marker and labeled control are equivalent. Media failure preserves text and labeled discovery; no timeline or image-load gate.
02 · Persistent controlsMobile: Buy Tickets / Visitor Info / Call Us. Desktop: hours, location, ticket message.Fixed to the review viewport; content and scroll clearance reserved. Menu remains in page flow. Phone and ticket routes are review handoffs; exact phone and redirects need verification.
03 · Experience cardsPreview actual attractions; follow an attraction link.Static editorial cards, no carousel dependence. Missing image retains title/description/link. Final admission inclusions and availability need content-owner approval.
04 · Visit planningAnswer admission/location/access questions; Visitor Info.Native disclosure, closed/open states; ordinary Back on destination navigation. Unknown hours/status must not become invented “open now” messaging.
05 · Meteorite storyInvite learning through approved history.Same disclosure pattern, distinct content and measurement section. Essential context always visible. No requirement to finish a narrative to buy.
06 · Events + proof + closingSupport a visit with timely reasons and credible proof; closing Buy Tickets.Editorial samples, not an approved feed. Successful zero events omits module; simulated failure offers local Retry. Existing recognition is shown as labeled placeholders, without invented ratings/testimonials.

Event failure is conditional on a client-fetched implementation. If WordPress renders the collection server-side, use an editorial fallback instead of introducing a fetch merely to implement a loader. No first-use/onboarding or search-empty state applies here.

What is decided, what remains open, and what to test
  • Selected: Panorama + Discovery; WordPress retained; Slider Revolution replaced; existing mobile/desktop sticky roles preserved.
  • Candidate: headline/copy, section ordering, simplified nav grouping, marker count/positions, inline disclosure treatment, and card selection. Drawings are placeholders. Actual content inventory determines the final points.
  • Content owner: confirm hours, ticket validity, current tour notice, phone number, attraction availability/inclusions, event dates, recognition rights and historical copy before production.
  • Implementer: validate theme/editor and shared script dependencies; prototype real media crops, marker alignment, keyboard/Back behavior, safe areas, consent collisions and sticky clearance in WordPress.
  • Analyst: reconcile purchase/transaction IDs and existing generic-click parameters, then instrument placement-aware ticket/visit/call actions and distinct crater/meteorite engagement.
  • Review tasks: identify the place after five seconds; find tickets without exploring; open and dismiss each story; find visitor information; open menu without losing purchase access; repeat with long text, reduced motion, media failure and a short mobile viewport.

This prototype validates structure and state logic, not real imagery, perceived wonder, production motion, a payment system, or field performance. User testing and the WordPress interaction slice remain next.