Website review, no card needed

k-ecommerce.com logo

k-ecommerce.com website review

Visit site (opens in a new tab)Reviewed 18 October 202632 issues · 83 checks

This review found 32 issues worth fixing on k-ecommerce.com, 9 of them high impact, across 83 checks. The most urgent: render-blocking requests. 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
6.9 s2.5 sApr 25Oct 103.1 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.3 s
May 2, 20263.6 s
May 9, 20263.6 s
May 16, 20263.6 s
May 23, 20263.7 s
May 30, 20263.9 s
Jun 6, 20263.9 s
Jun 13, 20263.8 s
Jun 20, 20263.9 s
Jun 27, 20264.9 s
Jul 4, 20265.1 s
Jul 11, 20265.9 s
Jul 18, 20266.4 s
Jul 25, 20264.9 s
Aug 1, 20264.9 s
Aug 8, 20265.0 s
Aug 15, 20264.8 s
Aug 22, 20264.3 s
Aug 29, 20264.1 s
Sep 5, 20263.6 s
Sep 12, 20263.0 s
Sep 19, 20263.4 s
Sep 26, 20263.2 s
Oct 3, 20263.1 s
Oct 10, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
683 ms69 msApr 25Oct 10172 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026612 ms
May 23, 2026187 ms
May 30, 2026172 ms
Jun 6, 2026209 ms
Jun 13, 2026223 ms
Jun 20, 2026239 ms
Jun 27, 2026272 ms
Jul 4, 2026239 ms
Jul 11, 2026210 ms
Jul 18, 2026167 ms
Jul 25, 2026161 ms
Aug 1, 2026167 ms
Aug 8, 2026171 ms
Aug 15, 2026162 ms
Aug 22, 2026151 ms
Aug 29, 2026147 ms
Sep 5, 2026145 ms
Sep 12, 2026140 ms
Sep 19, 2026155 ms
Sep 26, 2026167 ms
Oct 3, 2026167 ms
Oct 10, 2026172 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 k-ecommerce.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. k-ecommerce.com at 0.5 s0.5 s
  2. k-ecommerce.com at 1.1 s1.1 s
  3. k-ecommerce.com at 1.6 s1.6 s
  4. k-ecommerce.com at 2.1 s2.1 s
  5. k-ecommerce.com at 2.7 s2.7 s
  6. k-ecommerce.com at 3.2 s3.2 s
  7. k-ecommerce.com at 3.8 s3.8 s
  8. k-ecommerce.com at 4.3 s4.3 s

Speed

4 to fix72
  • Render-blocking requests

    1.9 s

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

  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72 (desktop: 98). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    380 ms · 87 KiB

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

  • Improve image delivery

    300 ms · 60 KiB

    2 images could be 60 KiB 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (wpmucdn.com, JSDelivr CDN and Google Fonts and others), adding 247 KiB and 193 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Reduce unused CSS

    18 KiB

    About 18 KiB of CSS is downloaded but never applied on this page.

  • Phones get a much slower page than desktops

    Desktop scores 98 but mobile only 72. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

  • Server response: 70 ms

    70 ms

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

Core Web Vitals

9 to fix33
  • 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.

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Largest Contentful Paint: 4.5 s

    4.5 s

    Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (2.0 s).

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user CLS: 0.20

    0.20

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Speed Index: 4.8 s

    4.8 s

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

  • Time to Interactive: 4.5 s

    4.5 s

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

4 checks passed
  • Real-user INP: 179 ms

    179 ms

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

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

    -58%

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

  • Total Blocking Time: 178 ms

    178 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.15 g

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

4 checks passed
  • Page weight: 551 KiB in 25 requests

    551 KiB

    Your homepage downloads 551 KiB in 25 requests on a phone: scripts 165 KiB (6), images 161 KiB (9) and fonts 140 KiB (8). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

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

  • Images are sized for phones

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

Accessibility

10 to fixGoogle 8088
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 39 tap targets too small

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

  • ARIA input fields must have an accessible name (2 elements)

    ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails 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.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

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

  • 4 links without text

    4 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 skip levels

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

2 checks passed
  • Every image has alt text

    All 41 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 9 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 9286
  • 3 H1 headlines

    There are 3 <h1> headlines (“Built for B2B Ecommerce, Powered by ERP Integrati…”, “Built for B2B Ecommerce, Powered by ERP Integrati…” and “What makes k-ecommerce so powerful?”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (Corporation, Organization and SiteNavigationElement) but with 1 problem, for example “Organization: review is an empty list”.

  • No social preview image

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

  • 7 links with vague text

    7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 166 internal links, 7 external

    The homepage links to 166 pages on k-ecommerce.com and 7 external pages.

5 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “K-ecommerce is the B2B online commerce and payment solution that uses ERP data to support high volume operations and pe…”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “B2B Ecommerce Platform, Powered by ERP | k-ecommerce”.

  • Canonical URL set

    The canonical URL is https://k-ecommerce.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://k-ecommerce.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://k-ecommerce.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: 4 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,387 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 45 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 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 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

    51 of 54 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • 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.

  • Thin social proof

    Social proof on the homepage: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 263 words of copy

    The homepage carries about 263 words of visible text.

4 checks passed
  • 20 calls to action

    The homepage has 20 calls to action, for example “Pricing”, “Watch demo” and “Interactive Demo”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Hotjar, HubSpot and Matomo.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

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

  • 5 other companies contacted

    Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 k-ecommerce.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager | Hotjar | Matomo

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 k-ecommerce.com, including 13 speed issues, 4 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