Website review, no card needed

xingyuntu.com logo

xingyuntu.com website review

Visit site (opens in a new tab)Reviewed 10 November 202635 issues · 69 checks

This review found 35 issues worth fixing on xingyuntu.com, 11 of them high impact, across 69 checks. The most urgent: avoid multiple page redirects. 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 xingyuntu.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. xingyuntu.com at 0.7 s0.7 s
  2. xingyuntu.com at 1.4 s1.4 s
  3. xingyuntu.com at 2.0 s2.0 s
  4. xingyuntu.com at 2.7 s2.7 s
  5. xingyuntu.com at 3.4 s3.4 s
  6. xingyuntu.com at 4.1 s4.1 s
  7. xingyuntu.com at 4.7 s4.7 s
  8. xingyuntu.com at 5.4 s5.4 s

Speed

5 to fix56
  • Avoid multiple page redirects

    1.9 s

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

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    150 ms · 737 KiB

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

  • Main-thread work: 2.3 s

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

  • xingyuntu.com adds 0 ms

    0 ms

    xingyuntu.com costs a phone 0 ms of main-thread work and 687 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.

  • Improve image delivery

    229 KiB

    2 images could be 229 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 71 ms. During a long task the page ignores taps.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Fonts, aliyuncs.com and xingyuntu.com), adding 687 KiB and 0 ms of main-thread time.

  • Reduce unused CSS

    19 KiB

    About 19 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.

  • Forced reflow

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

5 to fix56
  • Cumulative Layout Shift: 2.558

    2.558

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Speed Index: 5.5 s

    5.5 s

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

  • Largest Contentful Paint: 3.4 s

    3.4 s

    Your largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “hi 💗”. Most of its time is element render delay (1.6 s).

  • Time to Interactive: 4.1 s

    4.1 s

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

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

1 checks passed
  • Total Blocking Time: 11 ms

    11 ms

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.34 g

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

1 checks passed
  • Page weight: 1.2 MB in 65 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 65 requests on a phone: images 1.0 MB (27), stylesheets 87 KiB (16) and scripts 71 KiB (19). That is a lean page.

Accessibility

7 to fixGoogle 5679
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

  • 8 images without alt text

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 form fields without a label

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

1 checks passed
  • 19 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 24 WCAG 2.2 A/AA and best-practice rules on the phone render: 19 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

7 to fixGoogle 9066
  • No H1 headline

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

  • Title is short (24 characters)

    Your title is only 24 characters: “leyu.乐鱼(集团)体育-科技股份有限公司网站”. 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 http://www.xingyuntu.com/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.

  • 40 internal links, 2 external

    The homepage links to 40 pages on xingyuntu.com and 2 external pages.

2 checks passed
  • Meta description: 120 characters

    Your meta description is 120 characters: ““乐鱼体育【⭐️注册充值⭐️送好礼】大哥推荐【www.leyu.com】最新版本、手机版、app下载、登录入口、官方网站、网页版、平台、网址、地址、注册、,电竞,娱乐⭐️leyu官方网站-app下载【靠谱平台】(2025全站)最新...”/”.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

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://xingyuntu.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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

3 to fix86
  • 15 pages share a title

    /, https://xingyuntu.com/aboutus, https://xingyuntu.com/saas, https://xingyuntu.com/products, https://xingyuntu.com/list_42 and https://xingyuntu.com/list_32 and 9 others all use the title “leyu.乐鱼(集团)体育-科技股份有限公司网站”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages share a meta description

    https://xingyuntu.com/aboutus, https://xingyuntu.com/saas, https://xingyuntu.com/products, https://xingyuntu.com/list_42, https://xingyuntu.com/list_32 and https://xingyuntu.com/list_23 and 8 others use the same meta description. A description written for each page earns more clicks.

  • 14 pages without an H1

    https://xingyuntu.com/aboutus, https://xingyuntu.com/saas, https://xingyuntu.com/products, https://xingyuntu.com/list_42, https://xingyuntu.com/list_32 and https://xingyuntu.com/list_23 and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 pages with very little text

    https://xingyuntu.com/aboutus, https://xingyuntu.com/saas, https://xingyuntu.com/products, https://xingyuntu.com/list_42, https://xingyuntu.com/list_32 and https://xingyuntu.com/list_23 and 8 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.

  • 12 pages slow to respond

    https://xingyuntu.com/aboutus, https://xingyuntu.com/saas, https://xingyuntu.com/products, https://xingyuntu.com/list_42, https://xingyuntu.com/list_6 and https://xingyuntu.com/about_7 and 6 others took over 3 s to send their HTML from our server.

  • 14 internal pages checked

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

5 checks passed
  • Linked pages load

    All 14 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 14 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 7392
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Browser-reported issues

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

1 checks passed
  • 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 3 words

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

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

  • 2 other companies contacted

    Loading the homepage contacts 2 hosts 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 xingyuntu.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on xingyuntu.com, including 10 speed issues, 7 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