Website review, no card needed

hengliamerica.com logo

hengliamerica.com website review

Visit site (opens in a new tab)Reviewed 27 October 202655 issues · 95 checks

This review found 55 issues worth fixing on hengliamerica.com, 28 of them high impact, across 95 checks. The most urgent: use efficient cache lifetimes. 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

Real-visitor load time (LCP)75th percentile, phones
6.3 s2.3 sMay 9Oct 242.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.6 s
May 16, 20265.7 s
May 23, 20265.8 s
May 30, 20265.7 s
Jun 6, 20265.3 s
Jun 13, 20265.1 s
Jun 20, 20265.2 s
Jun 27, 20265.2 s
Jul 4, 20264.7 s
Jul 11, 20263.9 s
Jul 18, 20263.2 s
Jul 25, 20262.8 s
Aug 1, 20263.0 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.1 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.1 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.1 s
Oct 10, 20263.0 s
Oct 17, 20262.9 s
Oct 24, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
113 ms84 msMay 9Oct 2494 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026103 ms
May 16, 2026100 ms
May 23, 202699 ms
May 30, 202695 ms
Jun 6, 202693 ms
Jun 13, 202695 ms
Jun 20, 202691 ms
Jun 27, 202691 ms
Jul 4, 202691 ms
Jul 11, 202687 ms
Jul 18, 202691 ms
Jul 25, 202691 ms
Aug 1, 2026103 ms
Aug 8, 2026107 ms
Aug 15, 2026106 ms
Aug 22, 2026103 ms
Aug 29, 2026106 ms
Sep 5, 2026110 ms
Sep 12, 2026104 ms
Sep 19, 2026106 ms
Sep 26, 2026104 ms
Oct 3, 202699 ms
Oct 10, 2026100 ms
Oct 17, 202697 ms
Oct 24, 202694 ms

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

Full-page screenshot of hengliamerica.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hengliamerica.com at 0.5 s0.5 s
  2. hengliamerica.com at 0.9 s0.9 s
  3. hengliamerica.com at 1.4 s1.4 s
  4. hengliamerica.com at 1.9 s1.9 s
  5. hengliamerica.com at 2.4 s2.4 s
  6. hengliamerica.com at 2.8 s2.8 s
  7. hengliamerica.com at 3.3 s3.3 s
  8. hengliamerica.com at 3.8 s3.8 s

Speed

10 to fix45
  • Use efficient cache lifetimes

    26.4 s · 26.5 MB

    219 files are served with short cache lifetimes, so returning visitors download them again (26.5 MB).

  • Improve image delivery

    43.7 s · 9.4 MB

    19 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 43.7 s faster on a phone.

  • Render-blocking requests

    2.0 s

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

  • Document request latency

    1.3 s

    The HTML itself could arrive about 1.3 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    1.3 s

    Reduce initial server response time. Google estimates savings of 1.3 s on a phone.

  • Mobile performance score: 45

    45/100

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

  • Font display

    300 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

  • Main-thread work: 2.0 s

    A phone's processor spends 2.0 s on main-thread work while loading, 526 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 2,012 HTML elements

    The page has 2,012 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Server response: 1.4 s

    1.4 s

    Your server takes 1.4 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Reduce unused JavaScript

    150 ms · 98 KiB

    About 98 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Other Google APIs/SDKs), adding 176 KiB and 215 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Minify JavaScript

    16 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Core Web Vitals

11 to fix33
  • 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.

  • Real-user LCP: 4.3 s

    4.3 s

    Real visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.34

    0.34

    For real visitors the layout shifts by 0.34 (75th percentile). Good is under 0.1.

  • Real-user FCP: 3.0 s

    3.0 s

    Real visitors see the first content after 3.0 s (75th percentile). Good is under 1.8 s.

  • Largest Contentful Paint: 106.2 s

    106.2 s

    Your largest element takes 106.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Leading manufacturer of hydraulic drive control and system …”.

  • Time to Interactive: 110.3 s

    110.3 s

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

  • Speed Index: 13.1 s

    13.1 s

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

  • Real-user TTFB: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.246

    0.246

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

  • First Contentful Paint: 2.9 s

    2.9 s

    The first text or image appears after 2.9 s on a phone. Good is under 1.8 s.

  • 26 images without width and height

    26 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -6%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 103 ms to 94 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user INP: 92 ms

    92 ms

    Real visitors wait 92 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Largest content (LCP) got 50% faster for real visitors

    -50%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.6 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 187 ms

    187 ms

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

Images and page weight

5 to fix18
  • Page weight: 51.7 MB in 234 requests

    51.7 MB

    Your homepage downloads 51.7 MB in 234 requests on a phone: images 37.2 MB (193), media 10.4 MB (2) and fonts 3.6 MB (2). Under 2 MB keeps phones on slow connections fast.

  • 27 images over 500 KB

    27 images weigh 24.8 MB together. On a phone connection a single image that size takes seconds.

  • 18 images far larger than shown

    9.1 MB

    18 images are downloaded at several times the size a phone draws them, for example 1788400559767.png at 1,920 px wide, shown at 390 px. Resized copies would save about 9.1 MB.

  • 40 images in older formats

    40 images (29.6 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.

  • 19 images below the first screen load straight away

    19 images further down the page (13.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 14.7 g of CO₂ per visit

    14.66 g

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

Accessibility

14 to fixGoogle 7979
  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (2 elements)

    ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

  • ARIA input fields must have an accessible name (3 elements)

    ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 2 tap targets too small

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

  • <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements (1 element)

    <dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 116 images without alt text

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

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

    All page content should be contained by landmarks: 21 elements on the page fail this check, rated moderate by axe-core.

  • 16 links without text

    16 visible links have no text or label, so screen readers cannot say where they go.

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

6 to fixGoogle 9273
  • Title is short (16 characters)

    Your title is only 16 characters: “Hengli Hydraulic”. 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 (16 characters)

    Your meta description is only 16 characters: “Hengli Hydraulic”. 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.henglihydraulics.com/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 245 internal links, 6 external

    The homepage links to 245 pages on hengliamerica.com and 6 external pages.

2 checks passed
  • One H1 headline

    Your main headline reads: “Leading manufacturer of hydraulic drive control and system integration solutions”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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.henglihydraulics.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.

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,825 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix73
  • 1 page without a title

    https://www.henglihydraulics.com/en/col3197/index has no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://www.henglihydraulics.com/en and https://www.henglihydraulics.com/en/index.html all use the title “Hengli Hydraulic”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.henglihydraulics.com/en/col3197/index has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 190 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.

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

Best practices

2 to fixGoogle 8891
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 26 distorted images

    26 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    34 of 39 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

  • About 1,191 words of copy

    The homepage carries about 1,191 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads 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.

  • 3 cookies set on arrival

    3

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 hengliamerica.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2024.

Stack

Framework
jQuery
Analytics
Google Analytics
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 55 issues on hengliamerica.com, including 21 speed issues, 6 SEO issues and 2 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