moztech.cc website review

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

8 third-party services load with your homepage (Shopify, easychat.co and zotabox.com and others), adding 26.3 MB and 876 ms of main-thread time.

Shopify costs a phone 452 ms of main-thread work and 25.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.

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

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

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

About 496 KiB of JavaScript is downloaded but never used on this page.

easychat.co costs a phone 280 ms of main-thread work and 587 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.

12 images could be 281 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.

12 long tasks block the main thread while loading, the longest for 242 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 21 KiB JavaScript that modern phones do not need.

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

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

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

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

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

7 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 118 ms to 130 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 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 28.4 MB in 471 requests on a phone: media 24.7 MB (4), scripts 1.6 MB (228) and other files 999 KiB (190). Under 2 MB keeps phones on slow connections fast.

20261030-_-banner-mob.jpg 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).

1 image is downloaded at several times the size a phone draws it, for example 05_2.png at 1,500 px wide, shown at 293 px. Resized copies would save about 45 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 8.05 g of CO₂e: 965.7 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: 2 elements on the page fail this check, rated critical by axe-core.

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

3 elements hidden from screen readers can still receive keyboard focus.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 6 <h1> headlines (“MOZTECH 墨子科技”, “霧面。高透。滑順。” and “萬能充MAX”). One clear main headline is easier for people and search engines.

The homepage links to 150 pages on moztech.cc 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.

/products/moztech-%E7%8D%A8%E5%AE%B6%E5%B0%88%E5%88%A9-%E6%99%B6%E9%9C%A7%E8%B2%BC-%E9%9B%BB%E7%AB%B6%E5%B0%88%E7%94%A8-iphone-%E4%BF%9D%E8%AD%B7%E8%B2%BC and /products/moztech-iphone16-series-mist all use the title “MOZTECH® 墨子科技｜【獨家專利】晶霧貼 電競專用 iPhone 保護貼 – MOZTECH 墨子科技”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/buy1get1, /collections/mist-glass-protector, /collections/privacy-screen-protector, /pages/%E8%B2%BC%E8%86%9C%E7%A5%9E%E5%99%A8%E4%BD%BF%E7%94%A8%E8%AA%AA%E6%98%8E, /products/iphone-18-series-3d-mist-glassprotector and /products/iphone-17-series-3d-cold-sculpture-crystal-mist-gaming-screen-protector and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

/products/moztech-%E7%8D%A8%E5%AE%B6%E5%B0%88%E5%88%A9-%E6%99%B6%E9%9C%A7%E8%B2%BC-%E9%9B%BB%E7%AB%B6%E5%B0%88%E7%94%A8-iphone-%E4%BF%9D%E8%AD%B7%E8%B2%BC and /products/moztech-iphone16-series-mist use the same meta description. A description written for each page earns more clicks.

Your homepage links to 6 pages by a URL that isn't their canonical one, for example /collections/%E6%89%80%E6%9C%89%E5%95%86%E5%93%81, whose canonical is /collections/%e6%89%80%e6%9c%89%e5%95%86%e5%93%81. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/collections/%E6%89%80%E6%9C%89%E5%95%86%E5%93%81, /collections/mist-glass-protector, /collections/privacy-screen-protector, /collections/%E7%84%A1%E8%89%B2%E6%8A%97%E8%97%8D%E5%85%89%E6%99%B6%E9%9C%A7%E8%B2%BC, /collections/moztech-%E4%BF%9D%E8%AD%B7%E8%B2%BC%E7%B3%BB%E5%88%97 and /pages/%E8%B2%BC%E8%86%9C%E7%A5%9E%E5%99%A8%E4%BD%BF%E7%94%A8%E8%AA%AA%E6%98%8E have no <h1> headline, so visitors and search engines get no clear main topic.

/pages/%E8%B2%BC%E8%86%9C%E7%A5%9E%E5%99%A8%E4%BD%BF%E7%94%A8%E8%AA%AA%E6%98%8E 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.

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

2 errors were logged to the browser console while the page loaded, for example “The Content Security Policy directive 'frame-ancestors' is ignored when delivered via a <meta> element.”.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

moztech.cc's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 178 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.

DMARC is set to p=none, so mail pretending to be moztech.cc is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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