Speed
Short answer: on a live store with a pre-rendered menu, the Navi+ menu appears at the same time as the page, less than 0.1 seconds after the page shows. Globo does the same. Qikify is 1.2 seconds later on 4G and 6 seconds later on a slow 3G connection. Navi+ is not faster than Globo. The two are even on this measure, and Navi+’s code is heavier.
Measured Nov 4, 2026. Pick a network and device in the chart below to see each case.
Phone: “menu appears” means the moment you tap ☰ and the drawer finishes opening.
Phone: “menu appears” means the moment you tap ☰ and the drawer finishes opening.
How to read it: the light grey bar is the wait until the page shows. The dot is when the menu appears. A dot at the very end of the bar means the menu appears together with the page. A dot far behind means the menu is still late.
How late does the menu appear after the page?
This is the most useful column to compare. The three stores tested are different stores, so the absolute seconds can’t be compared directly.
Extra app size
Navi+’s code is nearly twice as heavy as Globo’s, and a little lighter than Qikify’s. The Navi+ menu still appears quickly despite the heavier code, because it is pre-rendered into the page and doesn’t have to wait for the code to finish loading.
Does the page jump around?
All three are good in most cases. It is not yet possible to separate what comes from the app and what comes from the theme.
How it was measured
Slow 3G: 1.6 Mbps, 562 ms latency
The menu counts as shown when: on desktop, the text of at least 3 menu items is actually visible; on mobile, when you tap ☰ and the Mobile Menu opens with its list of items. Three stores were measured: a live store running Navi+ (Dawn theme, pre-rendering on), Globo’s public demo (Dawn), and Qikify’s public demo (an older theme).
Where Navi+ loses or isn’t better
On menu delay after the page appears, the two apps are even. There isn’t enough evidence to say Navi+ is “the fastest”.
192 KB of JavaScript vs 96 KB, almost double.
Navi+ only pre-renders when it can capture the menu exactly as it really appears. When it can’t, the menu shows up after the code loads, about 1.7 seconds on 4G with a Desktop Mega Menu (measured Nov 3, 2026). See Does Navi+ slow down your store?. At that point Navi+ is closer to Qikify than to Globo.
0.024 vs 0.000 and 0.001 for the other two apps, though still in the good range.
Limits of the test
- Three different stores, not the same store with each of the three apps installed in turn. The menus in Globo’s and Qikify’s demos are set up by those companies and may differ from a real customer’s store.
- Measured only in Chrome (simulated phone), not yet on a real iPhone or Safari.
- Network and CPU are simulated, on one machine, so the numbers on your store will differ. Use them to compare apps with each other, not as absolute numbers.
- Each cell has only 5 to 8 runs.
Pre-rendering makes the menu appear at the same time as the page instead of waiting for the code to load. Measured Nov 3, 2026 on a live store, Desktop Mega Menu, 4G: about 0.3 seconds with pre-rendering, and about 1.7 seconds without.
See the detailed numbers
Test conditions
| Condition | Value |
|---|---|
| 4G network | 9 Mbps download, 1.5 Mbps upload, 170 ms latency |
| Slow 3G network | 1.6 Mbps download, 0.75 Mbps upload, 562 ms latency |
| Device | One machine, each case run in turn, Chrome incognito, CPU slowed 4×, cache off |
| Screen | Desktop 1440 × 900. Phone 393 × 852 |
| Runs | 1 warm-up run discarded, then 5 to 8 measured runs, using the median |
Desktop: when the menu appears (seconds from opening the page)
| Navi+ | Globo | Qikify | |
|---|---|---|---|
| 4G network | |||
| Menu appears | 0.62 | 0.69 | 1.76 |
| Page appears | 0.65 | 0.62 | 0.52 |
| Menu delay after page | 0.0 | 0.08 | 1.24 |
| Slow 3G network | |||
| Menu appears | 2.44 | 2.08 | 7.56 |
| Page appears | 2.41 | 2.00 | 1.40 |
| Menu delay after page | 0.01 | 0.08 | 6.16 |
Mobile: when the menu opens after tapping ☰ (seconds from opening the page until the Mobile Menu shows its list of items)
| Navi+ | Globo | Qikify | |
|---|---|---|---|
| 4G network | |||
| Mobile Menu open | 1.06 | 0.70 | 2.14 |
| Page appears | 0.97 | 0.58 | 0.52 |
| Open delay after page | 0.11 | 0.12 | 1.62 |
| Slow 3G network | |||
| Mobile Menu open | 2.50 | 2.06 | 7.58 |
| Page appears | 2.40 | 1.96 | 1.38 |
| Open delay after page | 0.10 | 0.12 | 6.21 |
Navi+’s absolute seconds on mobile are higher because the measured store page is heavier than Globo’s demo page (about 2 MB vs about 1 MB on 4G).
Size and extra requests (4G network, compressed)
| Navi+ | Globo | Qikify | |
|---|---|---|---|
| Total size | 232 KB | 144 KB | 282 KB |
| Of which JavaScript | 192 KB | 96 KB | 279 KB |
| Extra requests | 10 to 11 | 18 | 5 |
CLS (page layout shift)
| Navi+ | Globo | Qikify | |
|---|---|---|---|
| Desktop, 4G | 0.003 | 0.003 | 0.037 |
| Mobile, 4G | 0.024 | 0.000 | 0.001 |
| Mobile, slow 3G | 0.000 | 0.791 | 0.002 |
Load capacity, stability
A store with lots of visitors doesn’t slow the menu down, because the menu is served from Cloudflare’s CDN network, not from your admin.
~11 KB
Just a small piece of code
About 1/5 the size of one product image.
99.99%
Served from a global CDN
Main network Cloudflare, backup BunnyCDN. SLA commitment up to 99.99%.
- When you click save, Navi+ pushes your menu configuration to Cloudflare, a content delivery network (CDN) with servers in many countries. The browser also caches the menu file after the first load, so the next page doesn’t have to download it again.
- The BunnyCDN backup network is an option in the app embed settings, so the menu can still load if the main network has a problem. It is off by default. See Settings that keep your menu loading fast and flicker-free.
| Starter | Business | Elite | |
|---|---|---|---|
| Infrastructure | Basic infrastructure | Good CDN, strong in North America, Europe and Asia | Runs well globally, Cloudflare + BunnyCDN backup |
| SLA commitment | 99.00% | No figure published yet | 99.99% |
| Menu views | 20,000 per month | 500,000 per month | Unlimited |
When you go over the view limit, Navi+ does not turn off your menu. The app sends you an email warning. If you stay over for a long time, a small ad may appear in a corner of the menu, without blocking shoppers from clicking. The Elite plan has no ads. For details on each plan, see Plans and billing.
Data security
Navi+ only needs read access to store information to build the menu. The app does not ask for permission to edit the theme, read orders, or read customer purchase information.
Navi+ reads
Current themeProductsShopify menusPages and blog postsNavi+ does not touch
OrdersPaymentsCustomer dataTheme filesWhen you click Install app, Shopify shows a list of permissions. Navi+ asks for exactly four permissions, all read-only:
| Permission | Used for |
|---|---|
| Read themes | Recognizes your current theme and suggests where to place the menu |
| Read products | So you can pick products to put in the menu |
| Read navigation menus | Brings your existing Shopify menus over as a draft |
| Read content | So you can pick pages and blog posts for the menu |
- Not requested: permission to read orders, customer information or payments. There is also no permission to write to the theme: the menu shows on your store through the app embed switch, not by editing theme files. See What is Navi+?.
- Signature check: when Shopify reports something like a plan change or an app uninstall, Navi+ checks the signature (HMAC) before processing it. Requests with a wrong signature are rejected with a 401 error. When you open the app inside the Shopify admin, the app also checks the session token Shopify issues.
- Personal data: Shopify requires every public app to accept three requests: a customer asks to see their data, a customer asks to delete their data, and a store asks for data deletion after uninstalling the app. Navi+ has registered all three.
- Uninstall: the access token for your store in the Navi+ system is deleted, and the running paid plan is canceled. You don’t need to clean up any code in your theme, because Navi+ doesn’t insert anything there. See Turn off or uninstall Navi+.
SEO for menus
Navi+ menus give each item a real link so Google can read it, but only on the Elite plan. The Starter and Business plans don’t yet use real links, so Google can’t see these links from Navi+. If SEO matters to you, use Elite, or keep your theme’s menu for the links. See Plans and billing.
Real link, Google can read it
- Real link, with a name and URL: each menu item is wrapped in a link tag that has its URL, plus
altandtitleset to the item’s name. The item’s image also hasaltandtitle. - Available when the page opens: with pre-rendered menus, the menu content, including these links, is already in the page and doesn’t wait for the Navi+ library to download.
Check it yourself on your store
- Open your store, press F12 to open the browser’s inspector, and select the Elements tab.
- Press Ctrl+F (Mac: Cmd+F) and type the URL of a menu item, for example
/collections/giay. - You’ll see the
<a href="…" alt="…" title="…">tag for that item inside the menu section.
Good to know
- Include the important pages, such as main categories and collections, in your menu so Google can see the whole store structure.
- The theme’s menu always has real links, so on the top plan this is an area where Navi+ matches the theme rather than beating it.
- There is no data yet showing that Navi+ menus rank better on Google. Real links only help Google read the menu.