Website review, no card needed

laiye.com logo

laiye.com website review

Visit site (opens in a new tab)Reviewed 26 October 202637 issues · 75 checks

This review found 37 issues worth fixing on laiye.com, 14 of them high impact, across 75 checks. The most urgent: render-blocking requests. 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 laiye.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. laiye.com at 1.6 s1.6 s
  2. laiye.com at 3.2 s3.2 s
  3. laiye.com at 4.8 s4.8 s
  4. laiye.com at 6.4 s6.4 s
  5. laiye.com at 8.0 s8.0 s
  6. laiye.com at 9.6 s9.6 s
  7. laiye.com at 11.2 s11.2 s
  8. laiye.com at 12.8 s12.8 s

Speed

10 to fix29
  • Render-blocking requests

    5.0 s

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

  • Reduce unused JavaScript

    2.6 s · 486 KiB

    About 486 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.

  • Mobile performance score: 29

    29/100

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

  • Use efficient cache lifetimes

    2.3 MB

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

  • Improve image delivery

    2.3 MB

    6 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, website-files.com and cloudfront.net and others), adding 5.3 MB and 1.0 s of main-thread time.

  • website-files.com adds 349 ms

    349 ms

    website-files.com costs a phone 349 ms of main-thread work and 4.4 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.

  • Google Tag Manager adds 581 ms

    581 ms

    Google Tag Manager costs a phone 581 ms of main-thread work and 799 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 CSS

    450 ms · 87 KiB

    About 87 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Main-thread work: 3.3 s

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

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    11 KiB

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

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

1 checks passed
  • Server response: 219 ms

    219 ms

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

Core Web Vitals

7 to fix33
  • Largest Contentful Paint: 29.5 s

    29.5 s

    Your largest element takes 29.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Laiye Named a Visionary in the 2026 Gartner® Magic Quadrant…”.

  • Speed Index: 15.8 s

    15.8 s

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

  • Time to Interactive: 31.0 s

    31.0 s

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

  • First Contentful Paint: 6.1 s

    6.1 s

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

  • Cumulative Layout Shift: 0.445

    0.445

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

  • Total Blocking Time: 297 ms

    297 ms

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

  • 3 images without width and height

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

Images and page weight

1 to fix70
  • Page weight: 7.9 MB in 56 requests

    7.9 MB

    Your homepage downloads 7.9 MB in 56 requests on a phone: images 6.1 MB (15), scripts 1.0 MB (19) and fonts 609 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 2.2 g of CO₂ per visit

    2.23 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.23 g of CO₂e: 267.6 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

7 to fixGoogle 8891
  • Input buttons must have discernible text (1 element)

    Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

  • 15 text elements with low contrast

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

  • ARIA tab nodes must have an accessible name (4 elements)

    ARIA tab nodes must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 5 links without text

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

  • 2 form fields without a label

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

  • ARIA role should be appropriate for the element (1 element)

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

2 checks passed
  • Every image has alt text

    All 36 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

5 to fixGoogle 8572
  • No H1 headline

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

  • Title is long (84 characters)

    Your title is 84 characters, so Google will cut it off around 60: “Laiye Agentic Automation Platform: Drive Enterprise AI Transformation with AI Agents”.

  • Meta description is long (171 characters)

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

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, FAQPage, Organization and SoftwareApplication) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

  • 20 links with vague text

    20 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 126 internal links, 9 external

    The homepage links to 126 pages on laiye.com and 9 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://laiye.com/en.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://laiye.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://laiye.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.

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

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

Other pages

3 to fix85
  • 1 page without a meta description

    https://laiye.com/en/product/agentic-customer-experience has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://laiye.com/en/laiye-worker, whose canonical is https://laiye.com/en/laiyeworker. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://laiye.com/en/product/lead-generation-agent, https://laiye.com/en/product/candidate-screening-agent and https://laiye.com/en/product/market-analysis-agent have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://laiye.com/en/product/market-analysis-agent, https://laiye.com/en/solutions, https://laiye.com/en/solutions/fund and https://laiye.com/en/solutions/manufacturing took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 67 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 9678
  • 1 broken image

    1 image failed to load on a phone, for example https://laiye.com/en.

  • 2 small tap targets

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

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

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 812 words of copy

    The homepage carries about 812 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” and “Contact sales”.

  • 26 calls to action

    The homepage has 26 calls to action, for example “Contact Us”, “Free Trial” and “Contact sales”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 16 testimonial or review blocks and 1 customer or partner logo.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and LinkedIn Insight.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight (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.

  • 15 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Webflow
Framework
Tailwind CSS
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on laiye.com, including 17 speed issues, 5 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