Website review, no card needed
cdpgroupltd.com website review
Visit site (opens in a new tab)Reviewed 27 October 202644 issues · 79 checks
This review found 44 issues worth fixing on cdpgroupltd.com, 14 of them high impact, across 79 checks. The most urgent: font display. 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 | 4.7 s |
| May 16, 2026 | 4.7 s |
| May 23, 2026 | 4.5 s |
| May 30, 2026 | 4.2 s |
| Jun 6, 2026 | 4.2 s |
| Jun 13, 2026 | 4.1 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 4.5 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 4.7 s |
| Aug 1, 2026 | 5.2 s |
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.2 s
2.4 s
3.7 s
4.9 s
6.1 s
7.3 s
8.5 s
9.7 s
Speed
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Reduce unused JavaScript
1.6 s · 315 KiBAbout 315 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Render-blocking requests
1.4 s32 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Improve image delivery
4.0 MB20 images could be 4.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 54
54/100Your mobile performance score is 54 (desktop: 86). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
650 ms · 290 KiB66 files are served with short cache lifetimes, so returning visitors download them again (290 KiB).
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, bcebos.com and Baidu Analytics and others), adding 810 KiB and 837 ms of main-thread time.
Google Tag Manager adds 635 ms
635 msGoogle Tag Manager costs a phone 635 ms of main-thread work and 512 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.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 306 ms. During a long task the page ignores taps.
Legacy JavaScript
35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 86 but mobile only 54. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 21.8 s
21.8 sYour largest element takes 21.8 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: 23.1 s
23.1 sThe page becomes fully interactive after 23.1 s. Good is under 3.8 s.
Speed Index: 9.4 s
9.4 sVisually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 448 ms
448 msScripts block taps and scrolling for 448 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.7 s to 5.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
1 checks passed
Cumulative Layout Shift: 0.019
0.019The layout barely moves while loading (CLS 0.019, good is under 0.1).
Images and page weight
Page weight: 6.7 MB in 128 requests
6.7 MBYour homepage downloads 6.7 MB in 128 requests on a phone: images 5.6 MB (54), scripts 848 KiB (33) and media 121 KiB (1). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.
11 images far larger than shown
2.5 MB11 images are downloaded at several times the size a phone draws them, for example 640f4a5d92786e5de81384438386a56f.png at 1,502 px wide, shown at 322 px. Resized copies would save about 2.5 MB.
22 images in older formats
22 images (4.8 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.
21 images below the first screen load straight away
21 images further down the page (4.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.9 g of CO₂ per visit
1.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.89 g of CO₂e: 226.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 67 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (24 characters)
Your title is only 24 characters: “CDP集团-AI赋能的全场景化HCM SaaS+”. Between 30 and 65 characters leaves room to say what you do and for whom.
151 internal links, 1 external
The homepage links to 151 pages on cdpgroupltd.com and 1 external page.
6 checks passed
Meta description: 125 characters
Your meta description is 125 characters: “CDP集团首创新一代AI赋能的HCM SaaS+模式,打造以员工为核心的WorkLife应用,提供全球薪酬管理、福利、招聘、共享服务中心、人才发展及劳动力管理等一站式服务。现已为120多个国家和地区的5000多家客户提供专业服务,覆盖45…”.
Canonical URL set
The canonical URL is https://www.cdpgroupltd.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.
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://www.cdpgroupltd.com/sitemap_index.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.
No llms.txt
There is no https://www.cdpgroupltd.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
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Other pages
1 linked page is broken
Your homepage links to https://www.cdpgroupltd.com/elementor-page-ai-lab, which answers with an error. Visitors hit a dead end and search engines drop it.
6 pages without a meta description
https://www.cdpgroupltd.com/ai-lab, https://www.cdpgroupltd.com/news/cdp%e9%9b%86%e5%9b%a2%e5%86%8d%e5%ba%a6%e8%a2%ab%e8%ae%a4%e8%af%81%e4%b8%ba2025-2026%e5%b9%b4%e5%ba%a6great-place-to-work-certified-%e4%bc%81%e4%b8%9a%e3%80%82, https://www.cdpgroupltd.com/customer-success, https://www.cdpgroupltd.com/partnership, https://www.cdpgroupltd.com/about-us and https://www.cdpgroupltd.com/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.cdpgroupltd.com/news/cdp%e9%9b%86%e5%9b%a2%e5%86%8d%e5%ba%a6%e8%a2%ab%e8%ae%a4%e8%af%81%e4%b8%ba2025-2026%e5%b9%b4%e5%ba%a6great-place-to-work-certified-%e4%bc%81%e4%b8%9a%e3%80%82, whose canonical is https://www.cdpgroupltd.com/news/7133. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
12 pages without an H1
https://www.cdpgroupltd.com/customer-success, https://www.cdpgroupltd.com/partnership, https://www.cdpgroupltd.com/about-us, https://www.cdpgroupltd.com/en, https://www.cdpgroupltd.com/contact-us and https://www.cdpgroupltd.com/hcm and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
13 pages with very little text
https://www.cdpgroupltd.com/ai-lab, https://www.cdpgroupltd.com/news/cdp%e9%9b%86%e5%9b%a2%e5%86%8d%e5%ba%a6%e8%a2%ab%e8%ae%a4%e8%af%81%e4%b8%ba2025-2026%e5%b9%b4%e5%ba%a6great-place-to-work-certified-%e4%bc%81%e4%b8%9a%e3%80%82, https://www.cdpgroupltd.com/customer-success, https://www.cdpgroupltd.com/partnership, https://www.cdpgroupltd.com/about-us and https://www.cdpgroupltd.com/contact-us and 7 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://www.cdpgroupltd.com/news/cdp%e9%9b%86%e5%9b%a2%e5%86%8d%e5%ba%a6%e8%a2%ab%e8%ae%a4%e8%af%81%e4%b8%ba2025-2026%e5%b9%b4%e5%ba%a6great-place-to-work-certified-%e4%bc%81%e4%b8%9a%e3%80%82, https://www.cdpgroupltd.com/customer-success, https://www.cdpgroupltd.com/contact-us and https://www.cdpgroupltd.com/hcm took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.
3 checks passed
Titles are unique
Every page we checked has its own title.
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
8 small tap targets
8 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
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.
Only about 42 words
The homepage has only about 42 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.
3 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
15 other companies contacted
Loading the homepage contacts 15 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 cdpgroupltd.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
- Alibaba Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on cdpgroupltd.com, including 16 speed issues, 2 SEO issues and 4 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.