Website review, no card needed

kwikcharger.com logo

kwikcharger.com website review

Visit site (opens in a new tab)Reviewed 7 November 202639 issues · 77 checks

This review found 39 issues worth fixing on kwikcharger.com, 13 of them high impact, across 77 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

Full-page screenshot of kwikcharger.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kwikcharger.com at 0.4 s0.4 s
  2. kwikcharger.com at 0.8 s0.8 s
  3. kwikcharger.com at 1.3 s1.3 s
  4. kwikcharger.com at 1.7 s1.7 s
  5. kwikcharger.com at 2.1 s2.1 s
  6. kwikcharger.com at 2.5 s2.5 s
  7. kwikcharger.com at 2.9 s2.9 s
  8. kwikcharger.com at 3.4 s3.4 s

Speed

9 to fix51
  • Render-blocking requests

    1.6 s

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

  • Reduce unused JavaScript

    1.0 s · 407 KiB

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

  • Use efficient cache lifetimes

    950 ms · 542 KiB

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

  • Mobile performance score: 51

    51/100

    Your mobile performance score is 51. 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 (Klevu Search, Google Maps and Google Tag Manager and others), adding 1.3 MB and 530 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • 2,272 HTML elements

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

  • Google Maps adds 99 ms

    99 ms

    Google Maps costs a phone 99 ms of main-thread work and 398 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.

  • mothercare.co.id adds 75 ms

    75 ms

    mothercare.co.id costs a phone 75 ms of main-thread work and 434 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.

  • Legacy JavaScript

    150 ms · 7 KiB

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

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

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

  • Server response: 436 ms

    436 ms

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

Core Web Vitals

6 to fix52
  • Largest Contentful Paint: 8.2 s

    8.2 s

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

  • Time to Interactive: 14.9 s

    14.9 s

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

  • First Contentful Paint: 3.8 s

    3.8 s

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

  • Total Blocking Time: 538 ms

    538 ms

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

  • Speed Index: 5.0 s

    5.0 s

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

  • 16 images without width and height

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix83
  • Page weight: 2.1 MB in 213 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 213 requests on a phone: scripts 1.1 MB (131), other files 514 KiB (46) and images 465 KiB (28). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    google-en.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 below the first screen load straight away

    1 image further down the page (254 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.59 g

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

2 checks passed
  • 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

10 to fixGoogle 7385
  • Form elements must have labels (2 elements)

    Form elements must have labels: 2 elements on the page fail this check, rated critical by axe-core.

  • 52 text elements with low contrast

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

  • 13 tap targets too small

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

  • ARIA dialog and alertdialog nodes should have an accessible name (2 elements)

    ARIA dialog and alertdialog nodes should have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 3 images without alt text

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

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

  • 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 (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

4 to fixGoogle 9279
  • Title is long (72 characters)

    Your title is 72 characters, so Google will cut it off around 60: “SLOTMACAU188 | Eksplorasi Dunia Online dengan Ide Segar dan Wawasan Baru”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“SLOTMACAU188 | Eksplorasi Dunia Online dengan Ide…” and “SLOTMACAU188 | Eksplorasi Dunia Online dengan Ide…”). One clear main headline is easier for people and search engines.

  • Meta description is long (202 characters)

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

  • Structured data has 2 problems

    Structured data found (BreadcrumbList, FAQPage and Organization) but with 2 problems, for example “Organization: logo is not an absolute URL ("https://www.mcwhirterfoundation.org/images/logo.webp")”.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 389 internal links, 81 external

    The homepage links to 389 pages on kwikcharger.com and 81 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://mcwhirterfoundation.org/gallery/.

  • 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 http://www.mcwhirterfoundation.org/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.mcwhirterfoundation.org/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: 6 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix0
  • 15 linked pages are broken

    Your homepage links to https://www.mcwhirterfoundation.org/brand-a-z/addo.html, https://www.mcwhirterfoundation.org/brand-a-z/adidas.html, https://www.mcwhirterfoundation.org/brand-a-z/airfree.html, https://www.mcwhirterfoundation.org/brand-a-z/alamii.html, https://www.mcwhirterfoundation.org/brand-a-z/amara.html and https://www.mcwhirterfoundation.org/brand-a-z/aqua-scale.html and 9 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 15 internal pages checked

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

Best practices

6 to fixGoogle 4277
  • 285 small tap targets

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

  • 3 third-party cookies

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.mothercare.co.id/static/version1741963345/frontend/Codilar/mothercare/id_ID/fonts/mother…”.

  • No character set

    No character set is declared, so some characters can render as gibberish.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 4 low-resolution images

    4 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “download apps” and “Contact Us”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “download apps”, “Contact Us” and “contact us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 4 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 5 cookies set on arrival

    5

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

  • 22 other companies contacted

    Loading the homepage contacts 22 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 kwikcharger.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
E-commerce
Magento
Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on kwikcharger.com, including 15 speed issues and 4 SEO issues. 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