rhinoshield.tw website review

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

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

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

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

8 third-party services load with your homepage (ZenDesk, Klaviyo and Salesforce.com and others), adding 1.9 MB and 190 ms of main-thread time.

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

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

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

Google Fonts costs a phone 2 ms of main-thread work and 1.3 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.

ZenDesk costs a phone 86 ms of main-thread work and 355 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 175 ms. During a long task the page ignores taps.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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.

5 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 41.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “為 iPhone 18 Pro 而生”.

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

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

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

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

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

9 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 249 ms to 237 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.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.1 MB in 314 requests on a phone: images 5.7 MB (78), other files 2.3 MB (74) and scripts 1.6 MB (130). Under 2 MB keeps phones on slow connections fast.

23 images are downloaded at several times the size a phone draws them, for example product-card_impact-protector_0901.png at 1,000 px wide, shown at 117 px. Resized copies would save about 2.4 MB.

14 images (1.5 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.

1 image further down the page (123 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is only 22 characters: “官方網站 | RHINOSHIELD 犀牛盾”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

The homepage links to 71 pages on rhinoshield.tw and 15 external pages.

There is no https://rhinoshield.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://rhinoshield.tw/ditto/customize is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://rhinoshield.tw/ditto/customize all use the title “官方網站 | RHINOSHIELD 犀牛盾”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://rhinoshield.tw/ditto/customize has no <h1> headline, so visitors and search engines get no clear main topic.

https://rhinoshield.tw/design-studio, https://rhinoshield.tw/rhinoloop, https://rhinoshield.tw/products/airx, https://rhinoshield.tw/products/bumper/buy, https://rhinoshield.tw/products/clearx and https://rhinoshield.tw/products/bumper and 5 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.

We fetched 15 pages linked from your homepage (of 49 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.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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: 6 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 107 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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

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