2bm.com.tw website review

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

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

cybassets.com costs a phone 1.0 s of main-thread work and 5.5 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.

Google Tag Manager costs a phone 1.1 s of main-thread work and 1.5 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 17. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 third-party services load with your homepage (Google Tag Manager, cybassets.com and TikTok and others), adding 9.9 MB and 2.3 s of main-thread time.

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

9 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

meee.com.tw costs a phone 0 ms of main-thread work and 1.5 MB 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 Fonts costs a phone 1 ms of main-thread work and 1.1 MB 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.

Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

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

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.

4 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your homepage downloads 10.3 MB in 146 requests on a phone: images 4.9 MB (41), scripts 4.1 MB (50) and fonts 1.1 MB (19). Under 2 MB keeps phones on slow connections fast.

W1siZiIsIjMzMzAwL2F0dGFjaGVkX3Bob3Rvcy8xNzg3MDI5OTQ0XzIwMjYt weighs 630 KiB. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example W1siZiIsIjMzMzAwL2F0dGFjaGVkX3Bob3Rvcy8xNzkwMDU1MjI0XzIwMjYt at 3,125 px wide, shown at 390 px. Resized copies would save about 807 KiB.

12 images (1.7 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.

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

ARIA attributes must conform to valid values: 10 elements on the page fail this check, rated critical by axe-core.

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

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

Interactive controls must not be nested: 10 elements on the page fail this check, rated serious by axe-core.

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

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

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

11 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 27 characters: “母子鱷魚 ｜氣墊拖鞋・跑步拖鞋・輕量舒適・台灣永續品牌”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: missing name”.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 188 pages on 2bm.com.tw and 6 external pages.

Your Organization JSON-LD is missing name, 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.

There is no https://www.2bm.com.tw/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://www.2bm.com.tw/categories/special-offers, https://www.2bm.com.tw/categories/%E5%BF%85%E9%80%9B%E4%B8%BB%E9%A1%8C, https://www.2bm.com.tw/categories/slippers-sandals, https://www.2bm.com.tw/categories/clogs, https://www.2bm.com.tw/categories/sports and https://www.2bm.com.tw/categories/hiking and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.2bm.com.tw/categories/special-offers, https://www.2bm.com.tw/categories/%E5%BF%85%E9%80%9B%E4%B8%BB%E9%A1%8C, https://www.2bm.com.tw/categories/slippers-sandals, https://www.2bm.com.tw/categories/clogs, https://www.2bm.com.tw/categories/sports and https://www.2bm.com.tw/categories/hiking and 9 others have 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://www.2bm.com.tw/categories/accessories and https://www.2bm.com.tw/products/2bmbag took over 3 s to send their HTML from our server.

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

5 errors were logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Unexpected token '}'”.

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

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.

Social proof on the homepage: 2 trust badges. 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 has only about 58 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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 17 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.