Website review, no card needed

lining.com logo

lining.com website review

Visit site (opens in a new tab)Reviewed 31 October 202649 issues · 80 checks

This review found 49 issues worth fixing on lining.com, 21 of them high impact, across 80 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
3.8 s2.7 sMay 9Oct 243.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.0 s
May 16, 20263.0 s
May 23, 20263.1 s
May 30, 20263.0 s
Jun 6, 20263.2 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20263.0 s
Jul 25, 20263.1 s
Aug 1, 20263.2 s
Aug 8, 20263.3 s
Aug 15, 20263.1 s
Aug 22, 20263.0 s
Aug 29, 20263.1 s
Sep 5, 20263.0 s
Sep 12, 20263.1 s
Sep 19, 20263.2 s
Sep 26, 20263.3 s
Oct 3, 20263.4 s
Oct 10, 20263.5 s
Oct 17, 20263.6 s
Oct 24, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
288 ms61 msMay 9Oct 24205 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202690 ms
May 16, 202689 ms
May 23, 202687 ms
May 30, 202688 ms
Jun 6, 202695 ms
Jun 13, 2026100 ms
Jun 20, 2026115 ms
Jun 27, 2026129 ms
Jul 4, 2026115 ms
Jul 11, 2026135 ms
Jul 18, 2026147 ms
Jul 25, 2026149 ms
Aug 1, 2026114 ms
Aug 8, 2026102 ms
Aug 15, 202697 ms
Aug 22, 202694 ms
Aug 29, 202698 ms
Sep 5, 2026101 ms
Sep 12, 2026128 ms
Sep 19, 2026212 ms
Sep 26, 2026240 ms
Oct 3, 2026254 ms
Oct 10, 2026262 ms
Oct 17, 2026239 ms
Oct 24, 2026205 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 lining.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lining.com at 1.3 s1.3 s
  2. lining.com at 2.6 s2.6 s
  3. lining.com at 3.9 s3.9 s
  4. lining.com at 5.2 s5.2 s
  5. lining.com at 6.5 s6.5 s
  6. lining.com at 7.7 s7.7 s
  7. lining.com at 9.0 s9.0 s
  8. lining.com at 10.3 s10.3 s

Speed

6 to fix36
  • Use efficient cache lifetimes

    5.4 s · 2.3 MB

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

  • Improve image delivery

    3.8 s · 1.2 MB

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

  • Avoid multiple page redirects

    3.6 s

    The page goes through 1 redirect before it starts loading, costing about 3.6 s. Link and advertise the final URL directly.

  • Render-blocking requests

    1.2 s

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

  • Mobile performance score: 36

    36/100

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

  • Reduce unused JavaScript

    910 ms · 151 KiB

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

  • Minify JavaScript

    120 ms · 21 KiB

    21 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    12 KiB

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

  • 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: 0.6 s

    A phone's processor spends 0.6 s on main-thread work while loading, 88 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

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

  • Largest Contentful Paint: 14.0 s

    14.0 s

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

  • Cumulative Layout Shift: 0.848

    0.848

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

  • Speed Index: 10.6 s

    10.6 s

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

  • Time to Interactive: 14.5 s

    14.5 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Real-user LCP: 3.6 s

    3.6 s

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

  • Tap response (INP) got 148% slower for real visitors

    +148%

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

  • Largest content (LCP) got 22% slower for real visitors

    +22%

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • 35 images without width and height

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

4 checks passed
  • Real-user INP: 74 ms

    74 ms

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

  • Real-user CLS: 0.09

    0.09

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

  • Real-user TTFB: 424 ms

    424 ms

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

  • 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

1 to fix85
  • Page weight: 2.5 MB in 169 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 169 requests on a phone: images 2.1 MB (147), scripts 291 KiB (12) and stylesheets 53 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.70 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

10 to fixGoogle 4776
  • Form elements must have labels (1 element)

    Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.

  • Malformed lists

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

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

  • <marquee> elements are deprecated and must not be used (1 element)

    <marquee> elements are deprecated and must not be used: 1 element on the page fails this check, rated serious by axe-core.

  • 93 images without alt text

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

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

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

  • 8 links without text

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

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 21 automated accessibility rules passed

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

SEO

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

  • Meta description is short (1 characters)

    Your meta description is only 1 characters: “2”. 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 XML sitemap

    No XML sitemap at https://lining.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

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

  • 9 links crawlers can't follow

    9 links have no real href, so search engines can't follow them.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

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

  • 26 internal links, 181 external

    The homepage links to 26 pages on lining.com and 181 external pages.

AI search readiness

1 to fix69
  • 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://lining.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.

Other pages

4 to fix79
  • 1 page points its canonical at the homepage

    https://lining.com/brand/brand/index.html declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 1 page without a meta description

    https://lining.com/brand/brand/index.html has no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages share a meta description

    https://lining.com/other/shop-lining.html, https://lining.com/sportscamp/trainning/daily.html, https://lining.com/sportscamp/trainning/summerholiday.html, https://lining.com/sportscamp/trainning/winterholiday.html, https://lining.com/sportscamp/trainning/abroad.html and https://lining.com/youthcamp/basketball/primary.html and 8 others use the same meta description. A description written for each page earns more clicks.

  • 14 pages without an H1

    https://lining.com/other/shop-lining.html, https://lining.com/sportscamp/trainning/daily.html, https://lining.com/sportscamp/trainning/summerholiday.html, https://lining.com/sportscamp/trainning/winterholiday.html, https://lining.com/sportscamp/trainning/abroad.html and https://lining.com/youthcamp/basketball/primary.html and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 13 pages with very little text

    https://lining.com/other/shop-lining.html, https://lining.com/sportscamp/trainning/daily.html, https://lining.com/sportscamp/trainning/summerholiday.html, https://lining.com/sportscamp/trainning/winterholiday.html, https://lining.com/sportscamp/trainning/abroad.html and https://lining.com/youthcamp/basketball/primary.html and 7 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.

  • 3 pages slow to respond

    https://lining.com/sportscamp/trainning/daily.html, https://lining.com/sportscamp/trainning/summerholiday.html and https://lining.com/sportscamp/trainning/winterholiday.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 23 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.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7367
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 11 small tap targets

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • No console errors

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

Content and conversion

6 to fix43
  • 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: 16 trust badges. 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 13 words

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

1 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

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 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 lining.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
jQuery
Hosting
Alibaba Cloud

Company

Founded
1989
Headquarters
Beijing

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on lining.com, including 17 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

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