Garmin Fenix 9 Pro and the Display Lag Hall of Shame. Test Results.

I’ve been testing the Fenix 9 Pro in preparation for a detailed review later in the month. It’s a nice watch, and for a thousand dollars/pounds it should be.

Two negative aspects immediately spring to mind that potential buyers need to be aware of. One is a speaker that can’t handle the intended (default) volume and sounds broken, though this probably isn’t new hardware, as previous models sounded similar to me. The other issue is the new, faster CPU and graphics engine, which is improved over the earlier one on the Fenix 8/8 Pro (technical deep dive here into the Fenix 9 / 9 Pro component changes) but still isn’t up to the job.

The article explores why it isn’t up to the job, with some test results, and I’ve also added results from Jerome at MontreCardio in France, who has been running similar tests, instead comparing to Fenix 8/8 Pro.

Other Brands

On this site, I test all the sports watch brands on the market. In my testing, the current flagship adventure watches from Amazfit, Suunto, Apple, Coros and Polar all rendered a full map display very quickly: the Amazfit T-Rex Ultra 2, Suunto Vertical 2, Apple Watch Ultra 3, Coros Vertix 2S and Polar Grit X2 Pro all clear this test comfortably. The point is that technical solutions to lag exist, and Garmin isn’t using them.

Garmin Maps

Garmin has detailed maps. More than that, Garmin lets you add multiple overlays, like contours, weather and heatmaps. That’s much richer data than you get from the competition.

My working theory was that Garmin now has a modern graphics engine but was displaying much more data than the competition. Let’s see if that’s true, but also bear in mind that on-device caching may have sped up the performance I see here, and if you have the 51mm Fenix 9, its higher pixel count might further slow rendering.

Here are multiple, partly subjective speed tests covering many aspects of the Fenix 9 Pro’s interface.

Startup Time (cold Boot)

It takes 76 seconds for the Fenix 9 Pro to fully start up, including a map check.

Raise to wake watchface

This behaviour will vary by watchface. For the best-designed watchfaces, when the Always-On Display (AOD) is working, the screen dims when the wrist is turned away, and certain screen elements are disabled to save battery. When you twist your wrist to view, everything lights up, and the hidden screen elements are shown

Time: there is a very tiny lag, which is acceptable. I can’t measure how long it takes, but I’d estimate it at 0.1-0.2 seconds. Quick.

Press Start to enter menus and leave watchface

This is slower than the raise-to-wake movement. I would say it takes half a second.

Scrolling through main menus

This is 98% smooth. Occasionally, there is a slight jump when one menu item leaves the screen and another enters.

Choosing a Menu Option to show further options

This generally feels instant, but I did notice an almost 2-second delay going from Shortcuts to the list of shortcut options when first pressed.

Choosing a Sport Profile

With a choice of profiles showing on the screen, you choose one. The time it takes to display the particular sport profile’s start screen is about a second, sometimes longer, sometimes just under. This feels like a lag.

Exploring the profile and starting a workout

Exploring the profile seems almost lag-free. There is a minuscule lag when starting the workout itself. No different from before, and certainly better than something like the Apple Watch Ultra 3, where there is noticeable lag with the audible beep in what, after all, is one of the most important aspects of a sports watch’s performance: starting the workout correctly.

Discarding or saving a small workout

The end-of-workout behaviours from Garmin are market-leading in terms of the scope of the features offered. However, anyone who has owned a Garmin watch before will know that discarding or saving workouts takes seconds. That doesn’t appear to have changed.

• Discarding – takes 4-5 seconds
• Saving – varies depending on the length and complexity of the workout data.
  • Takes two seconds for the stop button to translate to resume/save.
  • Takes a further 4-5 seconds (minimum) to start displaying workout summary data

Map Performance

This is the area of most concern. Garmin map panning and zooming on previous-generation Fenix models was awful. Has it improved?

Fenix 7 and Fenix 8 owners have reported the same problem for years. Garmin’s own forums document Fenix 7 users flagging slow map scrolling, and Fenix 8 owners describing panning and redrawing as unusable in places, slower even than the older Epix 2. the5krunner documented the same problem on the Fenix 8 at launch, when full-screen map draws were taking up to 5 seconds.

I performed numerous tests and included four typical recordings for anyone who wants to dive deeper or see the experience they might encounter if they buy a Fenix 9 Pro. These cover every combination of zooming (layers vs no layers) and panning (layers vs no layers): watch the playlist here.

It’s worth understanding that Garmin’s default TOPO (topographic) maps, supplied free, comprise multiple map layers. Each layer has many square sections of vector map data, which are rendered separately, and there is a map layer for each zoom level. You could therefore expect more of a delay when zooming in or out, since that essentially loads a different map. When panning at the same zoom level, adjacent tiles from that level are loaded and displayed. Theoretically, these can be cached more easily, so when you pan, the watch has already anticipated where you might go and can serve those tiles quickly.

Garmin also supplies further special layers, like weather and the heatmap. These layers are overlaid on the map layer of the zoom level you’ve chosen. The more layers displayed simultaneously, the more information the watch has to load and display. At least that’s the theory.

Why Garmin’s Maps Are Slower to Render

Garmin’s built-in maps are vector-based, not like the pre-rendered image tiles used by some competitors. The watch draws roads, points of interest and contour lines live from raw map data every time you pan or zoom, rather than simply displaying a static picture. That’s more capable, and it’s part of why the data is so rich, but it’s also far more demanding on the processor.

Coros, by contrast, uses raster tile rendering: pre-rendered static images that the watch just displays. A discussion on Garmin’s own forums put it plainly: Coros’s approach is dramatically less CPU-intensive.

Hardware compounds the problem. According to a technical breakdown on Garmin’s forums, the Fenix, Epix and Enduro lines share a chip with just 5MB of onboard RAM, while the equivalent chip used by Coros, Suunto and Polar carries an extra 32MB module, for roughly 37MB total. That leaves Garmin’s watches with far less room to cache map data, so panning and zooming repeatedly forces the watch back to slower storage to redraw. The Fenix 9 Pro’s 50% RAM increase narrows that gap, but doesn’t close it, and it doesn’t change the underlying approach: real-time vector rendering will always ask more of the processor than displaying a static tile.

General findings are that:

• The most zoomed-out views take the longest to load.
• Enabling every special layer typically adds no more than one additional second to the rendering time.
• Tiles at the centre of the screen, the ones you’ll typically focus on first, are rendered almost immediately almost all the time.
• Peripheral tiles can take considerable time to load, sometimes up to 15 seconds (16 seconds with all special layers enabled).

Zoom tests were performed around a location on the map in London. Panning tests were performed in different areas of the map in Northern England and Scotland.

Map Zoom Tests

Zooming in typically takes about 3 seconds with layers enabled, though this can extend to 5 or 6 seconds. The central tiles on display always render immediately, and the last elements to display appear to be the additional layers.

Turning layers off typically saves about 1 second, though this varies. Even with layers off, zooming out fully can still take up to 15 seconds to redraw in some instances.

Map Pan Tests

With layers enabled, panning while zoomed out typically takes about 4 seconds, sometimes extending to 6. Zooming with layers enabled in the Scotland test areas was slightly faster than earlier, around 13 seconds.

With layers disabled, panning generally takes 0 to 3 seconds.

How Does This Compare to the Fenix 8 or Fenix 8 Pro?

Jerome at MontreCardio has run these Fenix 9 Pro vs Fenix 8 Pro comparisons. I’d encourage you to watch his video (French audio), and here’s a summary of his findings.

Menu navigation, route loading, weather overlay rendering, and activity stop-and-save timing were roughly identical on both watches. TopoActive zooming in and slow panning were faster on the Fenix 9 Pro, as was panning across shaded relief terrain, thanks to tile pre-loading. Shaded relief’s initial render was slightly faster on the Fenix 8 Pro, and post-activity stats loaded faster on the Fenix 8 Pro too. On the third-party MapRando map, the Fenix 9 Pro showed sharper detail at wide zoom levels, and small pans and recentering were significantly faster, again down to tile pre-loading. Both watches showed GPS drift while stationary over a 7-minute test in standalone GPS mode: 40m on one unit, 90m on the other.

Thoughts and Summary

Garmin has certainly improved the technology in the Fenix 9 Pro, and it is generally a superbly capable watch.

However, it’s an adventure watch, and adventurers typically buy this watch to use maps. As well as a sports tech company, Garmin is also a mapping company. Bearing those two things in mind, you would have thought that the mapping experience on a Garmin adventure watch would be second to none. In reality, it’s at the bottom of the pile.

Garmin says the Fenix 9 has 50% more RAM than the Fenix 8 and a new map engine, with panning up to 30% faster than the Fenix 8 and round-trip route calculation 40% faster than the Fenix 8 Pro. Neither claim matches what these tests show. Panning with layers enabled still takes up to 6 seconds, and peripheral map tiles can take up to 15 or 16 seconds to fully render.

Part of this can be explained by the richer map details Garmin displays, but many Garmin map rendering actions still feel to me three, four, or five times slower than on competitor watches. The fundamental architecture is the problem; more memory helps, but the underlying mechanism of live, vector-based rendering will always be CPU-intensive and slow.

There is no quick fix.

Quick answers

Does the Garmin Fenix 9 Pro have map lag?
Yes. Peripheral map tiles can take up to 15 to 16 seconds to render fully, particularly at wide zoom or with all layers enabled.

How long does the Garmin Fenix 9 Pro take to boot up?
A full cold boot, including a map check, takes 76 seconds.

Is Garmin's claimed 30% faster panning accurate in real-world testing?
Testing on this site and by MontreCardio shows mixed results rather than a consistent 30% improvement, with some map actions faster on the Fenix 9 Pro and others faster on the Fenix 8 Pro.

How does the Fenix 9 Pro's map speed compare to rivals?
The current flagship adventure watches from Amazfit, Suunto, Apple, Coros and Polar all render a full map display in under a second, comfortably ahead of the Fenix 9 Pro.

Last Updated on 3 September 2026 by the5krunner