Website review, no card needed
gpbatteries.cn website review
Visit site (opens in a new tab)Reviewed 7 November 202638 issues · 81 checks
This review found 38 issues worth fixing on gpbatteries.cn, 9 of them high impact, across 81 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
73C- #92,550 of 125,463 reviewed websitesbeats 23%
- #57,382 of 70,188 online storesbeats 15%
- #53,638 of 63,770 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
2.5 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Reduce unused JavaScript
900 ms · 189 KiBAbout 189 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and Cloudflare CDN and others), adding 6.5 MB and 264 ms of main-thread time.
Reduce unused CSS
600 ms · 111 KiBAbout 111 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.
Improve image delivery
100 ms · 581 KiB3 images could be 581 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.
Shopify adds 107 ms
107 msShopify costs a phone 107 ms of main-thread work and 5.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.
Google Fonts adds 2 ms
2 msGoogle Fonts costs a phone 2 ms of main-thread work and 933 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 120 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
100 ms · 9 KiB6 files are served with short cache lifetimes, so returning visitors download them again (9 KiB).
Legacy JavaScript
100 ms · 7 KiBPolyfills for old browsers add 7 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
10 KiB10 KiB could be saved by minifying CSS.
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.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 574 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.7 s
12.7 sYour largest element takes 12.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 12.8 s
12.8 sThe page becomes fully interactive after 12.8 s. Good is under 3.8 s.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 155 ms
155 msScripts block the page for only 155 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.016
0.016The layout barely moves while loading (CLS 0.016, good is under 0.1).
Images and page weight
Page weight: 8.5 MB in 207 requests
8.5 MBYour homepage downloads 8.5 MB in 207 requests on a phone: media 4.9 MB (5), images 1.0 MB (17) and fonts 1.0 MB (19). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
img-hp-stn01a-mb.gif weighs 2.1 MB. On a phone connection a single image that size takes seconds.
1 image in older formats
1 image (2.1 MB) is 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.
An image on the first screen is lazy-loaded
img-hp-banner03-mb.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).
About 2.4 g of CO₂ per visit
2.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.42 g of CO₂e: 290.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
4 elements use ARIA attributes their role does not allow, which confuses screen readers.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (14 elements)
All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 32 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (19 characters)
Your title is only 19 characters: “GP超霸中国 | 超过50年的电池专家”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (60 characters)
Your meta description is only 60 characters: “GP超霸是国际性电池品牌,专注产品研发超过50多年,致力于为大众提供安全可靠的一次性电池、充电电池、特种电池及充电器等。”. 70 to 160 characters is enough to sell the click.
Structured data has 1 problem
Structured data found (BreadcrumbList and WebSite) but with 1 problem, for example “BreadcrumbList: itemListElement is an empty list”.
8 links crawlers can't follow
8 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
71 internal links, 46 external
The homepage links to 71 pages on gpbatteries.cn and 46 external pages.
5 checks passed
One H1 headline
Your main headline reads: “全新升级碱性电池系列”.
Canonical URL set
The canonical URL is https://gpbatteries.cn/.
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.
XML sitemap found
Your XML sitemap is reachable at https://gpbatteries.cn/sitemap.xml.
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.
2 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.
llms.txt published
The site publishes https://gpbatteries.cn/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 linked pages hidden from search
https://gpbatteries.cn/collections/single-use-batteries/category_aa-batteries, https://gpbatteries.cn/collections/single-use-batteries/category_aaa-batteries, https://gpbatteries.cn/collections/single-use-batteries/category_c-d-batteries, https://gpbatteries.cn/collections/single-use-batteries/category_9v-batteries and https://gpbatteries.cn/collections/single-use-batteries/category_others-batteries are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
6 pages share a title
https://gpbatteries.cn/collections/single-use-batteries, https://gpbatteries.cn/collections/single-use-batteries/category_aa-batteries, https://gpbatteries.cn/collections/single-use-batteries/category_aaa-batteries, https://gpbatteries.cn/collections/single-use-batteries/category_c-d-batteries, https://gpbatteries.cn/collections/single-use-batteries/category_9v-batteries and https://gpbatteries.cn/collections/single-use-batteries/category_others-batteries all use the title “一次性电池 | GP超霸中国”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://gpbatteries.cn/collections/power-thru-chargers, https://gpbatteries.cn/collections/rechargeable-batteries, https://gpbatteries.cn/collections/battery-chargers-charger-docks, https://gpbatteries.cn/collections/coin-button-cell-batteries, https://gpbatteries.cn/collections/hearing-aid-batteries and https://gpbatteries.cn/collections/cylindrical-batteries and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages share a meta description
https://gpbatteries.cn/collections/single-use-batteries, https://gpbatteries.cn/collections/single-use-batteries/category_aa-batteries, https://gpbatteries.cn/collections/single-use-batteries/category_aaa-batteries, https://gpbatteries.cn/collections/single-use-batteries/category_c-d-batteries, https://gpbatteries.cn/collections/single-use-batteries/category_9v-batteries and https://gpbatteries.cn/collections/single-use-batteries/category_others-batteries use the same meta description. A description written for each page earns more clicks.
10 pages with very little text
https://gpbatteries.cn/collections/single-use-batteries, https://gpbatteries.cn/collections/power-thru-chargers, https://gpbatteries.cn/collections/rechargeable-batteries, https://gpbatteries.cn/collections/battery-chargers-charger-docks, https://gpbatteries.cn/collections/coin-button-cell-batteries and https://gpbatteries.cn/collections/hearing-aid-batteries and 4 others 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.
4 pages slow to respond
https://gpbatteries.cn/collections/single-use-batteries/category_9v-batteries, https://gpbatteries.cn/collections/single-use-batteries/category_others-batteries, https://gpbatteries.cn/collections/power-thru-chargers and https://gpbatteries.cn/collections/rechargeable-batteries took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.
4 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
9 small tap targets
9 of 28 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 22 words
The homepage has only about 22 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us”.
2 calls to action
The homepage has 2 calls to action, for example “Contact Us” and “Subscribe”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and 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.
10 cookies set on arrival
10Opening the homepage sets 10 cookies (measured from a US location before any click).
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.
16 other companies contacted
Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 gpbatteries.cn, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Gdpr Backpack
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
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 gpbatteries.cn, including 13 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.