gweikecloud.com website review

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

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

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

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

8 third-party services load with your homepage (PayPal, Unpkg and Facebook and others), adding 11.2 MB and 1.4 s of main-thread time.

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

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

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

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

PayPal costs a phone 380 ms of main-thread work and 395 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.

Unpkg costs a phone 338 ms of main-thread work and 271 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.

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

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

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

Polyfills for old browsers add 46 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.

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.28 (75th percentile). Good is under 0.1.

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

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

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

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

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

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

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

Your homepage downloads 15.2 MB in 362 requests on a phone: media 9.2 MB (6), images 2.4 MB (95) and scripts 2.0 MB (103). Under 2 MB keeps phones on slow connections fast.

blackfriday-banner-index-m.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).

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

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

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

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

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

Your title is 74 characters, so Google will cut it off around 60: “Desktop Laser Engraver Cutter Machine Home Wood 3D Diy Shop – gweike cloud”.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

Your <h1> is empty.

The homepage links to 165 pages on gweikecloud.com and 39 external pages.

/policies/shipping-policy, /pages/black-friday, /collections/fiber-laser, /collections/6-in-1 and /collections/mcore-laser have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/machine, /pages/black-friday, /products/g2-pro-fiber-laser-engraver, /products/g2-fiber-laser-marking-machine, /products/g2-50w-fiber-laser-engraver and /products/g6-mopa-30w-60w-100w-fiber-laser-marking-engraving-machine and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

/products/m-core took over 3 s to send its HTML from our server.

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

3 images failed to load on a phone, for example https://www.gweikecloud.com/.

5 errors were logged to the browser console while the page loaded, for example “Replace_with_Variable_Revenue_Function is not defined”.

14 images are served at too low a resolution for sharp phone screens.

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

Social proof on the homepage: 16 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.

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

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