Mobile Website Redesign Guide

A mobile website redesign matters more than most teams realize at the start of a project.

Mobile devices now account for over 60% of all global web traffic, yet most website redesigns still start with a desktop layout and shrink it to mobile as an afterthought, producing an experience that frustrates the majority of visitors from day one.

The sites that perform best across devices start from the smallest screen and build up.

This approach is not just a technical preference, it is a design philosophy that produces better results at every screen size, because the constraints of mobile force the prioritization that makes every interface cleaner and more effective.

Key Takeaways

• Mobile-First Is a Methodology: Starting design at the smallest screen forces content prioritization decisions that produce better desktop designs, not just better mobile ones.
• Performance Is Non-Negotiable: Page load time directly impacts bounce rate and conversion rate on mobile devices; Core Web Vitals are business metrics, not just technical benchmarks.
• Touch Requires Different Decisions: Tap targets, gesture navigation, and thumb zones require explicit design consideration that desktop-first design never demands.
• Google Indexes Mobile-First: Google's primary crawl is the mobile version of your site; a mobile experience inferior to desktop will measurably harm organic search rankings.
• Mobile SEO and UX Are Inseparable: The technical and experiential factors that make a mobile site rank well and convert well are largely the same set of requirements.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

The Mobile-First Design Methodology

Mobile-first design is not simply a matter of responsive CSS or flexible layouts. It is a design philosophy that changes the sequence of decisions and produces qualitatively different results.

Teams that adopt mobile-first methodology consistently report that it improves their desktop designs as a downstream effect, because the discipline of designing for constraints produces better thinking than designing for abundance.

What Mobile-First Design Actually Means

Mobile-first methodology means designing for the smallest screen first, then progressively enhancing for larger screens. This is the opposite of the traditional approach of designing for desktop and then adapting for mobile.

• Content Hierarchy Starts at 360px: Every content decision begins with the question "what is essential at the smallest viewport?", producing radically better prioritization at every size.
• Navigation Decisions Are Made for Constraints: Designing navigation for a 360px screen forces choices about information architecture that desktop-first design never requires.
• Performance Becomes a Design Constraint: Mobile-first designers must consider page weight from the first wireframe; desktop-first designers typically encounter performance problems only after the design is built.
• Progressive Enhancement Adds Complexity Intentionally: Features, columns, animations, and sidebar content are added as screen space increases, each addition must justify its place rather than being included by default.

The fundamental difference between mobile-first and desktop-first is not technical. It is the sequence of design decisions, and sequence determines outcomes.

Content Prioritization for Small Screens

Designing for mobile forces the question "what content is essential enough to show in 360 pixels of width?", and that discipline creates cleaner, more focused designs at all screen sizes.

• Only Essential Content Survives Mobile-First Scoping: Sidebars, secondary calls to action, and decorative content that survive desktop design rarely survive mobile-first prioritization.
• Heading Hierarchy Must Do More Work: Without visual hierarchy from multiple columns, typography must carry the information hierarchy, mobile-first design improves typographic thinking across the entire site.
• CTAs Become Unavoidable: When space is constrained, the call to action must be positioned deliberately rather than hoping it will be noticed among other visual elements.
• Content Decisions Become Strategic: Teams doing mobile-first design report that the process reveals how much low-value content has accumulated on desktop sites over years of addition without subtraction.

The best desktop sites are usually those designed mobile-first. The constraint is the source of the clarity.

Progressive Enhancement vs. Graceful Degradation

Progressive enhancement builds up from a mobile baseline, adding features as screen size increases.

Graceful degradation starts from a full desktop design and removes features for smaller screens. The former produces better mobile experiences in practice.

• Progressive Enhancement Guarantees Core Function: Every user on every device gets the core content and functionality; enhanced features are additions, not requirements.
• Graceful Degradation Produces Incomplete Mobile Experiences: When features are removed rather than avoided, mobile users receive a deliberately diminished version of what desktop users see.
• Enhancement Decisions Are Made at Scale: Deciding to add a feature at a larger breakpoint is easier to get right than deciding which features to remove from a complete design.
• Codebase Complexity Is Lower with Enhancement: Building up produces less conditional code and fewer breakpoint-specific overrides than stripping down, the codebase is simpler and more maintainable.

Teams that genuinely commit to progressive enhancement produce better mobile experiences than those who use the term while practicing graceful degradation.

Mobile UX Design Principles

Bringing a mobile UX design approach to a redesign means designing every interaction pattern explicitly for touch, not adapting mouse-based interaction patterns to a touchscreen.

Touch and mouse are fundamentally different input methods, and designs that treat them as equivalent fail mobile users at precisely the moments when they are most likely to complete a conversion.

Touch Target Sizing and Thumb Zones

WCAG and platform guidelines recommend a minimum tap target of 44x44px for all interactive elements. Smaller targets cause missed taps that frustrate users and increase interaction failure rates.

• Minimum 44px Height for All Buttons: Any interactive element a user is expected to tap, buttons, links, form elements, must meet minimum size requirements to prevent missed taps.
• Thumb Zones Define Comfortable Reach: The lower-center area of the screen is the most comfortable thumb reach zone; primary CTAs and navigation should be positioned in this zone when possible.
• Adequate Spacing Between Targets: Tap targets placed too close together cause accidental taps on the wrong element; minimum 8px spacing between adjacent interactive elements is a practical guideline.
• Bottom Navigation Is More Accessible Than Top Navigation: Bottom navigation bars that align with the natural thumb position are increasingly preferred for primary navigation in mobile-first applications.

Tap target sizing is the most frequently overlooked mobile UX requirement and one of the most frequently cited in automated accessibility audits. Get it right from the first design iteration.

Navigation Patterns for Mobile

The choice between hamburger menus, bottom navigation bars, tab bars, and priority-plus navigation patterns depends on site type, content volume, and how frequently different sections need to be accessed.

• Hamburger Menus Work for Low-Frequency Navigation: When users rarely switch between sections, a hamburger menu keeps the interface clean without penalizing navigation frequency.
• Bottom Navigation Works for High-Frequency Access: Apps and content-heavy sites where users frequently navigate between sections benefit from a persistent bottom navigation bar within thumb reach.
• Priority-Plus Navigation Solves Menu Depth Problems: For sites with many navigation items, showing the top five and collapsing the rest into a "more" button balances discoverability with simplicity.
• Navigation Must Be Consistent Across Pages: Inconsistent navigation placement between pages increases cognitive load; mobile navigation must be predictable regardless of which page the user is viewing.

Navigation decisions made for mobile determine the information architecture of the entire site. These decisions should be made before visual design begins.

Scroll vs. Tap: Mobile Interaction Patterns

Mobile users scroll rather than hover, and they tap rather than click. These behavioral differences require specific design adjustments that desktop-centric design teams often miss.

• Hover States Do Not Exist on Mobile: Any functionality revealed on desktop hover must be accessible by tap on mobile, tooltip content, dropdown menus, and hidden navigation items are common examples.
• Infinite Scroll Can Serve Content-Heavy Sites: For content browsing contexts, continuous scroll can outperform paginated navigation that requires tap navigation between pages.
• Sticky Elements Serve Mobile Scroll Patterns: Headers, CTAs, and key navigation elements that remain visible during scrolling provide persistent access without requiring users to scroll back to the top.
• Swipe Gestures Should Match Platform Expectations: Swipe navigation patterns should align with the native iOS and Android conventions users already know; custom swipe gestures that conflict with platform patterns create confusion.

Designing for mobile interaction patterns is not a technical constraint, it is a user behavior design challenge that requires research and testing with actual mobile users.

Mobile Performance and Core Web Vitals

Understanding page speed after a redesign starts with understanding that mobile performance is measured separately from desktop and consistently scores lower for most sites. This gap is a business problem, not just a technical metric.

Google's Core Web Vitals are the measurable expression of the mobile experience quality that affects both search rankings and conversion rates.

Understanding Core Web Vitals for Mobile

The three Core Web Vitals, Largest Contentful Paint, Cumulative Layout Shift, and Interaction to Next Paint, each have mobile-specific benchmarks that are measured using real user data from Chrome users on mobile devices.

• LCP Mobile Target Is Under 2.5 Seconds: The largest content element must render within 2.5 seconds on mobile; hero images, heading text blocks, and above-fold videos are the most common LCP elements.
• CLS Must Stay Below 0.1: Layout shifts caused by late-loading images, fonts, or embeds frustrate mobile users by moving content as they are reading or about to tap.
• INP Measures Responsiveness Throughout Session: INP replaced FID to capture the worst interaction latency during the entire page session, not just the first interaction, mobile devices are more sensitive to this than desktops.
• Field Data Differs from Lab Data: Google Search Console CrUX data reflects real mobile user experience; Lighthouse scores in a development environment are useful but may not match field performance accurately.

Core Web Vitals failures on mobile are more common than on desktop because mobile devices have lower CPU power, slower connections, and higher sensitivity to JavaScript execution delays.

Image Optimization for Mobile Delivery

Serving appropriately sized images for mobile viewports using responsive images, modern formats, and lazy loading is typically the single highest-impact performance optimization for mobile redesigns.

• Responsive Images Serve Appropriate Sizes: The srcset attribute allows browsers to select the appropriate image size for the viewport; serving desktop-sized images to mobile devices wastes significant bandwidth.
• WebP Format Reduces File Size Substantially: WebP images are approximately 30% smaller than equivalent JPEG files; AVIF offers even greater compression with broad browser support growing steadily.
• Lazy Loading Defers Off-Screen Images: Images below the visible viewport should load only when the user is about to scroll them into view; this prevents wasting bandwidth on content that may never be seen.
• Explicit Width and Height Prevent CLS: Image elements without explicit dimensions cause layout shifts as the page calculates space after the image loads; always declare width and height attributes.

Image optimization delivers performance gains proportional to the image-heaviness of the design. Sites with large hero images, galleries, or product photography typically see the largest gains from this work.

Reducing JavaScript Impact on Mobile Performance

JavaScript-heavy pages harm mobile performance because phones have less powerful CPUs than desktop computers, and JavaScript execution blocks the main thread that handles rendering and user interaction.

• Third-Party Scripts Are Major Offenders: Analytics, chat widgets, social embeds, and marketing automation scripts collectively add significant mobile performance overhead that compounds across scripts.
• Code Splitting Reduces Initial Parse Cost: Breaking JavaScript bundles into smaller chunks that load only when needed reduces the initial JavaScript parse and execution cost on page load.
• Deferred Loading Moves Non-Critical Scripts: Scripts that do not need to run before the user interacts with the page should be deferred; render-blocking scripts in the document head are almost always avoidable.
• JavaScript Audit Before Launch Is Required: Every script on the redesigned site should be evaluated for necessity, size, and loading priority before the site goes live.

JavaScript weight is the second most common cause of mobile performance failure after unoptimized images. Both must be addressed in every mobile website redesign.

Mobile SEO and Search Visibility

Effective mobile SEO during a redesign requires understanding that Google's primary index is built from the mobile version of your site, not the desktop version. This has been true since 2021 for all newly indexed sites.

Google's Mobile-First Indexing Requirements

Mobile-first indexing means Google uses the mobile version of your site to determine search rankings for all users, including desktop users.

Any content, structured data, or metadata present only on the desktop version will not benefit your rankings.

• Content Parity Between Mobile and Desktop: All indexed content must be identical or equivalent between the mobile and desktop versions; content hidden on mobile does not contribute to rankings.
• Structured Data Must Appear on Mobile Pages: Schema markup implemented only in the desktop template will not be crawled by Google's primary mobile-first crawl.
• Meta Tags Must Be Present on Mobile: Title tags, meta descriptions, and canonical tags must appear in the mobile version's HTML, not only in the desktop template.
• Intrusive Interstitials Harm Mobile Rankings: Pop-ups, banners, or overlays that block content on mobile, particularly shortly after page load, are subject to a Google ranking penalty.

Mobile-first indexing requirements are not optional SEO preferences. They are the technical baseline for maintaining search visibility in a redesigned site.

Mobile Page Speed as a Ranking Factor

Core Web Vitals are a confirmed Page Experience ranking signal. Pages with poor Core Web Vitals scores receive a ranking disadvantage compared to equivalent pages with good scores, particularly in competitive search results.

• CWV Report in GSC Shows Actual Problem Pages: Google Search Console's Core Web Vitals report identifies specific URLs with poor scores using real user data, these pages are the priority for pre-launch performance fixes.
• Mobile and Desktop Scores Are Reported Separately: A site with excellent desktop CWV scores and poor mobile scores will have ranking issues; both must be addressed independently.
• LCP Improvements Have the Largest Ranking Impact: Among the three CWV metrics, LCP improvements have been most consistently associated with search ranking improvements in case studies.
• Speed Gains Compound Over Time: Improving mobile performance tends to reduce bounce rates, increase engagement, and improve conversion, all of which send positive quality signals that reinforce ranking improvements.

Page speed optimization and SEO are not separate work streams in a mobile redesign. They share the same technical solutions and the same measurement framework.

Mobile-Friendly Technical SEO Checklist

The technical SEO checklist for a mobile redesign covers viewport meta tag configuration, absence of horizontal scrolling, legible font sizes, accessible tap targets, and absence of mobile-blocking interstitials.

• Viewport Meta Tag Must Be Correct: The viewport meta tag must be present in every page's HTML head.
• No Horizontal Scroll on Any Viewport: Horizontal scrolling on mobile is a known ranking signal failure; every page must render without horizontal overflow at all common mobile viewport widths.
• Font Size Minimum 16px for Body Text: Text smaller than 16px on mobile requires pinching to read; Google's mobile usability report flags font sizes below this threshold.
• Google Mobile-Friendly Test Before Launch: Run every key page through Google's Mobile-Friendly Test tool before launch to identify any configuration issues the redesign may have introduced.

Technical mobile SEO issues prevent search traffic from reaching a redesigned site. They must be resolved before launch, not after organic traffic fails to materialize.

Mobile Conversion Optimization

Understanding mobile conversions after redesign requires acknowledging that mobile conversion rates are consistently lower than desktop conversion rates across almost every industry, and that most of that gap is not inherent to mobile user behavior.

It is caused by design friction that can be reduced.

Why Mobile Converts at Lower Rates (and How to Close the Gap)

The conversion gap between mobile and desktop is primarily caused by specific friction points: form complexity, page speed, navigation difficulty, and payment flow friction. Each has a corresponding design solution.

• Form Length Is the Largest Single Friction Point: Every additional form field increases mobile abandonment rate; audit every form for fields that are genuinely required versus merely convenient for the organization.
• Page Speed Has Disproportionate Mobile Impact: Research by Google shows that every one-second delay in mobile page load time increases bounce rate by up to 20%; speed improvements have larger conversion effects on mobile than on desktop.
• Navigation Difficulty Prevents Goal Completion: Users who cannot find what they are looking for on mobile abandon more quickly than those on desktop because the search for navigation options is more effortful.
• Payment Friction Blocks Final Conversion: Long checkout forms, required account creation, and limited payment options are the primary causes of mobile payment abandonment; address each specifically.

Closing the mobile-to-desktop conversion gap is one of the highest-ROI optimization efforts in most website redesign projects. The solutions are well-documented and implementable.

Mobile-Optimized CTAs and Contact Patterns

Mobile CTAs must be designed for thumb reach, immediate visibility, and one-tap action. Sticky headers with phone numbers, bottom-of-screen booking buttons, and one-tap payment options eliminate the steps between intent and action.

• Sticky CTA Persists Throughout Scroll: A sticky button or header that remains visible as users scroll ensures the conversion path is always accessible without requiring a scroll back to the top.
• Click-to-Call Is a One-Tap Conversion: A phone number displayed as a tel: href link initiates a call with one tap; remove every barrier between a mobile user and the ability to call.
• Apple Pay and Google Pay Eliminate Form Entry: One-tap payment options that use stored credentials convert mobile users at dramatically higher rates than forms requiring manual card entry.
• Chat Entry Point Must Be Easy to Tap: Chat or messaging CTAs should use minimum 44px tap targets and be positioned within comfortable thumb reach, not in a corner where they are easily missed.

Mobile CTAs designed specifically for thumb use convert at meaningfully higher rates than those adapted from desktop designs. This is measurable and worth testing before full launch.

Mobile Form Optimization

Redesigning forms for mobile completion requires single-column layouts, correct input type attributes, autofill-compatible field names, and progress indicators for multi-step processes.

• Single-Column Forms Eliminate Horizontal Scanning: Multi-column forms require horizontal scanning that is unnatural on a phone; single-column forms match the mobile scroll pattern.
• Input Type Attributes Control the Mobile Keyboard: Using type="tel" for phone fields, type="email" for email fields, and type="number" for numeric fields triggers the correct mobile keyboard, reducing errors.
• Autocomplete Attributes Enable Browser-Saved Data: Correctly named autocomplete attributes allow browsers and password managers to fill contact information with one tap, dramatically reducing form abandonment.
• Multi-Step Forms Show Clear Progress: Showing "Step 2 of 3" with a visible progress bar on multi-step forms reduces abandonment by setting expectations and giving users a sense of forward momentum.

Mobile form optimization is a technical and design discipline with measurable conversion impacts. Every form on the redesigned site should be tested on multiple actual mobile devices before launch.

Accessibility and Mobile Design

Addressing accessibility in mobile redesigns is not a separate concern from mobile design, it is the same concern. Accessible mobile design produces better experiences for all users, not just for those with disabilities.

Mobile Accessibility Standards

The WCAG 2.1 success criteria most relevant to mobile include touch target sizing at criterion 2.5.5, content reflow at 400% zoom at criterion 1.4.10, and motion sensitivity at criterion 2.3.3. Each has specific mobile implementation requirements.

• Touch Target Sizing Must Meet 44x44px Minimum: WCAG 2.5.5 requires a minimum target size of 44x44 CSS pixels for all interactive elements; this is also the Apple and Google human interface guidelines standard.
• Content Must Reflow at 400% Zoom: Users who zoom to 400% must be able to access all content by vertical scrolling alone, without horizontal scrolling; this requirement applies to all mobile viewports.
• Animations Must Respect Motion Preferences: The prefers-reduced-motion media query must be honored; users with vestibular disorders can experience physical discomfort from site animations and parallax effects.
• Color Contrast Requirements Apply to Mobile: The 4.5:1 minimum contrast ratio for body text and 3:1 for large text apply equally to mobile; do not reduce contrast for mobile designs to achieve visual effect.

Mobile accessibility requirements are WCAG requirements that apply regardless of platform. Treating mobile accessibility as a separate audit category rather than integrating it into mobile design is the most common compliance failure.

Screen Reader Testing on Mobile

Testing mobile accessibility using VoiceOver on iOS and TalkBack on Android is the only reliable way to identify screen reader failures that automated tools cannot detect.

• VoiceOver on iOS Is Used by Approximately 30% of Screen Reader Users: Testing with VoiceOver on an actual iPhone is essential for any mobile site that serves a broad audience.
• TalkBack on Android Behaves Differently from VoiceOver: Test with both platforms; screen reader behaviors differ significantly between iOS and Android, and failures on one do not always appear on the other.
• Custom Gestures Must Not Conflict with Screen Reader Gestures: Swipe-based navigation and gesture interactions must be tested to ensure they do not intercept the swipe gestures that screen readers use for navigation.
• Dynamic Content Must Be Announced: Content that loads or updates after initial page load, chat messages, form errors, loading states, must be announced to screen reader users through ARIA live regions.

Manual screen reader testing is the only way to validate mobile accessibility with confidence. Add it to the pre-launch QA checklist as a required, not optional, gate.

Accessible Mobile Forms and Inputs

The accessibility requirements for mobile form interactions include labeled inputs, error identification, autocomplete attributes, and sufficient color contrast for input states, requirements that also improve usability for all users.

• Visible Labels Must Be Present on Every Field: Placeholder text that disappears on focus is not an acceptable label substitute; every form field must have a persistent visible label.
• Error Messages Must Identify the Problem: Form error messages that say "invalid input" fail both accessibility standards and basic usability; specify what is wrong and how to correct it.
• Focus States Must Be Visible on Mobile: Keyboard and switch control users on mobile need visible focus indicators; default browser focus styles are often removed in CSS resets and must be replaced.
• Success and Error States Need Distinct Visual Design: Relying only on color to distinguish success from error states fails WCAG 1.4.1; use iconography, text, or pattern in addition to color for form state communication.

Accessible form design is both an accessibility requirement and a conversion optimization, the same clarity that helps screen reader users helps all users complete forms without frustration.

Mobile Design Trends to Adopt

Tracking current mobile design trends helps teams ensure their mobile redesigns reflect contemporary user expectations without chasing patterns that will feel dated quickly.

The most durable mobile design trends are those rooted in user behavior research rather than aesthetic preference. Mobile design evolves quickly; adopt patterns that serve users, not just ones that look current.

Bottom Navigation Bar Adoption

Bottom navigation is increasingly the preferred pattern for mobile-heavy applications because it places primary navigation within natural thumb reach, reducing the strain of reaching for top navigation bars on larger phones.

• Bottom Navigation Improves One-Handed Use: Primary navigation at the bottom of the screen is accessible with the thumb without repositioning the hand, improving comfortable single-handed use.
• Tab Bars Signal App-Like Quality: Bottom tab bar navigation signals a deliberately mobile-optimized experience; top-only navigation is increasingly associated with desktop-adapted rather than mobile-first designs.
• Limited to Four or Five Primary Sections: Bottom navigation bars work best with four or five primary sections; more than five creates too-small tap targets and visual crowding.
• Floating Action Buttons Highlight Primary Actions: A floating action button (FAB) positioned above the bottom navigation bar provides a single, highly visible primary action CTA without requiring navigation.

Bottom navigation is a mature, well-researched mobile design pattern. Consider it for any site where users frequently switch between primary sections.

Larger Text and Cleaner Layouts

The trend toward larger body text sizes, more generous line height, and simpler layouts with ample white space reflects growing understanding that reading on a small screen requires more typographic support than reading on a large monitor.

• Body Text Minimum 16-18px on Mobile: Text below 16px on mobile is commonly identified as a readability issue by both users and automated accessibility audits.
• Line Height of 1.5-1.6 for Body Copy: Line height on mobile needs to be slightly more generous than on desktop because the shorter line lengths on mobile create denser visual rhythm.
• White Space Is Not Empty Space: Generous spacing between elements on mobile is not wasted space, it is what makes content readable and tappable without error.
• Single-Column Layouts Are the Modern Default: Multi-column layouts on mobile have largely been replaced by single-column designs that match the natural scroll pattern of mobile use.

Typography decisions for mobile have direct conversion and accessibility implications. Invest in getting them right rather than carrying desktop typographic scales into mobile designs.

Conclusion

A mobile website redesign done right does not make the desktop site smaller.

It builds a genuinely better experience for the majority of your users by treating mobile constraints as design opportunities rather than limitations to work around.

Open your current site on your phone right now and time how long it takes to complete your most important user task.

If it takes more than thirty seconds, that is your mobile redesign's most urgent priority, before any visual changes are made.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

LOW/CODE Agency Builds Mobile-First Websites That Perform and Convert

Building sites that perform on mobile requires a methodology that starts at the smallest screen, treats performance as a design constraint, and tests every interaction pattern on actual devices.

LOW/CODE Agency is a strategic product team that builds mobile-first websites for clients who need measurable results, not just responsive layouts.

We bring mobile-first design methodology, Core Web Vitals optimization, and mobile conversion architecture to every website engagement.

• Mobile-First Design Process: Every project at LOW/CODE Agency begins with mobile wireframes and mobile content prioritization before desktop design begins.
• Core Web Vitals Optimization: We set mobile performance benchmarks during discovery and deliver sites that pass LCP, CLS, and INP thresholds at launch.
• Mobile Conversion Architecture: We design CTAs, forms, and contact patterns specifically for mobile users, closing the conversion gap between mobile and desktop.
• Responsive Image Delivery: We implement srcset, WebP/AVIF formats, and lazy loading as standard practice on every redesign project.
• Accessibility Compliance: Every site we build meets WCAG 2.1 AA standards, including mobile-specific touch target, reflow, and motion sensitivity requirements.
• Mobile SEO Technical Implementation: We deliver mobile-first indexing compliance, viewport configuration, and technical SEO readiness as part of every launch checklist.
• Post-Launch Performance Monitoring: We monitor Core Web Vitals field data after launch and address regressions before they affect rankings or conversion rates.

LOW/CODE Agency has delivered 450+ products for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku. We bring that performance-first culture to every mobile website redesign.

Explore our mobile website redesign services or Start with a scoping call to discuss your mobile performance goals.