Website review, no card needed

1000gage.co.kr logo

1000gage.co.kr website review

Visit site (opens in a new tab)Reviewed 11 November 202652 issues · 95 checks

This review found 52 issues worth fixing on 1000gage.co.kr, 21 of them high impact, across 95 checks. The most urgent: use efficient cache lifetimes. 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
816 ms538 msMay 23Nov 7784 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026699 ms
May 30, 2026715 ms
Jun 6, 2026709 ms
Jun 13, 2026688 ms
Jun 20, 2026707 ms
Jun 27, 2026687 ms
Jul 4, 2026697 ms
Jul 11, 2026698 ms
Jul 18, 2026658 ms
Jul 25, 2026609 ms
Aug 1, 2026606 ms
Aug 8, 2026596 ms
Aug 15, 2026598 ms
Aug 22, 2026624 ms
Aug 29, 2026641 ms
Sep 5, 2026718 ms
Sep 12, 2026753 ms
Sep 19, 2026741 ms
Sep 26, 2026704 ms
Oct 3, 2026676 ms
Oct 10, 2026570 ms
Oct 17, 2026604 ms
Oct 24, 2026641 ms
Oct 31, 2026727 ms
Nov 7, 2026784 ms
Real-visitor tap response (INP)75th percentile, phones
115 ms55 msMay 23Nov 7108 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202663 ms
May 30, 202664 ms
Jun 6, 202668 ms
Jun 13, 202667 ms
Jun 20, 202671 ms
Jun 27, 202672 ms
Jul 4, 202677 ms
Jul 11, 202675 ms
Jul 18, 202671 ms
Jul 25, 202670 ms
Aug 1, 202670 ms
Aug 8, 202670 ms
Aug 15, 202670 ms
Aug 22, 202670 ms
Aug 29, 202670 ms
Sep 5, 202666 ms
Sep 12, 202669 ms
Sep 19, 202666 ms
Sep 26, 202662 ms
Oct 3, 202662 ms
Oct 10, 202662 ms
Oct 17, 202669 ms
Oct 24, 202684 ms
Oct 31, 202693 ms
Nov 7, 2026108 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 1000gage.co.kr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 1000gage.co.kr at 1.5 s1.5 s
  2. 1000gage.co.kr at 3.1 s3.1 s
  3. 1000gage.co.kr at 4.6 s4.6 s
  4. 1000gage.co.kr at 6.1 s6.1 s
  5. 1000gage.co.kr at 7.7 s7.7 s
  6. 1000gage.co.kr at 9.2 s9.2 s
  7. 1000gage.co.kr at 10.7 s10.7 s
  8. 1000gage.co.kr at 12.3 s12.3 s

Speed

14 to fix56
  • Use efficient cache lifetimes

    2.4 s · 6.2 MB

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

  • Reduce unused JavaScript

    1.1 s · 762 KiB

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

  • Render-blocking requests

    1.8 s

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

  • Document request latency

    1.0 s

    The HTML itself could arrive about 1.0 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • 4,322 HTML elements

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

  • Improve image delivery

    300 ms · 7.9 MB

    39 images could be 7.9 MB 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (cre.ma, Google Tag Manager and groobee.io and others), adding 5.5 MB and 761 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.

  • Avoid multiple page redirects

    802 ms

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

  • cre.ma adds 380 ms

    380 ms

    cre.ma costs a phone 380 ms of main-thread work and 860 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

    300 ms · 144 KiB

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

  • makeshop.co.kr adds 14 ms

    14 ms

    makeshop.co.kr costs a phone 14 ms of main-thread work and 4.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: 2.9 s

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

  • Google Tag Manager adds 200 ms

    200 ms

    Google Tag Manager costs a phone 200 ms of main-thread work and 301 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.

  • Minify JavaScript

    150 ms · 60 KiB

    60 KiB could be saved by minifying JavaScript.

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    30 KiB

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

  • Minify CSS

    14 KiB

    14 KiB could be saved by minifying CSS.

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

    166 ms

    Your server sent the HTML in 166 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.

  • Largest Contentful Paint: 11.9 s

    11.9 s

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

  • Speed Index: 17.9 s

    17.9 s

    Visually, the page fills in at 17.9 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.

  • Real-user CLS: 0.16

    0.16

    For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.

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

    +58%

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

  • 250 images without width and height

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Total Blocking Time: 233 ms

    233 ms

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

5 checks passed
  • Real-user LCP: 0.8 s

    0.8 s

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

  • Real-user INP: 129 ms

    129 ms

    Real visitors wait 129 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 0.7 s

    0.7 s

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

  • Real-user TTFB: 565 ms

    565 ms

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

  • Cumulative Layout Shift: 0.062

    0.062

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

Images and page weight

5 to fix18
  • Page weight: 13.2 MB in 208 requests

    13.2 MB

    Your homepage downloads 13.2 MB in 208 requests on a phone: images 10.9 MB (76), scripts 1.7 MB (53) and fonts 273 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 1.9 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    895 KiB

    3 images are downloaded at several times the size a phone draws them, for example 0530020004552.gif at 1,000 px wide, shown at 140 px. Resized copies would save about 895 KiB.

  • 26 images in older formats

    26 images (5.7 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.

  • 6 images below the first screen load straight away

    6 images further down the page (457 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.7 g of CO₂ per visit

    3.74 g

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

Accessibility

8 to fixGoogle 7386
  • 330 images without alt text

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

  • 24 tap targets too small

    24 tap targets are too small or too close together to hit reliably with a finger.

  • 13 text elements with low contrast

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

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

  • Zoom is disabled

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

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

  • 2 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 35 automated accessibility rules passed

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

SEO

2 to fixGoogle 9283
  • No H1 headline

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

  • Title is short (3 characters)

    Your title is only 3 characters: “천가게”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No X (Twitter) card tag

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

  • 470 internal links, 11 external

    The homepage links to 470 pages on 1000gage.co.kr and 11 external pages.

6 checks passed
  • Meta description: 84 characters

    Your meta description is 84 characters: “[천가게 범성원단]은 국내대표 원단쇼핑몰로 순면, 누빔원단, 디즈니원단, 골덴원단, 홈패션, 의류원단, 커튼원단, 털원단 등을 싸게 판매하고 있습니다.”.

  • Canonical URL set

    The canonical URL is https://www.1000gage.co.kr/.

  • Structured data in place

    Structured data found: Organization.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://1000gage.co.kr/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 (614 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://1000gage.co.kr/llms.txt (7 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix43
  • 1 linked page is broken

    Your homepage links to https://1000gage.co.kr/shop/plan.html, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 3 pages without a title

    https://1000gage.co.kr/board/board.html, https://1000gage.co.kr/shop/shopbrand.html and https://1000gage.co.kr/shop/shopdetail.html have no <title>, so Google invents the link text in results.

  • 2 pages share a title

    / and https://1000gage.co.kr/shop/idinfo.html all use the title “천가게”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://1000gage.co.kr/board/board.html, https://1000gage.co.kr/shop/shopbrand.html and https://1000gage.co.kr/shop/shopdetail.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://1000gage.co.kr/board/board.html, https://1000gage.co.kr/shop/shopbrand.html and https://1000gage.co.kr/shop/shopdetail.html have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://1000gage.co.kr/shop/idinfo.html has 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.

  • 1 page slow to respond

    https://1000gage.co.kr/shop/shopdetail.html took over 3 s to send its HTML from our server.

  • 6 internal pages checked

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

2 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

4 to fixGoogle 5086
  • 43 small tap targets

    43 of 91 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 (“Unload event listeners are deprecated and will be removed.”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

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

    The homepage carries about 725 words of visible text.

3 checks passed
  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 136 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 16 cookies set on arrival

    16

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

  • 25 other companies contacted

    Loading the homepage contacts 25 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 1000gage.co.kr, 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
Analytics
Google Analytics
Hosting
Kinxidc As Kr Kr Kinx

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on 1000gage.co.kr, including 23 speed issues, 2 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