Website review, no card needed
allinpay.com website review
Visit site (opens in a new tab)Reviewed 30 October 202657 issues · 85 checks
This review found 57 issues worth fixing on allinpay.com, 28 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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
42FClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
2.1 s
4.1 s
6.2 s
8.3 s
10.4 s
12.4 s
14.5 s
16.6 s
Speed
Use efficient cache lifetimes
5.7 s · 70.0 MB120 files are served with short cache lifetimes, so returning visitors download them again (70.0 MB).
Improve image delivery
2.8 s · 1.4 MB13 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.
Reduce unused JavaScript
2.3 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Render-blocking requests
2.7 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.7 s.
wowpop.cn adds 1.8 s
1.8 swowpop.cn costs a phone 1.8 s of main-thread work and 162 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Reduce unused CSS
1.4 s · 405 KiBAbout 405 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Font display
1.5 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.5 s).
Mobile performance score: 8
8/100Your mobile performance score is 8. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.7 s
A phone's processor spends 6.7 s on main-thread work while loading, 3.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,044 HTML elements
The page has 4,044 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 2.2 s. During a long task the page ignores taps.
4 third-party services on the page
4 third-party services load with your homepage (wowpop.cn, alicdn.com and Baidu Analytics and others), adding 291 KiB and 1.9 s of main-thread time.
Minify CSS
300 ms · 42 KiB42 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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
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: 46.6 s
46.6 sYour largest element takes 46.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “a1_banenrph02.jpg”.
Speed Index: 28.1 s
28.1 sVisually, the page fills in at 28.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 51.6 s
51.6 sThe page becomes fully interactive after 51.6 s. Good is under 3.8 s.
Total Blocking Time: 2.2 s
2.2 sScripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.541
0.541The layout shifts by 0.541 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
57 images without width and height
57 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.
Images and page weight
Page weight: 71.3 MB in 175 requests
71.3 MBYour homepage downloads 71.3 MB in 175 requests on a phone: media 54.0 MB (12), images 14.9 MB (100) and scripts 1.9 MB (31). Under 2 MB keeps phones on slow connections fast.
9 images over 500 KB
9 images weigh 7.7 MB together. On a phone connection a single image that size takes seconds.
18 images far larger than shown
7.1 MB18 images are downloaded at several times the size a phone draws them, for example 9041792732215.jpg at 1,244 px wide, shown at 231 px. Resized copies would save about 7.1 MB.
40 images in older formats
40 images (14.3 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.
24 images below the first screen load straight away
24 images further down the page (9.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 20.2 g of CO₂ per visit
20.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 20.21 g of CO₂e: 2425.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
30 text elements with low contrast
30 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
16 images without alt text
16 images have no alt text, which hurts accessibility and image search.
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
ARIA input fields do not have accessible names
ARIA input fields do not have accessible names (2 elements).
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements with role="none" or role="presentation" have conflicts
Elements with role="none" or role="presentation" have conflicts (1 element).
1 checks passed
29 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 33 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (4 characters)
Your title is only 4 characters: “通联支付”. 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.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (171 characters)
Your meta description is 171 characters; Google truncates after about 160, so the end of your pitch is cut.
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://www.allinpay.com/sitemap.xml, so Google discovers your pages only by following links.
16 links crawlers can't follow
16 links have no real href, so search engines can't follow them.
No robots.txt
There is no robots.txt at allinpay.com/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
124 internal links, 10 external
The homepage links to 124 pages on allinpay.com and 10 external pages.
1 checks passed
One H1 headline
Your main headline reads: “通联支付”.
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.
No llms.txt
There is no https://www.allinpay.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.
1 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Other pages
1 linked page is broken
Your homepage links to https://www.allinpay.com/product/center/enterprise/enterprise/11.html, which answers with an error. Visitors hit a dead end and search engines drop it.
8 pages without a meta description
https://www.allinpay.com/dynamic/news/corporate/14.html, https://www.allinpay.com/product/center.html, https://www.allinpay.com/product/activity/payment.html, https://www.allinpay.com/product/center/coopera/yinhang/27.html, https://www.allinpay.com/product/center/merchant/merchants/29.html and https://www.allinpay.com/solution.html and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://www.allinpay.com/solution/business/zhihuishangye/1.html, https://www.allinpay.com/solution/business/zhihuishangye/7.html, https://www.allinpay.com/solution/business/zhihuishangye/9.html and https://www.allinpay.com/solution/business/zhihuishangye/8.html use the same meta description. A description written for each page earns more clicks.
14 pages with very little text
https://www.allinpay.com/dynamic/news/corporate/14.html, https://www.allinpay.com/product/center.html, https://www.allinpay.com/product/activity/payment.html, https://www.allinpay.com/product/activity/e-marketing.html, https://www.allinpay.com/product/activity/digital-tech.html and https://www.allinpay.com/product/center/coopera/yinhang/27.html and 8 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
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 14 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://www.allinpay.com/__PUBLIC__/images/arrow01.png.
16 small tap targets
16 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
Only about 11 words
The homepage has only about 11 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
1 checks passed
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Privacy and tracking
4 cookies set on arrival
4Opening the homepage sets 4 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.
4 other companies contacted
Loading the homepage contacts 4 hosts 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 allinpay.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 57 issues on allinpay.com, including 20 speed issues, 8 SEO issues and 5 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.