Website review, no card needed

kukahomeus.com logo

kukahomeus.com website review

Visit site (opens in a new tab)Reviewed 13 November 202637 issues · 77 checks

This review found 37 issues worth fixing on kukahomeus.com, 9 of them high impact, across 77 checks. The most urgent: reduce unused JavaScript. 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 kukahomeus.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kukahomeus.com at 0.8 s0.8 s
  2. kukahomeus.com at 1.5 s1.5 s
  3. kukahomeus.com at 2.3 s2.3 s
  4. kukahomeus.com at 3.1 s3.1 s
  5. kukahomeus.com at 3.8 s3.8 s
  6. kukahomeus.com at 4.6 s4.6 s
  7. kukahomeus.com at 5.4 s5.4 s
  8. kukahomeus.com at 6.1 s6.1 s

Speed

14 to fix56
  • Reduce unused JavaScript

    6.2 s · 1.1 MB

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

  • Use efficient cache lifetimes

    2.0 s · 286 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Vimeo and Shopify and others), adding 8.5 MB and 837 ms of main-thread time.

  • Mobile performance score: 56

    56/100

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

  • Improve image delivery

    300 ms · 475 KiB

    5 images could be 475 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Vimeo adds 127 ms

    127 ms

    Vimeo costs a phone 127 ms of main-thread work and 5.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.

  • Reduce unused CSS

    460 ms · 62 KiB

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

  • Render-blocking requests

    500 ms

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

  • Google Tag Manager adds 369 ms

    369 ms

    Google Tag Manager costs a phone 369 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.

  • Legacy JavaScript

    300 ms · 27 KiB

    Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 3.0 s

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

  • Shopify adds 126 ms

    126 ms

    Shopify costs a phone 126 ms of main-thread work and 736 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.

  • robinpro.gallery adds 61 ms

    61 ms

    robinpro.gallery costs a phone 61 ms of main-thread work and 556 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.

  • robinpro.org adds 13 ms

    13 ms

    robinpro.org costs a phone 13 ms of main-thread work and 454 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.

  • 6 long tasks on the main thread

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

  • Minify CSS

    160 ms · 13 KiB

    13 KiB could be saved by minifying CSS.

  • Font display

    100 ms

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

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

    7 ms

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

Core Web Vitals

6 to fix63
  • Largest Contentful Paint: 24.6 s

    24.6 s

    Your largest element takes 24.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MoFit 感恩节海报手机版”.

  • Time to Interactive: 25.4 s

    25.4 s

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

  • Speed Index: 11.0 s

    11.0 s

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

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

  • Total Blocking Time: 210 ms

    210 ms

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

  • 1 image without width and height

    1 image 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.

1 checks passed
  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

1 to fix70
  • Page weight: 9.9 MB in 318 requests

    9.9 MB

    Your homepage downloads 9.9 MB in 318 requests on a phone: other files 6.0 MB (160), scripts 2.8 MB (125) and images 795 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • About 2.8 g of CO₂ per visit

    2.79 g

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

3 to fixGoogle 9596
  • 1 image without alt text

    1 image has 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.

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

4 to fixGoogle 9286
  • Canonical points to another host

    Your canonical URL points to mofithome.com, not kukahomeus.com, so Google may credit that host instead.

  • No social preview image

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

  • 4 links crawlers can't follow

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

  • One H1 headline

    Your <h1> is empty.

  • 64 internal links, 10 external

    The homepage links to 64 pages on kukahomeus.com and 10 external pages.

5 checks passed
  • Meta description: 129 characters

    Your meta description is 129 characters: “MoFit Home strives to provide luxurious and personalizable modern motion reclining furniture. Expert craftsmanship for …”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “MoFit Home modern motion reclining furniture.”.

  • Structured data in place

    Structured data found: BreadcrumbList.

  • 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://kukahomeus.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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://kukahomeus.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 8 pages without a meta description

    https://kukahomeus.com/collections/artistic-pieces, https://kukahomeus.com/collections/modern-couch, https://kukahomeus.com/collections/motion-accessories, https://kukahomeus.com/collections/motion-bed, https://kukahomeus.com/collections/living and https://kukahomeus.com/collections/dining and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://kukahomeus.com/collections/motion-bed, https://kukahomeus.com/collections/dining and https://kukahomeus.com/pages/customer-gallery took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

4 to fixGoogle 5483
  • 5 small tap targets

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

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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.

  • Thin social proof

    Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 293 words of visible text.

3 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Subscribe”, “contact us” and “Contact Us”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 4 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.

  • 37 other companies contacted

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

Apps on your store

Your storefront loads 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Inbox · Hulk Contact Form Builder · Ta Labels Badges · w3apps.co · getmason.io · itoris.com · hextom.com · robinpro.gallery

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

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 kukahomeus.com, including 20 speed issues, 4 SEO issues and 2 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