unionaire.com website review

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

16 images could be 4.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

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

Google Tag Manager costs a phone 1.2 s of main-thread work and 1.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 2.9 MB and 1.8 s of main-thread time.

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

Facebook costs a phone 389 ms of main-thread work and 426 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.

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

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

Google CDN costs a phone 80 ms of main-thread work and 351 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 49 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.

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

21 KiB could be saved by minifying JavaScript.

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 7.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 1.0 s for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your largest element takes 20.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “UNIONAIRE-&-Souhola-1000×1000”.

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

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

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

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

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

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

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

11 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 9.9 MB in 272 requests on a phone: images 6.1 MB (61), scripts 3.2 MB (95) and fonts 225 KiB (6). Under 2 MB keeps phones on slow connections fast.

5 images weigh 4.0 MB together. On a phone connection a single image that size takes seconds.

8 images (3.8 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.

4 images further down the page (3.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example Installement-New-Banner-1000×1000.webp at 1,900 px wide, shown at 390 px. Resized copies would save about 182 KiB.

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

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

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

All page content should be contained by landmarks: 12 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.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 16 characters: “Home - Unionaire”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 116 pages on unionaire.com and 5 external pages.

https://unionaire.com/product-category/fans and https://unionaire.com/product-category/screens use the same meta description. A description written for each page earns more clicks.

https://unionaire.com/ar, https://unionaire.com/help, https://unionaire.com/product-category/fans, https://unionaire.com/product-category/screens, https://unionaire.com/about-us and https://unionaire.com/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

https://unionaire.com/ct has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://unionaire.com/ar, https://unionaire.com/help, https://unionaire.com/product-category/fans and https://unionaire.com/product-category/screens took over 3 s to send their HTML from our server.

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

55 of 120 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 “e.jetStickySection is not a function o (https://unionaire.com/wp-content/plugins/jet-blocks/assets/js/jet-blocks.min.js…”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 666 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, Meta Pixel and TikTok 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 28 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.