wafuu.com website review

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

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

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

8 third-party services load with your homepage (minmaxify.com, Google Tag Manager and vitals.app and others), adding 1.3 MB and 1.2 s of main-thread time.

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

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

minmaxify.com costs a phone 409 ms of main-thread work and 10 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.

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

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

Google Tag Manager costs a phone 328 ms of main-thread work and 356 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.

vitals.app costs a phone 220 ms of main-thread work and 533 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.

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

6 images could be 75 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Polyfills for old browsers add 10 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.

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

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “WAFUU JAPAN”.

Scripts block taps and scrolling for 980 ms in total while the page loads. Good is under 200 ms.

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

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

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

Your homepage downloads 3.7 MB in 416 requests on a phone: scripts 1.4 MB (95), other files 963 KiB (125) and images 942 KiB (178). Under 2 MB keeps phones on slow connections fast.

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

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

13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

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

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

10 links have no real href, so search engines can't follow them.

Your <h1> is empty.

The homepage links to 981 pages on wafuu.com and 11 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://wafuu.com/ar-us, https://wafuu.com/de-us, https://wafuu.com/es-us and https://wafuu.com/fil-us have no <h1> headline, so visitors and search engines get no clear main topic.

https://wafuu.com/ar-us and https://wafuu.com/es-us took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343025659&Ver=2&mid=5bb86c35-1a64-47b9-8883-64bc6c6766ff&bo=1&sid=03aebd60d80611f18806ab1d2c76a50e&vid=03aef1d0d80611f1b88ba7f408829a04&vids=1&msclkid=N&pi=918639831&l.

57 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 171 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 shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 1,276 words of visible text.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 4 mores (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 24 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 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.