ugreen.jp website review

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

About 646 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.

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Klaviyo and others), adding 1.7 MB and 1.1 s of main-thread time.

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

Google Tag Manager costs a phone 407 ms of main-thread work and 471 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 181 ms of main-thread work and 470 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 2,141 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Klaviyo costs a phone 172 ms of main-thread work and 308 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.

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

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

About 16 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.

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

Polyfills for old browsers add 27 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 62.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “UGREEN <span class=”.

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

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

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

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

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

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

Your homepage downloads 14.3 MB in 322 requests on a phone: fonts 8.1 MB (10), images 3.5 MB (89) and scripts 1.8 MB (97). Under 2 MB keeps phones on slow connections fast.

15 images are downloaded at several times the size a phone draws them, for example 7d9ea842-6fda-4eac-8859-8d30b26a3bcf.png at 1,387 px wide, shown at 321 px. Resized copies would save about 1.6 MB.

7d9ea842-6fda-4eac-8859-8d30b26a3bcf.png weighs 746 KiB. On a phone connection a single image that size takes seconds.

15 images (2.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.

magflow-us-banner_mo_0911_1536x.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).

5 images further down the page (418 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 4.05 g of CO₂e: 486.5 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”.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

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

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

ARIA role should be appropriate for the element: 10 elements on the page fail this check, rated minor by axe-core.

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https:files/ugreen_logo.svg")”.

1 link has no real href, so search engines can't follow it.

Your <h1> is empty.

The homepage links to 158 pages on ugreen.jp and 37 external pages.

There is no https://ugreen.jp/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://ugreen.jp/products/ugreen-160w-retractable-charger, https://ugreen.jp/products/ugreen-nexode-pro-160w-usb-c-charger, https://ugreen.jp/products/ugreen-100w-4-port-gan-charger and https://ugreen.jp/products/ugreen-nexode-300w-charger have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'setAttribute')”.

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 271 words of visible text.

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