Website review, no card needed

golfpartner-cosmo.com logo

golfpartner-cosmo.com website review

Visit site (opens in a new tab)Reviewed 11 November 202655 issues · 91 checks

This review found 55 issues worth fixing on golfpartner-cosmo.com, 23 of them high impact, across 91 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.1 s1.3 sMay 23Oct 312.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.6 s
Jun 27, 20261.4 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.9 s
Oct 31, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
124 ms99 msMay 23Aug 8102 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026112 ms
May 30, 2026113 ms
Jun 6, 2026115 ms
Jun 13, 2026110 ms
Jun 20, 2026104 ms
Jun 27, 2026108 ms
Jul 4, 2026113 ms
Jul 11, 2026121 ms
Jul 18, 2026119 ms
Jul 25, 2026121 ms
Aug 1, 2026115 ms
Aug 8, 2026102 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 golfpartner-cosmo.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. golfpartner-cosmo.com at 1.4 s1.4 s
  2. golfpartner-cosmo.com at 2.8 s2.8 s
  3. golfpartner-cosmo.com at 4.2 s4.2 s
  4. golfpartner-cosmo.com at 5.6 s5.6 s
  5. golfpartner-cosmo.com at 7.0 s7.0 s
  6. golfpartner-cosmo.com at 8.4 s8.4 s
  7. golfpartner-cosmo.com at 9.8 s9.8 s
  8. golfpartner-cosmo.com at 11.2 s11.2 s

Speed

12 to fix28
  • Improve image delivery

    15.0 s · 6.8 MB

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

  • Use efficient cache lifetimes

    10.4 s · 6.8 MB

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

  • Reduce unused JavaScript

    1.9 s · 560 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Minify JavaScript

    1.1 s · 174 KiB

    174 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 28

    28/100

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

  • Main-thread work: 4.2 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Facebook and TikTok and others), adding 23.3 MB and 625 ms of main-thread time.

  • cafe24img.com adds 27 ms

    27 ms

    cafe24img.com costs a phone 27 ms of main-thread work and 15.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.

  • YouTube adds 174 ms

    174 ms

    YouTube costs a phone 174 ms of main-thread work and 7.5 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

    600 ms · 82 KiB

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

  • 2,442 HTML elements

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

  • Legacy JavaScript

    250 ms · 42 KiB

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

  • 8 long tasks on the main thread

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

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

    558 ms

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

Core Web Vitals

7 to fix23
  • Largest Contentful Paint: 42.9 s

    42.9 s

    Your largest element takes 42.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “스릭슨 ZXi RKT”.

  • Time to Interactive: 44.3 s

    44.3 s

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

  • Speed Index: 14.1 s

    14.1 s

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

  • Cumulative Layout Shift: 0.953

    0.953

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

  • 36 images without width and height

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

  • Total Blocking Time: 410 ms

    410 ms

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Tap response (INP) held steady for real visitors

    -4%

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

  • Largest content (LCP) got 16% slower for real visitors

    +16%

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

  • 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

4 to fix25
  • Page weight: 25.0 MB in 191 requests

    25.0 MB

    Your homepage downloads 25.0 MB in 191 requests on a phone: images 15.1 MB (56), scripts 7.8 MB (49) and HTML 777 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 11 images over 500 KB

    11 images weigh 8.9 MB together. On a phone connection a single image that size takes seconds.

  • 20 images far larger than shown

    3.3 MB

    20 images are downloaded at several times the size a phone draws them, for example shop1_59b2b6536174c81e786ca6d2a519b32d.png at 720 px wide, shown at 178 px. Resized copies would save about 3.3 MB.

  • 40 images in older formats

    40 images (14.8 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.

  • About 7.1 g of CO₂ per visit

    7.10 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

13 to fixGoogle 7682
  • Frames without titles

    11 frames have no title, so screen-reader users cannot tell what they contain.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 7 text elements with low contrast

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

  • 5 images without alt text

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

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

    All page content should be contained by landmarks: 160 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

  • ARIA role should be appropriate for the element (36 elements)

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

  • 12 links without text

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

  • 3 form fields without a label

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

  • Alternative text of images should not be repeated as text (8 elements)

    Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 11 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 10079
  • Title is short (14 characters)

    Your title is only 14 characters: “주식회사 골프파트너앤코스모”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (55 characters)

    Your meta description is only 55 characters: “골프파트너 공식 온라인몰. 중고 골프클럽, 드라이버, 아이언, 퍼터 및 다양한 골프용품을 만나보세요”. 70 to 160 characters is enough to sell the click.

  • No social preview image

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 227 internal links, 1 external

    The homepage links to 227 pages on golfpartner-cosmo.com and 1 external page.

4 checks passed
  • One H1 headline

    Your main headline reads: “{#item}”.

  • Canonical URL set

    The canonical URL is https://golfpartner-cosmo.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://golfpartner-cosmo.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.

  • No llms.txt

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

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

Other pages

7 to fix38
  • 1 linked page is broken

    Your homepage links to https://golfpartner-cosmo.com/%7B, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages without a title

    https://golfpartner-cosmo.com/board/consult/list.html and https://golfpartner-cosmo.com/myshop/board_list.html have no <title>, so Google invents the link text in results.

  • 7 pages share a title

    /, https://golfpartner-cosmo.com/member/agreement.html, https://golfpartner-cosmo.com/myshop/wish_list.html, https://golfpartner-cosmo.com/myshop/mileage/historyList.html, https://golfpartner-cosmo.com/myshop/deposits/historyList.html and https://golfpartner-cosmo.com/myshop/coupon/coupon.html and 1 other all use the title “주식회사 골프파트너앤코스모”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://golfpartner-cosmo.com/board/product/list.html, https://golfpartner-cosmo.com/board/consult/list.html, https://golfpartner-cosmo.com/myshop/board_list.html and https://golfpartner-cosmo.com/product/list.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://golfpartner-cosmo.com/member/agreement.html, https://golfpartner-cosmo.com/myshop/wish_list.html, https://golfpartner-cosmo.com/myshop/mileage/historyList.html, https://golfpartner-cosmo.com/myshop/deposits/historyList.html, https://golfpartner-cosmo.com/myshop/coupon/coupon.html and https://golfpartner-cosmo.com/myshop/likeit/product.html use the same meta description. A description written for each page earns more clicks.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://golfpartner-cosmo.com/board/free/list.html, whose canonical is https://golfpartner-cosmo.com/board/%EC%9E%90%EC%9C%A0%EA%B2%8C%EC%8B%9C%ED%8C%902/1002. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://golfpartner-cosmo.com/board/consult/list.html and https://golfpartner-cosmo.com/myshop/board_list.html have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages with very little text

    https://golfpartner-cosmo.com/board/free/list.html, https://golfpartner-cosmo.com/board/gallery/list.html, https://golfpartner-cosmo.com/board/product/list.html, https://golfpartner-cosmo.com/myshop/wish_list.html, https://golfpartner-cosmo.com/myshop/mileage/historyList.html and https://golfpartner-cosmo.com/myshop/deposits/historyList.html and 3 others have 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.

  • 8 pages slow to respond

    https://golfpartner-cosmo.com/board/free/list.html, https://golfpartner-cosmo.com/board/gallery/list.html, https://golfpartner-cosmo.com/board/product/list.html, https://golfpartner-cosmo.com/myshop/mileage/historyList.html, https://golfpartner-cosmo.com/myshop/deposits/historyList.html and https://golfpartner-cosmo.com/myshop/likeit/product.html and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

1 checks passed
  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9278
  • 4 broken images

    4 images failed to load on a phone, for example https://golfpartner-cosmo.com/.

  • 11 small tap targets

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

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

  • Only about 199 words

    The homepage has only about 199 words of visible text; thin pages give Google and first-time buyers little to go on.

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

4 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks and 48 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel and TikTok Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 2 email links.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 19 cookies set on arrival

    19

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

  • 19 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Analytics
Google Analytics
Hosting
Korea Telecom

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 55 issues on golfpartner-cosmo.com, including 19 speed issues, 5 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