navyz.com website review

54 files are served with short cache lifetimes, so returning visitors download them again (19.9 MB).

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).

About 362 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

Your mobile performance score is 38 (desktop: 64). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

Polyfills for old browsers add 42 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

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

4 third-party services load with your homepage (userway.org, cloudflare.com and FontAwesome CDN and others), adding 561 KiB and 131 ms of main-thread time.

15 KiB could be saved by minifying JavaScript.

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

Desktop scores 64 but mobile only 38. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Real visitors wait 2.2 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Video Player Contact-free Solutions to Run Your Business GE…”. Most of its time is resource load delay (10.2 s).

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

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

The first text or image appears after 5.0 s on a phone. Good is under 1.8 s.

The layout shifts by 0.38 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.

Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 25.1 MB in 114 requests on a phone: media 17.9 MB (4), other files 4.1 MB (38) and scripts 962 KiB (26). Under 2 MB keeps phones on slow connections fast.

Popup_FreeGeniusPOS_2026.png weighs 519 KiB. On a phone connection a single image that size takes seconds.

2 images (559 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

1 image further down the page (519 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example Popup_FreeGeniusPOS_2026.png at 1,200 px wide, shown at 390 px. Resized copies would save about 26 KiB.

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

2 dropdowns have no label.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

40 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Headings skip levels (h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

There are 3 <h1> headlines (“Contact-free Solutions to Run Your Business”, “Contact-free Solutions to Run Your Business” and “Contact-free Solutions to Run Your Business”). One clear main headline is easier for people and search engines.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 106 pages on navyz.com and 6 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.

There is no https://www.navyz.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.navyz.com/kr and https://www.navyz.com/navyz-geniuspos have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.navyz.com/kr, https://www.navyz.com/pos-solution, https://www.navyz.com/qsr-pos, https://www.navyz.com/restaurant-pos, https://www.navyz.com/salon-pos and https://www.navyz.com/retail-pos and 6 others took over 3 s to send their HTML from our server.

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

2 of 5 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Your longest form asks for 9 fields (5 required). Every extra field lowers completion.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 533 words of visible text.

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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.