Mobile Experience

Making a site “responsive” and making it genuinely mobile-friendly are two very different things. Here’s what the gap actually costs you – and how to close it.

The uncomfortable truth about “responsive” design

Most park district sites are built desktop-first and then made to reflow on small screens. That is not mobile-first design. Real mobile-first means the phone experience is the primary design constraint – not an afterthought.

  • 68% of residents use mobile to access your site
  • <3s load time needed to keep mobile users engaged
  • 5 taps max from homepage to completed registration

When a resident can’t find a program or complete a registration on their phone, they don’t call back later on a desktop. They just don’t register. That lost participation is quiet, invisible, and entirely preventable.

What actually needs to change – in order of impact

1. Rethink navigation from scratch (Highest impact)

Deep menu trees (Programs > Youth > Summer > Session 2) are unusable on a phone. Reduce top-level nav to 4-5 items max. Make a persistent search bar the primary discovery mechanism – mobile users search more than they browse. Put the three most-used actions one tap from the homepage.

Target actions to surface: Register, Find a facility, Upcoming events

2. Fix performance before anything else (Highest impact)

A slow site on mobile kills everything else you get right. Target under 3 seconds to first meaningful content on a 4G connection. The usual culprits: uncompressed program photos, heavy PDF embeds, and poorly-optimized third-party registration widgets. Run Google PageSpeed Insights – it’s free and gives specific, actionable fixes.

Quick win: compress images. Park district sites routinely serve 3-5MB images where 200KB would be identical on screen.

3. Make registration actually work on a phone (High impact)

Registration is the most important conversion on a parks site, and most forms are broken on mobile. Input fields should auto-trigger the right keyboard (numeric for phone numbers, email keyboard for email fields). Multi-step forms must save progress – a phone call mid-form should not lose everything. No horizontal scrolling, no pinch-to-zoom required.

Test tip: Test your registration form cold, on a real device, without knowing the answers. That’s what a first-time resident experiences.

4. Fix touch targets – they’re probably too small (Medium impact)

Every tappable element needs to be at least 44x44px to be reliably hit by a finger. This sounds minor but causes constant frustration. Small “Register” links, cramped facility listings, and tiny calendar event dots all fail this test on most park sites. One misfire and a resident gives up.

Check: buttons, nav links, calendar items, and inline links inside paragraphs.

5. Restructure content hierarchy for scanners (Medium impact)

Mobile users scan aggressively – they don’t read. Lead with what matters: date, time, cost, how to register. Not a paragraph of program description. Most park district program pages bury the practical details below long marketing copy. Invert that structure on mobile.

Rule: If the “Register Now” button isn’t visible without scrolling on a phone, it’s in the wrong place.

6. Test on a real device – not browser dev tools (Ongoing)

Browser developer tools give an approximation. A real phone in a real hand tells you the truth. The tap targets that seem fine on a desktop simulator are frustrating on glass. The load time that looks acceptable on a fast office Wi-Fi is brutal on 4G. There is no substitute.

Tip: Test on the cheapest Android device you can find – that’s often the device your most underserved residents are using.

Do this right now, on your actual phone

  • Go to your homepage. How many taps to find a program? More than 3 is a problem.
  • Type “swimming lessons” in the search bar. Do the results make sense? No results or irrelevant pages means your search is broken.
  • Try to start a registration. Does the form work without pinching or horizontal scrolling?
  • Check your mobile page speed at pagespeed.web.dev – anything below 50 on mobile is hurting you.
  • Count total taps from homepage to a completed registration. If it’s more than 5, you have a fixable problem.

The gap between responsive and mobile-first

Responsive-only (most sites)
  • Desktop layout squeezed to fit small screen
  • Navigation collapses into a hamburger – still 4 levels deep
  • Registration form requires pinch-to-zoom
  • Program description leads – date and cost buried below
  • Slow load times because images aren’t optimized
Mobile-first (what it should be)
  • Search bar front and center – residents find, not browse
  • Max 4 top-level nav items, most common actions one tap away
  • Forms optimized for thumb input, progress saved automatically
  • Date, cost, and register button above the fold on every program page
  • Under 3 seconds load time on a 4G connection

Not sure where your site stands?

SmartRoots offers a free mobile audit – a practical breakdown of exactly where your site is losing residents on mobile, and what to fix first.

No cost. No commitment. Results you can actually act on.