mino77-blue.com website review

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

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

POWr costs a phone 1.8 s of main-thread work and 62 KiB 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.

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

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

8 third-party services load with your homepage (POWr, bluettipower.id and powrcdn.com and others), adding 2.0 MB and 2.3 s of main-thread time.

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

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

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

bluettipower.id costs a phone 205 ms of main-thread work and 919 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.

powrcdn.com costs a phone 163 ms of main-thread work and 609 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.

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

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

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.

Your largest element takes 16.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MINO77 x BLUETTI Genset Bertenaga Surya EB3A MINO77 x BLUET…”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

27 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.

Your homepage downloads 3.7 MB in 149 requests on a phone: scripts 1.3 MB (58), other files 1.3 MB (61) and images 774 KiB (13). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example SGTotemWarrior.webp at 400 px wide, shown at 88 px. Resized copies would save about 173 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 1.06 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.

1 button has no accessible name, so screen readers announce just “button”.

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 link inside paragraphs relies on colour alone to stand out.

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

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

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

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 19 characters: “MINO77 x BLUETTI-ID”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 83 pages on mino77-blue.com and 10 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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

Your homepage links to https://mino77-blue.com/collections/christmas-sale-2024, which answers with an error. Visitors hit a dead end and search engines drop it.

https://mino77-blue.com/collections/blackfriday, https://mino77-blue.com/pages/portable-power-station, https://mino77-blue.com/products/eb3a, https://mino77-blue.com/collections/portable-power-station, https://mino77-blue.com/pages/solar-generator and https://mino77-blue.com/collections/solar-generator-kit and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://mino77-blue.com/products/ac180 and https://mino77-blue.com/products/bluetti-ac180-portable-power-station-1800w-1152wh use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mino77-blue.com/collections/blackfriday, whose canonical is https://mino77-blue.com/collections/christmas-sale. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://mino77-blue.com/pages/portable-solar-panel has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

4 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads 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 10 cookies, 2 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.