Website review, no card needed

microvast.com logo

microvast.com website review

Visit site (opens in a new tab)Reviewed 17 November 202638 issues · 73 checks

This review found 38 issues worth fixing on microvast.com, 13 of them high impact, across 73 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.9 s1.5 sMay 30Nov 142.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20262.2 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.9 s
Aug 1, 20262.7 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.7 s
Aug 29, 20263.0 s
Sep 5, 20263.1 s
Sep 12, 20263.6 s
Sep 19, 20263.2 s
Sep 26, 20263.0 s
Oct 3, 20262.8 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Oct 24, 20262.8 s
Oct 31, 20262.8 s
Nov 7, 20262.6 s
Nov 14, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
88 ms68 msMay 30Nov 1479 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202682 ms
Jun 6, 202683 ms
Jun 13, 202677 ms
Jun 20, 202686 ms
Jun 27, 202685 ms
Jul 4, 202677 ms
Jul 11, 202672 ms
Jul 18, 202673 ms
Jul 25, 202670 ms
Aug 1, 202673 ms
Aug 8, 202675 ms
Aug 15, 202672 ms
Aug 22, 202674 ms
Aug 29, 202674 ms
Sep 5, 202670 ms
Sep 12, 202675 ms
Sep 19, 202676 ms
Sep 26, 202672 ms
Oct 3, 202672 ms
Oct 10, 202676 ms
Oct 17, 202674 ms
Oct 24, 202681 ms
Oct 31, 202682 ms
Nov 7, 202676 ms
Nov 14, 202679 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of microvast.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. microvast.com at 0.4 s0.4 s
  2. microvast.com at 0.8 s0.8 s
  3. microvast.com at 1.1 s1.1 s
  4. microvast.com at 1.5 s1.5 s
  5. microvast.com at 1.9 s1.9 s
  6. microvast.com at 2.3 s2.3 s
  7. microvast.com at 2.6 s2.6 s
  8. microvast.com at 3.0 s3.0 s

Speed

6 to fix69
  • Use efficient cache lifetimes

    12.8 s · 8.6 MB

    18 files are served with short cache lifetimes, so returning visitors download them again (8.6 MB).

  • Improve image delivery

    12.4 s · 8.3 MB

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

  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 69

    69/100

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

  • Reduce unused JavaScript

    750 ms · 148 KiB

    About 148 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Reduce unused CSS

    600 ms · 105 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 101 ms. During a long task the page ignores taps.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 checks passed
  • Main-thread work: 0.5 s

    A phone's processor spends 0.5 s on main-thread work while loading, 150 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 33.5 s

    33.5 s

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

  • Time to Interactive: 35.1 s

    35.1 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user CLS: 0.22

    0.22

    For real visitors the layout shifts by 0.22 (75th percentile). Good is under 0.1.

  • Largest content (LCP) got 45% slower for real visitors

    +45%

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 804 ms

    804 ms

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

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • Speed Index: 4.3 s

    4.3 s

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

  • 11 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

3 checks passed
  • Real-user INP: 75 ms

    75 ms

    Real visitors wait 75 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 51 ms

    51 ms

    Scripts block the page for only 51 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix28
  • Page weight: 9.4 MB in 34 requests

    9.4 MB

    Your homepage downloads 9.4 MB in 34 requests on a phone: images 8.6 MB (18), scripts 453 KiB (9) and stylesheets 316 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 4.7 MB together. On a phone connection a single image that size takes seconds.

  • 7 images in older formats

    7 images (5.4 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.

  • 8 images below the first screen load straight away

    8 images further down the page (5.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    61 KiB

    1 image is downloaded at several times the size a phone draws it, for example new-about-driving.webp at 1,432 px wide, shown at 390 px. Resized copies would save about 61 KiB.

  • About 2.7 g of CO₂ per visit

    2.67 g

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

Accessibility

Google 100100
2 checks passed
  • Every image has alt text

    All 25 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 5056
  • robots.txt blocks all crawlers

    Your robots.txt disallows the whole site for every crawler, so search engines are told to stay out.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://microvast.com/sitemap.xml, so Google discovers your pages only by following links.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 25 internal links, 4 external

    The homepage links to 25 pages on microvast.com and 4 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “Forward Thinking. Powering Now.™”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Microvast - Industrial Lithium-ion Battery Solutions”.

AI search readiness

2 to fix53
  • robots.txt blocks 6 AI answer engine crawlers

    6 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No Organization structured data

    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.

  • No llms.txt

    There is no https://microvast.com/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.

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (275 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 15 pages share a title

    /, https://microvast.com/company, https://microvast.com/sectors/transportation, https://microvast.com/sectors/specialty, https://microvast.com/sectors/kfa-school-bus-solutions and https://microvast.com/future/energy-storage and 9 others all use the title “Microvast - Industrial Lithium-ion Battery Solutions”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    https://microvast.com/company, https://microvast.com/sectors/transportation, https://microvast.com/sectors/specialty, https://microvast.com/sectors/kfa-school-bus-solutions, https://microvast.com/future/energy-storage and https://microvast.com/future/data-centers and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages with very little text

    https://microvast.com/batteries/cells, https://microvast.com/batteries/modules and https://microvast.com/batteries/packs 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.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Loading media from 'https://d3pqhi7e4wht1s.cloudfront.net/Microvast_School_Bus_Promo-ENG-60S.mp4' violates the followin…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

    9 of 9 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • No social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

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

  • No risk reducer

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

  • About 263 words of copy

    The homepage carries about 263 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “LEARN MORE”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “CONTACT”, “LEARN MORE” and “Contact Us”.

Privacy and tracking

  • No consent tool detected

    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.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at microvast.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Azure

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on microvast.com, including 17 speed issues, 8 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25