Website review, no card needed

tklmerch.com logo

tklmerch.com website review

Visit site (opens in a new tab)Reviewed 8 November 202632 issues · 78 checks

This review found 32 issues worth fixing on tklmerch.com, 7 of them high impact, across 78 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
1.2 s821 msAug 22Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 2026897 ms
Sep 26, 2026868 ms
Oct 3, 2026877 ms
Oct 10, 2026922 ms
Oct 17, 2026982 ms
Oct 24, 20261.0 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
97 ms87 msAug 22Oct 3194 ms
Show as table
DateReal-visitor tap response (INP)
Aug 22, 202696 ms
Aug 29, 202696 ms
Sep 5, 202696 ms
Sep 12, 202696 ms
Sep 19, 202690 ms
Sep 26, 202688 ms
Oct 3, 202689 ms
Oct 10, 202693 ms
Oct 17, 202696 ms
Oct 24, 202695 ms
Oct 31, 202694 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 tklmerch.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tklmerch.com at 0.6 s0.6 s
  2. tklmerch.com at 1.1 s1.1 s
  3. tklmerch.com at 1.7 s1.7 s
  4. tklmerch.com at 2.2 s2.2 s
  5. tklmerch.com at 2.8 s2.8 s
  6. tklmerch.com at 3.4 s3.4 s
  7. tklmerch.com at 3.9 s3.9 s
  8. tklmerch.com at 4.5 s4.5 s

Speed

9 to fix60
  • Improve image delivery

    1.1 s · 315 KiB

    2 images could be 315 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 60

    60/100

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

  • Use efficient cache lifetimes

    500 ms · 74 KiB

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

  • Reduce unused CSS

    450 ms · 82 KiB

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

  • Reduce unused JavaScript

    300 ms · 49 KiB

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

  • Minify JavaScript

    300 ms · 7 KiB

    7 KiB could be saved by minifying JavaScript.

  • Render-blocking requests

    300 ms

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

  • Klaviyo adds 129 ms

    129 ms

    Klaviyo costs a phone 129 ms of main-thread work and 309 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.

  • Shopify adds 26 ms

    26 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Shopify and orderlogicapp.com and others), adding 811 KiB and 215 ms of main-thread time.

  • Minify CSS

    150 ms · 15 KiB

    15 KiB could be saved by minifying CSS.

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    19 KiB

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

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

2 checks passed
  • Main-thread work: 2.0 s

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

  • 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 fix100
  • Largest Contentful Paint: 11.2 s

    11.2 s

    Your largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BEFORE I FORGET VINYL”.

  • Time to Interactive: 11.7 s

    11.7 s

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

  • Speed Index: 7.2 s

    7.2 s

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Total Blocking Time: 213 ms

    213 ms

    Scripts block taps and scrolling for 213 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.

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

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

    1.0 s

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

  • Real-user INP: 88 ms

    88 ms

    Real visitors wait 88 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: 443 ms

    443 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix69
  • Page weight: 2.1 MB in 210 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 210 requests on a phone: other files 749 KiB (92), scripts 700 KiB (102) and images 470 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    tkl_bif_signed_full_mock.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).

  • 1 image far larger than shown

    282 KiB

    1 image is downloaded at several times the size a phone draws it, for example Dove.png at 851 px wide, shown at 25 px. Resized copies would save about 282 KiB.

  • About 0.6 g of CO₂ per visit

    0.61 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

3 to fixGoogle 9695
  • 5 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

  • 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 3 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

1 to fixGoogle 10093
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “The Kid LAROI | Official Merchandise Store – THE KID LAROI US STORE”.

  • 11 internal links, 6 external

    The homepage links to 11 pages on tklmerch.com and 6 external pages.

7 checks passed
  • Meta description: 103 characters

    Your meta description is 103 characters: “Shop the official collection of music, clothing, accessories, and other merchandise from The Kid LAROI.”.

  • One H1 headline

    Your main headline reads: “THE KID LAROI US STORE”.

  • Canonical URL set

    The canonical URL is https://shop.thekidlaroi.com/.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://shop.thekidlaroi.com/sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), 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.

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://shop.thekidlaroi.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://shop.thekidlaroi.com/policies/refund-policy, https://shop.thekidlaroi.com/policies/privacy-policy, https://shop.thekidlaroi.com/policies/terms-of-service, https://shop.thekidlaroi.com/policies/shipping-policy and https://shop.thekidlaroi.com/policies/contact-information have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://shop.thekidlaroi.com/products/before-i-forget-vinyl has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://shop.thekidlaroi.com/policies/contact-information 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.

  • 6 internal pages checked

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

5 checks passed
  • Linked pages load

    All 6 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 6 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 8 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Required ref "headerDrawerContainer" not found in component header-component”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 67 words

    The homepage has only about 67 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.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP” and “Sign up”.

  • 2 calls to action

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

  • 3 short forms

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

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

  • 13 cookies set on arrival

    13

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

  • 24 other companies contacted

    Loading the homepage contacts 24 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 tklmerch.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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geo Pro Geolocation · Orderlogic Min Max Limits · Klaviyo Email Marketing Sms · Easylocation

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

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 32 issues on tklmerch.com, including 15 speed issues, 1 SEO issue 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