Website review, no card needed

hanshow.com logo

hanshow.com website review

Visit site (opens in a new tab)Reviewed 27 October 202645 issues · 88 checks

This review found 45 issues worth fixing on hanshow.com, 15 of them high impact, across 88 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
2.7 s2.1 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.7 s
May 16, 20262.6 s
May 23, 20262.6 s
May 30, 20262.7 s
Jun 6, 20262.6 s
Jun 13, 20262.6 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.4 s
Jul 11, 20262.3 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.3 s
Sep 12, 20262.2 s
Sep 19, 20262.1 s
Sep 26, 20262.2 s
Oct 3, 20262.3 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
104 ms85 msMay 9Oct 2489 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202698 ms
May 16, 202697 ms
May 23, 2026100 ms
May 30, 2026102 ms
Jun 6, 202699 ms
Jun 13, 202697 ms
Jun 20, 202698 ms
Jun 27, 202696 ms
Jul 4, 202696 ms
Jul 11, 202698 ms
Jul 18, 202696 ms
Jul 25, 202698 ms
Aug 1, 202699 ms
Aug 8, 202694 ms
Aug 15, 202690 ms
Aug 22, 202689 ms
Aug 29, 202689 ms
Sep 5, 202693 ms
Sep 12, 202695 ms
Sep 19, 202696 ms
Sep 26, 202695 ms
Oct 3, 202694 ms
Oct 10, 202689 ms
Oct 17, 202687 ms
Oct 24, 202689 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 hanshow.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hanshow.com at 0.5 s0.5 s
  2. hanshow.com at 1.0 s1.0 s
  3. hanshow.com at 1.4 s1.4 s
  4. hanshow.com at 1.9 s1.9 s
  5. hanshow.com at 2.4 s2.4 s
  6. hanshow.com at 2.9 s2.9 s
  7. hanshow.com at 3.4 s3.4 s
  8. hanshow.com at 3.8 s3.8 s

Speed

10 to fix49
  • Use efficient cache lifetimes

    3.0 s · 4.2 MB

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

  • hcaptcha.com adds 1.5 s

    1.5 s

    hcaptcha.com costs a phone 1.5 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 49

    49/100

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

  • Main-thread work: 4.8 s

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

  • Improve image delivery

    900 ms · 1.7 MB

    9 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • 7 third-party services on the page

    7 third-party services load with your homepage (hcaptcha.com, Google Tag Manager and Cookiebot and others), adding 1.6 MB and 2.0 s of main-thread time.

  • 16 long tasks on the main thread

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

  • Google Tag Manager adds 446 ms

    446 ms

    Google Tag Manager costs a phone 446 ms of main-thread work and 360 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.

  • Reduce unused JavaScript

    433 KiB

    About 433 KiB of JavaScript is downloaded but never used on this page.

  • 1,711 HTML elements

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

  • Reduce unused CSS

    100 KiB

    About 100 KiB of CSS is downloaded but never applied on this page.

  • Legacy JavaScript

    14 KiB

    Polyfills for old browsers add 14 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    8 KiB

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

1 checks passed
  • Server response: 46 ms

    46 ms

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

Core Web Vitals

8 to fix67
  • 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.

  • Time to Interactive: 19.2 s

    19.2 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

    Scripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.

  • Speed Index: 7.3 s

    7.3 s

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

  • Largest Contentful Paint: 4.5 s

    4.5 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0.119

    0.119

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

6 checks passed
  • Real-user INP: 91 ms

    91 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Tap response (INP) got 10% faster for real visitors

    -10%

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

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

    -12%

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

  • First Contentful Paint: 1.0 s

    1.0 s

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

Images and page weight

5 to fix18
  • Page weight: 5.7 MB in 77 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 77 requests on a phone: images 2.8 MB (49), scripts 1.3 MB (8) and media 776 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 2.0 MB together. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    1.4 MB

    1 image is downloaded at several times the size a phone draws it, for example home_nebular_ultra_1_s.png at 3,821 px wide, shown at 230 px. Resized copies would save about 1.4 MB.

  • 8 images in older formats

    8 images (2.4 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.

  • 1 image below the first screen load straight away

    1 image further down the page (1.5 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.6 g of CO₂ per visit

    1.63 g

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

Accessibility

8 to fixGoogle 8290
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 6 tap targets too small

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

  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

  • 2 form fields without a label

    2 form fields have 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.

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 75 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

7 to fixGoogle 9270
  • Title is long (87 characters)

    Your title is 87 characters, so Google will cut it off around 60: “Leading Electronic Shelf Label Supplier for Digital Retail Solutions| Hanshow | Hanshow”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Electronic Shelf Label Solution” and “Intelligent Store Solutions”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • Meta description is long (166 characters)

    Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 119 internal links, 4 external

    The homepage links to 119 pages on hanshow.com and 4 external pages.

2 checks passed
  • 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.hanshow.com/sitemap.xml.

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.hanshow.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 (1,423 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 2 pages share a title

    https://www.hanshow.com/en and / all use the title “Leading Electronic Shelf Label Supplier for Digital Retail Solutions|…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without an H1

    https://www.hanshow.com/en/polaris-pro, https://www.hanshow.com/en/smartcart and https://www.hanshow.com/en/business-cases have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.hanshow.com/en/smartcart, https://www.hanshow.com/en/solutions/category/all-star-cloud, https://www.hanshow.com/en/business-cases and https://www.hanshow.com/en/case/spar-in-france-group-casino took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 37 found) and read each the way a search engine does.

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

  • 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

3 to fixGoogle 6988
  • 70 distorted images

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

  • 2 JavaScript errors while loading

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

    15 of 18 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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,246 words of copy

    The homepage carries about 1,246 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: “LEARN MORE ⟶”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact” and “Learn More ⟶”.

  • 3 short forms

    3 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 8 testimonial or review blocks and 24 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies (measured from a US location before any click).

  • 13 other companies contacted

    Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 hanshow.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 © 2023.

Stack

Analytics
Google Tag Manager
Hosting
Azure

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on hanshow.com, including 18 speed issues, 7 SEO issues and 1 conversion gap. 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