Website review, no card needed
cmfchina.com website review
Visit site (opens in a new tab)Reviewed 22 October 202650 issues · 82 checks
This review found 50 issues worth fixing on cmfchina.com, 18 of them high impact, across 82 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
62DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
14.6 s · 9.5 MB133 files are served with short cache lifetimes, so returning visitors download them again (9.5 MB).
Render-blocking requests
7.5 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.5 s.
Reduce unused JavaScript
2.3 s · 445 KiBAbout 445 KiB 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.
Reduce unused CSS
2.3 s · 369 KiBAbout 369 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Mobile performance score: 46
46/100Your mobile performance score is 46 (desktop: 57). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
150 ms · 2.0 MB13 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
2,113 HTML elements
The page has 2,113 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 548 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1 third-party service on the page
1 third-party service load with your homepage (mi.com), adding 1.0 MB and 0 ms of main-thread time.
mi.com adds 0 ms
0 msmi.com costs a phone 0 ms of main-thread work and 1.0 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 147 ms. During a long task the page ignores taps.
Legacy JavaScript
32 KiBPolyfills for old browsers add 32 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: 243 ms
243 msYour server sent the HTML in 243 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 9.3 s
9.3 sThe first text or image appears after 9.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 35.3 s
35.3 sYour largest element takes 35.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “为您提供,一流的资产管理服务 13.10亿 注册资本 2800+亿 累计为客户盈利 1.90亿 服务客户数 5500+…”.
Speed Index: 16.3 s
16.3 sVisually, the page fills in at 16.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 36.9 s
36.9 sThe page becomes fully interactive after 36.9 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.2
0.2The layout shifts by 0.2 while loading, so content jumps under the reader's thumb. Good is under 0.1.
2 images without width and height
2 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.
1 checks passed
Total Blocking Time: 30 ms
30 msScripts block the page for only 30 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 10.5 MB in 142 requests
10.5 MBYour homepage downloads 10.5 MB in 142 requests on a phone: images 7.7 MB (42), scripts 1.3 MB (50) and fonts 1.0 MB (37). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 4.4 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
894 KiB5 images are downloaded at several times the size a phone draws them, for example hm_adv_img01.jpg at 2,304 px wide, shown at 460 px. Resized copies would save about 894 KiB.
8 images in older formats
8 images (3.2 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.
2 images below the first screen load straight away
2 images further down the page (1.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.0 g of CO₂ per visit
2.97 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.97 g of CO₂e: 356.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
41 images without alt text
41 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 elements on the page fail 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.
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.
7 links without text
7 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.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
16 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 25 WCAG 2.2 A/AA and best-practice rules on the phone render: 16 passed and 9 failed. 2 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.
63 links crawlers can't follow
63 links have no real href, so search engines can't follow them.
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://cmfchina.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at cmfchina.com/robots.txt, the first file search crawlers ask for.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
84 internal links, 118 external
The homepage links to 84 pages on cmfchina.com and 118 external pages.
2 checks passed
Meta description: 136 characters
Your meta description is 136 characters: “基金购买,就选招商基金!招商基金管理有限公司是中国第一家中外合资基金管理公司,经过二十余年的规范运作、稳健经营,招商基金在公募基金、社保基金、年金、养老金、QDII、特定客户资产管理等各个资产管理业务领域均取得了长足进展,成长为国内业务资…”.
Title: 50 characters
Your title is a healthy 50 characters: “招商基金管理有限公司-基金购买|招商基金APP下载|养老有招|招商基金网上交易-为投资者创造更多价值”.
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://cmfchina.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
8 pages share a title
/, https://cmfchina.com/web/elderlyCare/securityPension/index.html, https://cmfchina.com/web/elderlyCare/enterprisePension/index.html, https://cmfchina.com/web/elderlyCare/personalPension/index.html, https://cmfchina.com/web/esg/infopublish/esgreport/index.html and https://cmfchina.com/web/esg/infopublish/esgnews/index.html and 2 others all use the title “招商基金管理有限公司-基金购买|招商基金APP下载|养老有招|招商基金网上交易-为投资者创造更多价值”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages share a meta description
https://cmfchina.com/web/elderlyCare/securityPension/index.html, https://cmfchina.com/web/elderlyCare/enterprisePension/index.html, https://cmfchina.com/web/elderlyCare/personalPension/index.html, https://cmfchina.com/web/esg/infopublish/esgreport/index.html, https://cmfchina.com/web/esg/infopublish/esgnews/index.html and https://cmfchina.com/web/esg/infopublish/publicwelfare/index.html and 1 other use the same meta description. A description written for each page earns more clicks.
7 pages without an H1
https://cmfchina.com/web/elderlyCare/securityPension/index.html, https://cmfchina.com/web/elderlyCare/enterprisePension/index.html, https://cmfchina.com/web/elderlyCare/personalPension/index.html, https://cmfchina.com/web/esg/infopublish/esgreport/index.html, https://cmfchina.com/web/esg/infopublish/esgnews/index.html and https://cmfchina.com/web/esg/infopublish/publicwelfare/index.html and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages with very little text
https://cmfchina.com/web/elderlyCare/securityPension/index.html, https://cmfchina.com/web/elderlyCare/enterprisePension/index.html, https://cmfchina.com/web/elderlyCare/personalPension/index.html, https://cmfchina.com/web/esg/infopublish/esgreport/index.html, https://cmfchina.com/web/esg/infopublish/esgnews/index.html and https://cmfchina.com/web/esg/infopublish/publicwelfare/index.html and 1 other 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://cmfchina.com/web/elderlyCare/securityPension/index.html, https://cmfchina.com/web/elderlyCare/enterprisePension/index.html, https://cmfchina.com/web/elderlyCare/personalPension/index.html and https://cmfchina.com/web/esg/infopublish/esgreport/index.html took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.
5 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 7 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 7 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
18 of 19 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
Only about 36 words
The homepage has only about 36 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.
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 cmfchina.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on cmfchina.com, including 16 speed issues, 8 SEO issues and 6 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.