Website review, no card needed

lxhausys.com logo

lxhausys.com website review

Visit site (opens in a new tab)Reviewed 17 November 202639 issues · 73 checks

This review found 39 issues worth fixing on lxhausys.com, 19 of them high impact, across 73 checks. The most urgent: improve image delivery. 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
5.3 s3.2 sMay 30Nov 143.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20265.0 s
Jun 6, 20264.6 s
Jun 13, 20264.2 s
Jun 20, 20264.2 s
Jun 27, 20264.2 s
Jul 4, 20264.3 s
Jul 11, 20264.4 s
Jul 18, 20264.6 s
Aug 1, 20264.6 s
Aug 8, 20264.6 s
Aug 15, 20264.2 s
Aug 22, 20264.1 s
Aug 29, 20263.9 s
Sep 5, 20264.0 s
Sep 12, 20264.2 s
Sep 19, 20264.2 s
Sep 26, 20264.3 s
Oct 3, 20263.9 s
Oct 10, 20263.7 s
Oct 17, 20263.7 s
Oct 24, 20263.6 s
Oct 31, 20263.6 s
Nov 7, 20263.6 s
Nov 14, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
511 ms123 msMay 30Nov 14214 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026168 ms
Jun 6, 2026171 ms
Jun 13, 2026205 ms
Jun 20, 2026364 ms
Jun 27, 2026391 ms
Jul 4, 2026426 ms
Jul 11, 2026329 ms
Jul 18, 2026204 ms
Aug 1, 2026224 ms
Aug 8, 2026254 ms
Aug 15, 2026254 ms
Aug 22, 2026309 ms
Aug 29, 2026352 ms
Sep 5, 2026390 ms
Sep 12, 2026466 ms
Sep 19, 2026459 ms
Sep 26, 2026436 ms
Oct 3, 2026378 ms
Oct 10, 2026251 ms
Oct 17, 2026217 ms
Oct 24, 2026212 ms
Oct 31, 2026204 ms
Nov 7, 2026214 ms
Nov 14, 2026214 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 lxhausys.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. lxhausys.com at 0.7 s0.7 s
  2. lxhausys.com at 1.4 s1.4 s
  3. lxhausys.com at 2.1 s2.1 s
  4. lxhausys.com at 2.8 s2.8 s
  5. lxhausys.com at 3.5 s3.5 s
  6. lxhausys.com at 4.2 s4.2 s
  7. lxhausys.com at 4.9 s4.9 s
  8. lxhausys.com at 5.6 s5.6 s

Speed

11 to fix36
  • Improve image delivery

    120.5 s · 36.9 MB

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

  • Reduce unused JavaScript

    18.5 s · 3.4 MB

    About 3.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 18.5 s faster on a phone.

  • Render-blocking requests

    3.5 s

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

  • Use efficient cache lifetimes

    1.8 s · 323 KiB

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

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.4 MB and 642 ms of main-thread time.

  • 13 long tasks on the main thread

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

  • Reduce unused CSS

    460 ms · 82 KiB

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

  • Google CDN adds 397 ms

    397 ms

    Google CDN costs a phone 397 ms of main-thread work and 1.1 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.

  • Main-thread work: 3.4 s

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

  • 1,942 HTML elements

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

  • Font display

    250 ms

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

  • Minify CSS

    23 KiB

    23 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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.

  • 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: 1 ms

    1 ms

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

Core Web Vitals

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

  • First Contentful Paint: 22.2 s

    22.2 s

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

  • Largest Contentful Paint: 150.9 s

    150.9 s

    Your largest element takes 150.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Celebrating 250 Years of American Independence”.

  • Speed Index: 22.2 s

    22.2 s

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

  • Time to Interactive: 150.9 s

    150.9 s

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

  • Total Blocking Time: 798 ms

    798 ms

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

  • 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 26% slower for real visitors

    +26%

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

  • 18 images without width and height

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

6 checks passed
  • Real-user INP: 150 ms

    150 ms

    Real visitors wait 150 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.8 s

    1.8 s

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

  • Real-user TTFB: 712 ms

    712 ms

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

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

    -27%

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

  • Cumulative Layout Shift: 0.002

    0.002

    The layout barely moves while loading (CLS 0.002, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 45.4 MB in 173 requests

    45.4 MB

    Your homepage downloads 45.4 MB in 173 requests on a phone: images 39.4 MB (67), scripts 4.2 MB (15) and fonts 977 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 18 images over 500 KB

    18 images weigh 36.1 MB together. On a phone connection a single image that size takes seconds.

  • 12 images far larger than shown

    20.6 MB

    12 images are downloaded at several times the size a phone draws them, for example Superior White_Bathroom.jpg at 5,000 px wide, shown at 390 px. Resized copies would save about 20.6 MB.

  • 29 images in older formats

    29 images (39.3 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.

  • 7 images below the first screen load straight away

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

  • About 12.9 g of CO₂ per visit

    12.87 g

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

Accessibility

3 to fixGoogle 9597
  • All page content should be contained by landmarks (53 elements)

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

  • 2 form fields without a label

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

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • No H1 headline

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

  • 27 links crawlers can't follow

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Discover eco-friendly, human-centric building materials from LX Hausys for residential and commercial spaces, plus top-…”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Building Materials & Automotive | LX Hausys US”.

  • Canonical URL set

    The canonical URL is https://www.lxhausys.com/us/index.

  • Structured data in place

    Structured data found: LocalBusiness, WholesaleStore and WebSite.

  • 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://www.lxhausys.com/sitemap-index.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 787 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    29 of 31 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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 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 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.

  • About 787 words of copy

    The homepage carries about 787 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 1 of them by other companies (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.

  • 6 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on lxhausys.com, including 20 speed issues, 3 SEO issues and 4 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