Website review, no card needed

trollbeads.kr logo

trollbeads.kr website review

Visit site (opens in a new tab)Reviewed 8 November 202630 issues · 73 checks

This review found 30 issues worth fixing on trollbeads.kr, 8 of them high impact, across 73 checks. The most urgent: hidden but focusable. 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 trollbeads.kr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. trollbeads.kr at 0.7 s0.7 s
  2. trollbeads.kr at 1.4 s1.4 s
  3. trollbeads.kr at 2.1 s2.1 s
  4. trollbeads.kr at 2.7 s2.7 s
  5. trollbeads.kr at 3.4 s3.4 s
  6. trollbeads.kr at 4.1 s4.1 s
  7. trollbeads.kr at 4.8 s4.8 s
  8. trollbeads.kr at 5.5 s5.5 s

Speed

4 to fix77
  • Mobile performance score: 77

    77/100

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

  • Render-blocking requests

    450 ms

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

  • Reduce unused JavaScript

    350 ms · 73 KiB

    About 73 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 350 ms faster on a phone.

  • 1,638 HTML elements

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

  • Reduce unused CSS

    250 ms · 38 KiB

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

  • Improve image delivery

    150 ms · 81 KiB

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

  • Legacy JavaScript

    150 ms · 19 KiB

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

  • Use efficient cache lifetimes

    150 ms · 5 KiB

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Klaviyo, Shopify and Google CDN and others), adding 255 KiB and 74 ms of main-thread time.

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

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

4 to fix72
  • Largest Contentful Paint: 5.7 s

    5.7 s

    Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “조이풀 스피릿 TAGBE-00325”.

  • Time to Interactive: 5.7 s

    5.7 s

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

  • Speed Index: 4.1 s

    4.1 s

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

  • 5 images without width and height

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

3 checks passed
  • Cumulative Layout Shift: 0.009

    0.009

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

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    Hero_Peoples-uniques-2026_mobile.jpg 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).

  • About 0.5 g of CO₂ per visit

    0.47 g

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

3 checks passed
  • Page weight: 1.7 MB in 152 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 152 requests on a phone: other files 755 KiB (83), images 481 KiB (19) and scripts 331 KiB (42). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8391
  • Hidden but focusable

    4 elements hidden from screen readers can still receive keyboard focus.

  • 2 text elements with low contrast

    2 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 (6 elements)

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

  • 5 form fields without a label

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

  • 5 links without text

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

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 7 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 7777
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (13 characters)

    Your title is only 13 characters: “Trollbeads KR”. 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.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 246 internal links, 10 external

    The homepage links to 246 pages on trollbeads.kr and 10 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Trollbeads KR”.

  • Canonical URL set

    The canonical URL is https://www.trollbeads.kr/.

  • 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.trollbeads.kr/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

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.

  • llms.txt published

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

Other pages

3 to fix85
  • 1 page without a meta description

    https://www.trollbeads.kr/collections/beads-and-pendants has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.trollbeads.kr/products/%ED%8A%B8%EB%A1%A4%EB%B9%84%EC%A6%88-%EC%A5%AC%EB%B9%8C%EB%A6%AC, whose canonical is https://www.trollbeads.kr/products/%ed%8a%b8%eb%a1%a4%eb%b9%84%ec%a6%88-%ec%a5%ac%eb%b9%8c%eb%a6%ac. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://www.trollbeads.kr/collections/jubilee, https://www.trollbeads.kr/collections/new-in, https://www.trollbeads.kr/collections/gift-guide and https://www.trollbeads.kr/collections/beads have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.trollbeads.kr/products/%EC%9C%A0-%EB%84%A4%ED%81%AC%EB%A6%AC%EC%8A%A4 and https://www.trollbeads.kr/collections/necklaces took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 14 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10084
  • 4 broken images

    4 images failed to load on a phone, for example https://www.trollbeads.kr/.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    33 of 36 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 79 words

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

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

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us” and “Contact”.

  • 11 short forms

    11 short forms (2 fields at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 8 cookies set on arrival

    8

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 trollbeads.kr, 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 1 app. It is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on trollbeads.kr, including 8 speed issues, 4 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