Website review, no card needed

coway-usa.com logo

coway-usa.com website review

Visit site (opens in a new tab)Reviewed 25 October 202634 issues · 84 checks

This review found 34 issues worth fixing on coway-usa.com, 14 of them high impact, across 84 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
2.2 s750 msMay 2Oct 17927 ms
Show as table
DateReal-visitor load time (LCP)
May 2, 2026943 ms
May 9, 2026966 ms
May 16, 2026955 ms
May 23, 2026980 ms
May 30, 2026984 ms
Jun 6, 2026992 ms
Jun 13, 20261.0 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.5 s
Aug 29, 20261.4 s
Sep 5, 20261.2 s
Sep 12, 2026946 ms
Sep 19, 2026945 ms
Sep 26, 2026926 ms
Oct 3, 2026914 ms
Oct 10, 2026914 ms
Oct 17, 2026927 ms
Real-visitor tap response (INP)75th percentile, phones
124 ms72 msMay 2Oct 1788 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202679 ms
May 9, 202679 ms
May 16, 202678 ms
May 23, 202679 ms
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202680 ms
Jun 20, 202688 ms
Jun 27, 202695 ms
Jul 4, 2026103 ms
Jul 11, 2026112 ms
Jul 18, 2026113 ms
Jul 25, 2026118 ms
Aug 1, 2026116 ms
Aug 8, 2026112 ms
Aug 15, 2026109 ms
Aug 22, 2026104 ms
Aug 29, 2026103 ms
Sep 5, 202696 ms
Sep 12, 202695 ms
Sep 19, 202696 ms
Sep 26, 202695 ms
Oct 3, 202692 ms
Oct 10, 202687 ms
Oct 17, 202688 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 coway-usa.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. coway-usa.com at 0.4 s0.4 s
  2. coway-usa.com at 0.8 s0.8 s
  3. coway-usa.com at 1.1 s1.1 s
  4. coway-usa.com at 1.5 s1.5 s
  5. coway-usa.com at 1.9 s1.9 s
  6. coway-usa.com at 2.3 s2.3 s
  7. coway-usa.com at 2.6 s2.6 s
  8. coway-usa.com at 3.0 s3.0 s

Speed

6 to fix58
  • Improve image delivery

    3.6 s · 1.4 MB

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

  • Render-blocking requests

    1.9 s

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

  • Reduce unused JavaScript

    1.2 s · 298 KiB

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

  • Use efficient cache lifetimes

    1.1 s · 109 KiB

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

  • Reduce unused CSS

    900 ms · 176 KiB

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

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58 (desktop: 74). Pages that score under 90 lose visitors before the first paint.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Intercom, Accessibe Accessibility Overlay and hcaptcha.com and others), adding 906 KiB and 291 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 14 KiB

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

  • 3 long tasks on the main thread

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

  • Minify CSS

    20 KiB

    20 KiB could be saved by minifying CSS.

  • Minify JavaScript

    15 KiB

    15 KiB could be saved by minifying JavaScript.

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

2 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 607 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 19.6 s

    19.6 s

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

  • Time to Interactive: 19.9 s

    19.9 s

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

  • Speed Index: 9.2 s

    9.2 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

  • 2 images without width and height

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

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

    +11%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.1 s

    1.1 s

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

  • Real-user INP: 83 ms

    83 ms

    Real visitors wait 83 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.0 s

    1.0 s

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

  • Real-user TTFB: 485 ms

    485 ms

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

  • Total Blocking Time: 94 ms

    94 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

6 to fix29
  • Page weight: 4.1 MB in 222 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 222 requests on a phone: images 2.1 MB (32), scripts 871 KiB (51) and other files 805 KiB (108). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    620_gradient_resized.png weighs 579 KiB. On a phone connection a single image that size takes seconds.

  • 5 images below the first screen load straight away

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

  • An image on the first screen is lazy-loaded

    Frame_10.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images in older formats

    2 images (830 KiB) 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.

  • 3 images far larger than shown

    458 KiB

    3 images are downloaded at several times the size a phone draws them, for example 620_gradient_resized.png at 1,500 px wide, shown at 390 px. Resized copies would save about 458 KiB.

  • About 1.2 g of CO₂ per visit

    1.17 g

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

Accessibility

6 to fixGoogle 8391
  • 9 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

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

  • 4 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 59 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

4 to fixGoogle 9285
  • Meta description is long (291 characters)

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

  • No social preview image

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

  • 5 links with vague text

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

  • One H1 headline

    Your <h1> is empty.

  • 91 internal links, 4 external

    The homepage links to 91 pages on coway-usa.com and 4 external pages.

5 checks passed
  • Title: 54 characters

    Your title is a healthy 54 characters: “Coway USA Official Website: Water and Air Purification”.

  • Canonical URL set

    The canonical URL is https://coway-usa.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

100
4 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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 5 pages without a meta description

    https://coway-usa.com/pages/lease, https://coway-usa.com/pages/coway-promotion, https://coway-usa.com/pages/about-us, https://coway-usa.com/pages/faq and https://coway-usa.com/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://coway-usa.com/collections/filters-shop, https://coway-usa.com/pages/coway-promotion and https://coway-usa.com/blogs/news have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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 7791
  • 8 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).

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

3 to fix67
  • 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.

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

    The homepage carries about 526 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Sign Up Log in”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Contact Us”, “Learn More” and “Sign Up Log in”.

  • 4 short forms

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

Privacy and tracking

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 11 other companies contacted

    Loading the homepage contacts 11 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 coway-usa.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
E-commerce
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on coway-usa.com, including 11 speed issues, 4 SEO issues and 3 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