Website review, no card needed

kratomdirect.com logo

kratomdirect.com website review

Visit site (opens in a new tab)Reviewed 17 November 202641 issues · 81 checks

This review found 41 issues worth fixing on kratomdirect.com, 12 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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 kratomdirect.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix54
  • Reduce unused JavaScript

    3.8 s · 777 KiB

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

  • Improve image delivery

    4.0 MB

    12 images could be 4.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 54

    54/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Judge.me and Shopify and others), adding 1.5 MB and 656 ms of main-thread time.

  • Render-blocking requests

    750 ms

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

  • Reduce unused CSS

    600 ms · 137 KiB

    About 137 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.

  • YouTube adds 345 ms

    345 ms

    YouTube costs a phone 345 ms of main-thread work and 999 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.

  • Use efficient cache lifetimes

    300 ms · 44 KiB

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

  • Main-thread work: 2.4 s

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

  • 1,633 HTML elements

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

  • Shopify adds 87 ms

    87 ms

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

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

5 to fix64
  • Largest Contentful Paint: 30.9 s

    30.9 s

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

  • Time to Interactive: 32.2 s

    32.2 s

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

  • First Contentful Paint: 6.1 s

    6.1 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • 32 images without width and height

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

2 checks passed
  • Total Blocking Time: 146 ms

    146 ms

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

  • Cumulative Layout Shift: 0.072

    0.072

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

Images and page weight

4 to fix28
  • Page weight: 8.1 MB in 269 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 269 requests on a phone: images 5.2 MB (73), scripts 1.5 MB (55) and other files 901 KiB (117). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

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

  • 8 images far larger than shown

    3.2 MB

    8 images are downloaded at several times the size a phone draws them, for example Product_Posters_36_x_24_in_36_x_20_in_36_x_19.5_in_36_x_19_i at 3,456 px wide, shown at 350 px. Resized copies would save about 3.2 MB.

  • 12 images below the first screen load straight away

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

  • About 2.3 g of CO₂ per visit

    2.29 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.29 g of CO₂e: 275.3 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

8 to fixGoogle 8091
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 11 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

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

  • 35 links without text

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

  • 2 form fields without a label

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

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

  • Headings skip levels

    Headings skip levels (h2 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 79 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

6 to fixGoogle 8576
  • Title is long (77 characters)

    Your title is 77 characters, so Google will cut it off around 60: “Kratom Direct. MIT45, Super K, K-Chill, HUSH @ Lowest Prices! – Kratom Direct”.

  • Meta description is long (220 characters)

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

  • Structured data has 2 problems

    Structured data found (BreadcrumbList, Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • 2 links with vague text

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

  • 136 internal links, 1 external

    The homepage links to 136 pages on kratomdirect.com and 1 external page.

4 checks passed
  • Canonical URL set

    The canonical URL is https://kratomdirect.com/.

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

AI search readiness

100
  • No llms.txt

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

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.

  • Organization data: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 6991
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Identifier 'urlToPreload' has already been declared”.

  • 2 low-resolution images

    2 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
  • Tap targets are thumb-sized

    10 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 147 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 1,270 words of copy

    The homepage carries about 1,270 words of visible text.

4 checks passed
  • 18 calls to action

    The homepage has 18 calls to action, for example “Subscribe”, “Contact” and “K-Chill shop now”.

  • 20 short forms

    20 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 6 cookies set on arrival

    6

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

  • 20 other companies contacted

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

Apps your storefront loads

Blockify Age Verification · Age Verifier By Omega · Navidium Shipping Protection · smile.io · powr.io · hextom.com

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 41 issues on kratomdirect.com, including 16 speed issues, 6 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