masayaco.com website review

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

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

8 third-party services load with your homepage (loox.io, Klaviyo and tidio.co and others), adding 1.0 MB and 518 ms of main-thread time.

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

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

tidio.co costs a phone 94 ms of main-thread work and 515 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.

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

1 image could be 33 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

About 16 KiB of CSS is downloaded but never applied on this page.

6 KiB JavaScript is shipped twice across bundles.

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 11.6 s. Good is under 3.8 s.

Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Solid Teak handmade sidetable for outdoor”.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 146 ms to 195 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 2.0 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.9 MB in 226 requests on a phone: images 1.8 MB (32), scripts 1.0 MB (79) and other files 751 KiB (87). Under 2 MB keeps phones on slow connections fast.

1 image (222 KiB) is 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.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 26 characters: “MasayaCo Forever Furniture”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 231 pages on masayaco.com and 16 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/, /nl-nl, /nl-be, /de-de, /fr-fr and /es-es all use the title “MasayaCo Forever Furniture”. Search engines can't tell which page to show for a search, so each competes with the others.

/nl-nl, /nl-be, /de-de, /fr-fr and /es-es use the same meta description. A description written for each page earns more clicks.

/pages/trade and /pages/showrooms have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 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: 5 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.

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 595 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 34 cookies, 3 of them by other companies (measured from a US location before any click).

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