Website review, no card needed
yuhong.com.cn website review
Visit site (opens in a new tab)Reviewed 29 October 202648 issues · 87 checks
This review found 48 issues worth fixing on yuhong.com.cn, 19 of them high impact, across 87 checks. The most urgent: improve image delivery. 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
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 2.9 s |
| Jun 13, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 3.2 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.3 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.5 s
3.0 s
4.5 s
6.0 s
7.4 s
8.9 s
10.4 s
11.9 s
Speed
Improve image delivery
3.4 s · 2.4 MB20 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.4 s faster on a phone.
Render-blocking requests
4.1 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.1 s.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Use efficient cache lifetimes
350 ms · 1.3 MB14 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
150 ms · 55 KiBAbout 55 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.
Minify CSS
150 ms · 11 KiB11 KiB could be saved by minifying CSS.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 91 ms. During a long task the page ignores taps.
1 third-party service on the page
1 third-party service load with your homepage (Baidu Analytics), adding 24 KiB and 52 ms of main-thread time.
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.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 272 ms of it running JavaScript. That is comfortably low.
Server response: 73 ms
73 msYour server sent the HTML in 73 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.
Largest Contentful Paint: 7.3 s
7.3 sYour largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load duration (3.3 s).
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.277
0.277The layout shifts by 0.277 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 7.3 s
7.3 sThe page becomes fully interactive after 7.3 s. Good is under 3.8 s.
Real-user CLS: 0.17
0.17For real visitors the layout shifts by 0.17 (75th percentile). Good is under 0.1.
Real-user TTFB: 934 ms
934 msReal visitors wait 934 ms for your server to start answering (75th percentile). Good is under 800 ms.
92 images without width and height
92 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
4 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 41 ms
41 msScripts block the page for only 41 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 11.3 MB in 157 requests
11.3 MBYour homepage downloads 11.3 MB in 157 requests on a phone: images 9.9 MB (138), fonts 1.3 MB (3) and scripts 90 KiB (7). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
1-260204154604536.jpg weighs 683 KiB. On a phone connection a single image that size takes seconds.
8 images in older formats
8 images (1.7 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 far larger than shown
202 KiB2 images are downloaded at several times the size a phone draws them, for example 1-260204154604536.jpg at 1,182 px wide, shown at 390 px. Resized copies would save about 202 KiB.
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: 385.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (34 elements)
All page content should be contained by landmarks: 34 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.
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.
Headings should not be empty (22 elements)
Headings should not be empty: 22 elements on the page fail this check, rated minor by axe-core.
12 links without text
12 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 (h3 → h6, h3 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
28 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 28 passed and 10 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.
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.
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.yuhong.com.cn/sitemap.xml, so Google discovers your pages only by following links.
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.
192 internal links, 50 external
The homepage links to 192 pages on yuhong.com.cn and 50 external pages.
2 checks passed
Meta description: 110 characters
Your meta description is 110 characters: “北京东方雨虹防水技术股份有限公司作为建筑建材系统服务商,以主营防水业务为核心延伸上下游及相关产业链,形成建筑防水、民用建材、非织造布、建筑涂料、建筑修缮、节能保温、特种砂浆、建筑粉料等业务板块合力的建筑建材系统服务体系。”.
robots.txt in place
robots.txt is in place.
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.yuhong.com.cn/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
6 pages without a title
https://www.yuhong.com.cn/about, https://www.yuhong.com.cn/about/Team, https://www.yuhong.com.cn/about/Passion, https://www.yuhong.com.cn/about/history, https://www.yuhong.com.cn/Business and https://www.yuhong.com.cn/Business/building have no <title>, so Google invents the link text in results.
6 pages without a meta description
https://www.yuhong.com.cn/about, https://www.yuhong.com.cn/about/Team, https://www.yuhong.com.cn/about/Passion, https://www.yuhong.com.cn/about/history, https://www.yuhong.com.cn/Business and https://www.yuhong.com.cn/Business/building have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages share a meta description
https://www.yuhong.com.cn/about/Introduction, https://www.yuhong.com.cn/about/culture, https://www.yuhong.com.cn/about/World, https://www.yuhong.com.cn/Business/Energy, https://www.yuhong.com.cn/Business/Civil and https://www.yuhong.com.cn/Business/nonwovens and 3 others use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://www.yuhong.com.cn/about, https://www.yuhong.com.cn/about/Introduction, https://www.yuhong.com.cn/about/Team, https://www.yuhong.com.cn/about/culture, https://www.yuhong.com.cn/about/World and https://www.yuhong.com.cn/about/Passion and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages with very little text
https://www.yuhong.com.cn/about/Introduction, https://www.yuhong.com.cn/about/culture, https://www.yuhong.com.cn/about/World, https://www.yuhong.com.cn/Business/Energy, https://www.yuhong.com.cn/Business/Civil and https://www.yuhong.com.cn/Business/nonwovens and 3 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.
2 pages slow to respond
https://www.yuhong.com.cn/about/World and https://www.yuhong.com.cn/about/history took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 149 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.
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.
Best practices
2 broken images
2 images failed to load on a phone, for example https://www.yuhong.com.cn/.
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.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Invalid regular expression: missing /”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
100 of 103 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.
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 78 words
The homepage has only about 78 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.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
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 yuhong.com.cn, 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 48 issues on yuhong.com.cn, including 14 speed issues, 7 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.