nawhals.com website review

11 images could be 597 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Facebook, Shopify and nfcube.com and others), adding 1.1 MB and 384 ms of main-thread time.

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

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

Shopify costs a phone 135 ms of main-thread work and 536 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.

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

About 208 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

Polyfills for old browsers add 13 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 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Mix & Match Original / Spicy”.

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

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

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

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

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

mms-story-decor.webp weighs 706 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 3.7 MB in 314 requests on a phone: images 1.3 MB (24), scripts 1,006 KiB (125) and other files 843 KiB (133). Under 2 MB keeps phones on slow connections fast.

3 images (1.2 MB) 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.

mobile_EN_spicy_bbq.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

2 tap targets are too small or too close together to hit reliably with a finger.

2 images have no alt text, which hurts accessibility and image search.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

The homepage links to 57 pages on nawhals.com and 12 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://nawhals.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://nawhals.com/customer_authentication/redirect, https://nawhals.com/products/pack-soiree-kebab-1, https://nawhals.com/products/pack-soiree-burger-1 and https://nawhals.com/products/pack-soiree-tacos-1 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://nawhals.com/products/spicy-barbecue-sauce and https://nawhals.com/fr/products/spicy-barbecue-sauce all use the title “SPICY BARBECUE SAUCE – Nawhal's Sauces”. Search engines can't tell which page to show for a search, so each competes with the others.

https://nawhals.com/blogs/news, https://nawhals.com/pages/contact, https://nawhals.com/customer_authentication/redirect, https://nawhals.com/policies/shipping-policy, https://nawhals.com/products/mix-match-algerienne-barbecue and https://nawhals.com/products/mix-match-algerienne-spicy-bbq have no meta description, so Google writes the search snippet from whatever text it finds.

https://nawhals.com/products/spicy-barbecue-sauce and https://nawhals.com/fr/products/spicy-barbecue-sauce use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://nawhals.com/fr/products/spicy-barbecue-sauce, whose canonical is https://nawhals.com/products/spicy-barbecue-sauce. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://nawhals.com/pages/who-we-are, https://nawhals.com/pages/contact and https://nawhals.com/customer_authentication/redirect have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://nawhals.com/cdn/shop/t/163/assets/tiny.content.min.css?v=11732' because its MIME t…”.

Requests the notification permission on page load.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 16 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage has only about 109 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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, 1 of them by other companies (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 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.