Website review, no card needed
a123systems.com website review
Visit site (opens in a new tab)Reviewed 29 October 202631 issues · 65 checks
This review found 31 issues worth fixing on a123systems.com, 12 of them high impact, across 65 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.8 s |
| May 16, 2026 | 5.8 s |
| May 23, 2026 | 5.8 s |
| May 30, 2026 | 5.6 s |
| Jun 6, 2026 | 5.3 s |
| Jun 13, 2026 | 5.6 s |
| Jun 20, 2026 | 6.1 s |
| Jun 27, 2026 | 6.4 s |
| Jul 4, 2026 | 6.3 s |
| Jul 11, 2026 | 6.1 s |
| Jul 18, 2026 | 5.8 s |
| Jul 25, 2026 | 5.4 s |
| Aug 1, 2026 | 5.4 s |
| Aug 8, 2026 | 5.4 s |
| Aug 15, 2026 | 5.1 s |
| Aug 22, 2026 | 5.0 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 4.7 s |
| Sep 12, 2026 | 4.7 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.8 s |
| Oct 3, 2026 | 4.9 s |
| Oct 10, 2026 | 5.1 s |
| Oct 17, 2026 | 5.0 s |
| Oct 24, 2026 | 4.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 95 ms |
| May 16, 2026 | 98 ms |
| May 23, 2026 | 99 ms |
| May 30, 2026 | 101 ms |
| Jun 6, 2026 | 100 ms |
| Jun 13, 2026 | 108 ms |
| Jun 20, 2026 | 96 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 102 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 105 ms |
| Jul 25, 2026 | 105 ms |
| Aug 1, 2026 | 102 ms |
| Aug 8, 2026 | 94 ms |
| Aug 15, 2026 | 89 ms |
| Aug 22, 2026 | 89 ms |
| Aug 29, 2026 | 91 ms |
| Sep 5, 2026 | 101 ms |
| Sep 12, 2026 | 97 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 97 ms |
| Oct 3, 2026 | 97 ms |
| Oct 10, 2026 | 97 ms |
| Oct 17, 2026 | 95 ms |
| Oct 24, 2026 | 90 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
How it loaded on a phone
1.3 s
2.6 s
3.9 s
5.2 s
6.6 s
7.9 s
9.2 s
10.5 s
Speed
Render-blocking requests
2.9 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Mobile performance score: 46
46/100Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5 third-party services on the page
5 third-party services load with your homepage (Hubspot, Cloudflare CDN and yun300.cn and others), adding 10.9 MB and 181 ms of main-thread time.
Improve image delivery
1.1 MB5 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
thefastimg.com adds 0 ms
0 msthefastimg.com costs a phone 0 ms of main-thread work and 10.8 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 413 ms. During a long task the page ignores taps.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Reduce unused CSS
150 ms · 25 KiBAbout 25 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
171 KiB48 files are served with short cache lifetimes, so returning visitors download them again (171 KiB).
Reduce unused JavaScript
47 KiBAbout 47 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
38 KiBPolyfills for old browsers add 38 KiB JavaScript that modern phones do not need.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 112 ms
112 msYour server sent the HTML in 112 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user LCP: 5.2 s
5.2 sReal visitors wait 5.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.2 s
4.2 sReal visitors see the first content after 4.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.0 s
3.0 sReal visitors wait 3.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 13.4 s
13.4 sYour largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Main Business”.
Time to Interactive: 13.4 s
13.4 sThe page becomes fully interactive after 13.4 s. Good is under 3.8 s.
Speed Index: 8.9 s
8.9 sVisually, the page fills in at 8.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 873 ms
873 msScripts block taps and scrolling for 873 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 95 ms to 90 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 89 ms
89 msReal visitors wait 89 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.8 s to 4.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.013
0.013The layout barely moves while loading (CLS 0.013, good is under 0.1).
Images and page weight
Page weight: 11.3 MB in 111 requests
11.3 MBYour homepage downloads 11.3 MB in 111 requests on a phone: images 10.8 MB (48), scripts 409 KiB (32) and stylesheets 80 KiB (15). Under 2 MB keeps phones on slow connections fast.
About 3.2 g of CO₂ per visit
3.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.21 g of CO₂e: 384.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
2 checks passed
Every image has alt text
All 60 images in the HTML carry an alt attribute.
4 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 4 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (26 characters)
Your title is only 26 characters: “Wanxiang A123 Systems Corp”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Main Business” and “A123 Systems world-wide”). One clear main headline is easier for people and search engines.
Meta description is long (211 characters)
Your meta description is 211 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://www.a123systems.com/sitemap.xml, so Google discovers your pages only by following links.
112 internal links, 5 external
The homepage links to 112 pages on a123systems.com and 5 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.a123systems.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
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.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
Your server turned our page checks away
15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 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 733 words of copy
The homepage carries about 733 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Us”.
Social proof on the page
Social proof on the homepage: 2 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: HubSpot.
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 other company contacted
Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 a123systems.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
- CHINA UNICOM China169 Backbone
Company
- Employees
- 1,100
- Founded
- 2001
- Headquarters
- Hangzhou
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on a123systems.com, including 16 speed issues, 5 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.