Website review, no card needed

newhopeliuhe.com logo

newhopeliuhe.com website review

Visit site (opens in a new tab)Reviewed 30 October 202640 issues · 72 checks

This review found 40 issues worth fixing on newhopeliuhe.com, 16 of them high impact, across 72 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of newhopeliuhe.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. newhopeliuhe.com at 1.1 s1.1 s
  2. newhopeliuhe.com at 2.3 s2.3 s
  3. newhopeliuhe.com at 3.4 s3.4 s
  4. newhopeliuhe.com at 4.5 s4.5 s
  5. newhopeliuhe.com at 5.7 s5.7 s
  6. newhopeliuhe.com at 6.8 s6.8 s
  7. newhopeliuhe.com at 7.9 s7.9 s
  8. newhopeliuhe.com at 9.1 s9.1 s

Speed

6 to fix40
  • Improve image delivery

    22.0 s · 9.4 MB

    11 images could be 9.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 22.0 s faster on a phone.

  • Render-blocking requests

    1.1 s

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Mobile performance score: 40

    40/100

    Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 1 third-party service on the page

    1 third-party service load with your homepage (newhope-liuhe.cn), adding 13.8 MB and 0 ms of main-thread time.

  • newhope-liuhe.cn adds 0 ms

    0 ms

    newhope-liuhe.cn costs a phone 0 ms of main-thread work and 13.8 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.

  • Use efficient cache lifetimes

    750 ms · 168 KiB

    36 files are served with short cache lifetimes, so returning visitors download them again (168 KiB).

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 200 ms. During a long task the page ignores taps.

  • Minify JavaScript

    160 ms · 20 KiB

    20 KiB could be saved by minifying JavaScript.

  • 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.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 142 ms of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

    Your server sent the HTML in 1 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix34
  • Largest Contentful Paint: 58.0 s

    58.0 s

    Your largest element takes 58.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 60.7 s

    60.7 s

    The page becomes fully interactive after 60.7 s. Good is under 3.8 s.

  • Speed Index: 14.2 s

    14.2 s

    Visually, the page fills in at 14.2 s (Speed Index). Good is under 3.4 s.

  • Cumulative Layout Shift: 0.997

    0.997

    The layout shifts by 0.997 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 12 images without width and height

    12 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
  • First Contentful Paint: 1.3 s

    1.3 s

    The first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 14.8 MB in 66 requests

    14.8 MB

    Your homepage downloads 14.8 MB in 66 requests on a phone: images 14.7 MB (53), scripts 131 KiB (8) and stylesheets 12 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 6.9 MB together. On a phone connection a single image that size takes seconds.

  • 8 images far larger than shown

    6.6 MB

    8 images are downloaded at several times the size a phone draws them, for example 20231127145209-5236.jpg at 8,195 px wide, shown at 390 px. Resized copies would save about 6.6 MB.

  • 11 images in older formats

    11 images (8.5 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 (955 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.2 g of CO₂ per visit

    4.20 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.20 g of CO₂e: 504.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

5 to fixGoogle 7890
  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • 16 images without alt text

    16 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (16 elements)

    All page content should be contained by landmarks: 16 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.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 30 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

9 to fixGoogle 8258
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (11 characters)

    Your title is only 11 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.

  • Meta description is short (15 characters)

    Your meta description is only 15 characters: “新希望六和股份有限公司官方网站”. 70 to 160 characters is enough to sell the click.

  • 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.newhopeliuhe.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at newhopeliuhe.com/robots.txt, the first file search crawlers ask for.

  • 3 links crawlers can't follow

    3 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 incomplete here.

  • 29 internal links, 27 external

    The homepage links to 29 pages on newhopeliuhe.com and 27 external pages.

AI search readiness

1 to fix83
  • 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.newhopeliuhe.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

2 to fix90
  • 16 pages share a title

    /, https://www.newhopeliuhe.com/lh/briefintroduction.html, https://www.newhopeliuhe.com/lh/companynews.html, https://www.newhopeliuhe.com/lh/productbrand.html, https://www.newhopeliuhe.com/lh/technical.html and https://www.newhopeliuhe.com/lh/concept.html and 10 others all use the title “新希望六和股份有限公司”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://www.newhopeliuhe.com/lh/briefintroduction.html, https://www.newhopeliuhe.com/lh/companynews.html, https://www.newhopeliuhe.com/lh/productbrand.html, https://www.newhopeliuhe.com/lh/technical.html, https://www.newhopeliuhe.com/lh/concept.html and https://www.newhopeliuhe.com/lh/esg.html and 9 others use the same meta description. A description written for each page earns more clicks.

  • 15 pages with very little text

    https://www.newhopeliuhe.com/lh/briefintroduction.html, https://www.newhopeliuhe.com/lh/companynews.html, https://www.newhopeliuhe.com/lh/productbrand.html, https://www.newhopeliuhe.com/lh/technical.html, https://www.newhopeliuhe.com/lh/concept.html and https://www.newhopeliuhe.com/lh/esg.html and 9 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.

  • 8 pages slow to respond

    https://www.newhopeliuhe.com/lh/technical.html, https://www.newhopeliuhe.com/lh/concept.html, https://www.newhopeliuhe.com/lh/esg.html, https://www.newhopeliuhe.com/lh/contactus.html, https://www.newhopeliuhe.com/lh/mediacoverage.html and https://www.newhopeliuhe.com/lh/videocenter.html and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage and read each the way a search engine does.

6 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 a meta description

    All 15 pages that loaded have a meta description.

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 5 small tap targets

    5 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix25
  • 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.

  • 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 26 words

    The homepage has only about 26 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

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 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.

  • 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 newhopeliuhe.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 40 issues on newhopeliuhe.com, including 11 speed issues, 9 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25