jangyao.com website review

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

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

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

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

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

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

46 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

8 third-party services load with your homepage (Shopify, pop-convert.com and Google CDN and others), adding 1.9 MB and 866 ms of main-thread time.

Shopify costs a phone 408 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.

pop-convert.com costs a phone 279 ms of main-thread work and 279 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 122 ms of main-thread work and 298 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.

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

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

5 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

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

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 29.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “David in Tennessee United StatesPurchased DJI Osmo Pocket 4…”.

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

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.4 MB in 499 requests on a phone: other files 2.6 MB (251), scripts 1.8 MB (151) and images 1.5 MB (70). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

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

Your title is only 7 characters: “JANGYAO”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 372 pages on jangyao.com and 10 external pages.

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

https://jangyao.com/blogs/news, https://jangyao.com/blogs/buying-guide and https://jangyao.com/blogs/official-notes have no meta description, so Google writes the search snippet from whatever text it finds.

https://jangyao.com/products/insta360-snap-vlog-screen-upgrade-phone-to-pro-camera-magnetic-rear-camera-selfie-monitor-with-touch-control, https://jangyao.com/collections/antigravity-a1, https://jangyao.com/collections/autel-evo-lite-series and https://jangyao.com/collections/autel-evo-lite took over 3 s to send their HTML from our server.

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

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: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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