Website review, no card needed

kwik.delivery logo

kwik.delivery website review

Visit site (opens in a new tab)Reviewed 21 October 202652 issues · 87 checks

This review found 52 issues worth fixing on kwik.delivery, 23 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
5.1 s4.0 sMay 2Oct 174.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.2 s
May 9, 20264.2 s
May 16, 20264.3 s
May 23, 20264.5 s
May 30, 20264.7 s
Jun 6, 20264.8 s
Jun 13, 20265.0 s
Jun 20, 20264.9 s
Jun 27, 20265.0 s
Jul 4, 20265.0 s
Jul 11, 20264.7 s
Jul 18, 20264.5 s
Jul 25, 20264.2 s
Aug 1, 20264.2 s
Aug 8, 20264.3 s
Aug 15, 20264.5 s
Aug 22, 20264.5 s
Aug 29, 20264.5 s
Sep 5, 20264.5 s
Sep 12, 20264.4 s
Sep 19, 20264.5 s
Sep 26, 20264.7 s
Oct 3, 20264.7 s
Oct 10, 20264.6 s
Oct 17, 20264.7 s
Real-visitor tap response (INP)75th percentile, phones
217 ms113 msMay 2Oct 17142 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026147 ms
May 9, 2026145 ms
May 16, 2026161 ms
May 23, 2026169 ms
May 30, 2026188 ms
Jun 6, 2026195 ms
Jun 13, 2026197 ms
Jun 20, 2026204 ms
Jun 27, 2026198 ms
Jul 4, 2026205 ms
Jul 11, 2026194 ms
Jul 18, 2026193 ms
Jul 25, 2026186 ms
Aug 1, 2026169 ms
Aug 8, 2026169 ms
Aug 15, 2026161 ms
Aug 22, 2026157 ms
Aug 29, 2026144 ms
Sep 5, 2026130 ms
Sep 12, 2026128 ms
Sep 19, 2026125 ms
Sep 26, 2026130 ms
Oct 3, 2026139 ms
Oct 10, 2026139 ms
Oct 17, 2026142 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 kwik.delivery (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kwik.delivery at 0.5 s0.5 s
  2. kwik.delivery at 0.9 s0.9 s
  3. kwik.delivery at 1.4 s1.4 s
  4. kwik.delivery at 1.8 s1.8 s
  5. kwik.delivery at 2.3 s2.3 s
  6. kwik.delivery at 2.7 s2.7 s
  7. kwik.delivery at 3.2 s3.2 s
  8. kwik.delivery at 3.6 s3.6 s

Speed

8 to fix30
  • Use efficient cache lifetimes

    3.8 s · 1.6 MB

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

  • Improve image delivery

    2.6 s · 1.3 MB

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

  • Reduce unused JavaScript

    2.7 s · 557 KiB

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

  • Render-blocking requests

    2.0 s

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

  • Mobile performance score: 30

    30/100

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

  • Reduce unused CSS

    600 ms · 125 KiB

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

  • Main-thread work: 2.7 s

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

  • Google CDN adds 142 ms

    142 ms

    Google CDN costs a phone 142 ms of main-thread work and 351 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.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google/Doubleclick Ads, Google CDN and Hotjar and others), adding 893 KiB and 497 ms of main-thread time.

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 163 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.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

12 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 LCP: 6.6 s

    6.6 s

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

  • Real-user CLS: 0.72

    0.72

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Real-user TTFB: 2.2 s

    2.2 s

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

  • Largest Contentful Paint: 17.8 s

    17.8 s

    Your largest element takes 17.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “THE MARKETPLACE FOR ON-DEMAND LOGISTICS SERVICES IN AFRICA”.

  • Time to Interactive: 18.1 s

    18.1 s

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

  • Cumulative Layout Shift: 0.868

    0.868

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

  • First Contentful Paint: 4.9 s

    4.9 s

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

  • Speed Index: 6.7 s

    6.7 s

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

  • Total Blocking Time: 266 ms

    266 ms

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

  • 18 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -4%

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

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

    +10%

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

1 checks passed
  • Real-user INP: 159 ms

    159 ms

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

Images and page weight

4 to fix58
  • Page weight: 3.2 MB in 91 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 91 requests on a phone: images 1.9 MB (32), scripts 933 KiB (26) and stylesheets 172 KiB (20). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (1.3 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.

  • 6 images below the first screen load straight away

    6 images further down the page (1,007 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    84 KiB

    1 image is downloaded at several times the size a phone draws it, for example SCR-20240901-1fg.jpeg at 657 px wide, shown at 68 px. Resized copies would save about 84 KiB.

  • About 0.9 g of CO₂ per visit

    0.91 g

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

Accessibility

9 to fixGoogle 7787
  • 31 text elements with low contrast

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

  • 3 tap targets too small

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

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • 22 images without alt text

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

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

    All page content should be contained by landmarks: 27 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.

  • 9 links without text

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

  • 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 (h3 → h5, h2 → h6 and h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 10 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 6975
  • No meta description

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

  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“the marketplacefor on-demandlogistics servicesin …” and “Work with Kwik today !”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 32 internal links, 15 external

    The homepage links to 32 pages on kwik.delivery and 15 external pages.

4 checks passed
  • Title: 36 characters

    Your title is a healthy 36 characters: “Kwik – ecommerce logistics made easy”.

  • Canonical URL set

    The canonical URL is https://kwik.delivery/.

  • 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://kwik.delivery/wp-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://kwik.delivery/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 (1,543 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix53
  • 2 linked pages are broken

    Your homepage links to https://kwik.delivery/kwiksters and https://kwik.delivery/job-offers, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages share a title

    https://kwik.delivery/home/contact and https://kwik.delivery/contact all use the title “Contact Kwik – Kwik”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://kwik.delivery/corporate-clients, https://kwik.delivery/alibaba-ggs, https://kwik.delivery/payment, https://kwik.delivery/agent-network, https://kwik.delivery/home/contact and https://kwik.delivery/news and 7 others have 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://kwik.delivery/payment, whose canonical is https://kwik.delivery/home/payment. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    https://kwik.delivery/alibaba-ggs, https://kwik.delivery/pricing, https://kwik.delivery/joining-alibaba-com-what-does-it-mean-exactly, https://kwik.delivery/momo-by-mtn-partners-with-kwik-africa-to-revolutionise-payment-system-in-logistics and https://kwik.delivery/why-warehousing-is-the-best-way-to-store-inventory have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://kwik.delivery/home/contact, https://kwik.delivery/pricing and https://kwik.delivery/areas-covered 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.

  • 15 internal pages checked

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

2 checks passed
  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 3 small tap targets

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

  • 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 “$ is not a function”.

  • 1 low-resolution image

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

3 checks passed
  • 17 calls to action

    The homepage has 17 calls to action, for example “Contact Kwik”, “Make/Request a delivery” and “Apply Now”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Hotjar.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 2 cookies set on arrival

    2

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

  • 11 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on kwik.delivery, including 20 speed issues, 6 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