xpeng.com website review

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

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

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

Your mobile performance score is 37. 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, Optanon and Amazon Web Services and others), adding 1.7 MB and 1.0 s of main-thread time.

Google Tag Manager costs a phone 816 ms of main-thread work and 1.2 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 41 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

1 image could be 50 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. 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.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Optanon costs a phone 101 ms of main-thread work and 294 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 100 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 240 ms faster on a phone.

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

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

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 17.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Compagny and its partners use cookies and similar technolog…”.

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

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

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

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

Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

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

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

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

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

Your homepage downloads 2.9 MB in 139 requests on a phone: scripts 2.5 MB (68), images 120 KiB (23) and HTML 101 KiB (2). Under 2 MB keeps phones on slow connections fast.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

6 links have no real href, so search engines can't follow them.

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

The homepage links to 51 pages on xpeng.com and 9 external pages.

Your Organization JSON-LD is missing 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://www.xpeng.com/technology/ai_cars, https://www.xpeng.com/technology/ai_robot_iron, https://www.xpeng.com/technology/flying_cars, https://www.xpeng.com/technology/turing_ai_chip, https://www.xpeng.com/ai-engineering and https://www.xpeng.com/model/p7plus all use the title “XPENG - Official Website | XPENG Motors – XPENG”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.xpeng.com/technology/ai_cars, https://www.xpeng.com/technology/ai_robot_iron, https://www.xpeng.com/technology/flying_cars, https://www.xpeng.com/technology/turing_ai_chip, https://www.xpeng.com/ai-engineering and https://www.xpeng.com/model/p7plus use the same meta description. A description written for each page earns more clicks.

https://www.xpeng.com/technology/ai_cars, https://www.xpeng.com/technology/ai_robot_iron, https://www.xpeng.com/technology/flying_cars, https://www.xpeng.com/technology/turing_ai_chip, https://www.xpeng.com/ai-engineering and https://www.xpeng.com/model/p7plus and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.xpeng.com/technology/ai_robot_iron, https://www.xpeng.com/technology/turing_ai_chip, https://www.xpeng.com/ai-engineering and https://www.xpeng.com/model/p7plus took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 27 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 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 221 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 Tag Manager (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 2 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 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.