navigatecraft.com website review

18 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

The page has 3,828 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Your mobile performance score is 78. Pages that score under 90 lose visitors before the first paint.

8 images could be 257 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

About 349 KiB of JavaScript is downloaded but never used on this page.

A phone's processor spends 2.3 s on main-thread work while loading, 720 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Shopify costs a phone 156 ms of main-thread work and 333 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

8 third-party services load with your homepage (Shopify, Google Tag Manager and Klaviyo and others), adding 766 KiB and 428 ms of main-thread time.

2 long tasks block the main thread while loading, the longest for 101 ms. During a long task the page ignores taps.

11 files are served with short cache lifetimes, so returning visitors download them again (57 KiB).

About 10 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 20 ms faster on a phone.

Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ The biggest discount of the year, 50% off. ”.

The page becomes fully interactive after 9.3 s. Good is under 3.8 s.

Visually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 107 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.0 MB in 224 requests on a phone: images 1.0 MB (36), scripts 852 KiB (82) and other files 810 KiB (80). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.85 g of CO₂e: 102.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element hidden from screen readers can still receive keyboard focus.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.

16 visible links have no text or label, so screen readers cannot say where they go.

Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.

Your title is 70 characters, so Google will cut it off around 60: “Navigate Craft | Premium Metal Aircraft Wall Decor | Shop Aviation Art”.

Your meta description is 288 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 372 pages on navigatecraft.com and 0 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://navigatecraft.com/collections/all, https://navigatecraft.com/policies/shipping-policy, https://navigatecraft.com/collections/best-sellers, https://navigatecraft.com/collections/aircraft, https://navigatecraft.com/collections/fighters and https://navigatecraft.com/collections/trainers and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://navigatecraft.com/products/p-51-mustang-metal-aircraft-wall-art-ncp0111, https://navigatecraft.com/products/skyhawk-172-metal-aircraft-wall-art-ncp0126 and https://navigatecraft.com/products/spitfire-mk-ii-metal-aircraft-wall-art-ncp0130 use the same meta description. A description written for each page earns more clicks.

We fetched 15 pages linked from your homepage (of 185 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 858 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 14 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.