Website review, no card needed

yokke.co.id logo

yokke.co.id website review

Visit site (opens in a new tab)Reviewed 3 November 202644 issues · 80 checks

This review found 44 issues worth fixing on yokke.co.id, 17 of them high impact, across 80 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
3.7 s2.8 sMay 16Oct 313.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.6 s
May 23, 20263.5 s
May 30, 20263.4 s
Jun 6, 20263.4 s
Jun 13, 20263.4 s
Jun 20, 20263.5 s
Jun 27, 20263.6 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.4 s
Jul 25, 20263.3 s
Aug 1, 20263.3 s
Aug 8, 20263.4 s
Aug 15, 20263.5 s
Aug 22, 20263.5 s
Aug 29, 20263.6 s
Sep 5, 20263.4 s
Sep 12, 20263.5 s
Sep 19, 20263.3 s
Sep 26, 20263.0 s
Oct 3, 20263.0 s
Oct 10, 20262.9 s
Oct 17, 20262.9 s
Oct 24, 20263.0 s
Oct 31, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
220 ms140 msMay 16Oct 31200 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026196 ms
May 23, 2026191 ms
May 30, 2026181 ms
Jun 6, 2026180 ms
Jun 13, 2026175 ms
Jun 20, 2026200 ms
Jun 27, 2026211 ms
Jul 4, 2026210 ms
Jul 11, 2026184 ms
Jul 18, 2026156 ms
Jul 25, 2026156 ms
Aug 1, 2026150 ms
Aug 8, 2026154 ms
Aug 15, 2026162 ms
Aug 22, 2026162 ms
Aug 29, 2026149 ms
Sep 5, 2026151 ms
Sep 12, 2026162 ms
Sep 19, 2026149 ms
Sep 26, 2026158 ms
Oct 3, 2026156 ms
Oct 10, 2026153 ms
Oct 17, 2026160 ms
Oct 24, 2026188 ms
Oct 31, 2026200 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 yokke.co.id (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. yokke.co.id at 0.9 s0.9 s
  2. yokke.co.id at 1.8 s1.8 s
  3. yokke.co.id at 2.7 s2.7 s
  4. yokke.co.id at 3.6 s3.6 s
  5. yokke.co.id at 4.6 s4.6 s
  6. yokke.co.id at 5.5 s5.5 s
  7. yokke.co.id at 6.4 s6.4 s
  8. yokke.co.id at 7.3 s7.3 s

Speed

10 to fix45
  • Improve image delivery

    5.0 s · 1.1 MB

    1 image could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.0 s faster on a phone.

  • Reduce unused JavaScript

    4.2 s · 845 KiB

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

  • Use efficient cache lifetimes

    1.3 s · 138 KiB

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

  • Mobile performance score: 45

    45/100

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Intercom and Facebook and others), adding 837 KiB and 858 ms of main-thread time.

  • Google Tag Manager adds 477 ms

    477 ms

    Google Tag Manager costs a phone 477 ms of main-thread work and 453 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.

  • 9 long tasks on the main thread

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

  • Legacy JavaScript

    300 ms · 32 KiB

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

  • Intercom adds 259 ms

    259 ms

    Intercom costs a phone 259 ms of main-thread work and 229 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.

  • Main-thread work: 2.5 s

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

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • 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: 470 ms

    470 ms

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

Core Web Vitals

10 to fix67
  • 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: 4.4 s

    4.4 s

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

  • Largest Contentful Paint: 19.8 s

    19.8 s

    Your largest element takes 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Yuk, beralih ke Yokke solusi terbaik untuk bisnis Anda”.

  • Time to Interactive: 19.9 s

    19.9 s

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

  • Speed Index: 11.9 s

    11.9 s

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

  • Total Blocking Time: 755 ms

    755 ms

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • 37 images without width and height

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Tap response (INP) held steady for real visitors

    0%

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

4 checks passed
  • Real-user INP: 156 ms

    156 ms

    Real visitors wait 156 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.

  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix67
  • Page weight: 3.5 MB in 64 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 64 requests on a phone: images 1.9 MB (34), scripts 1.4 MB (19) and fonts 137 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.00 g

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

Accessibility

8 to fixGoogle 6457
  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

  • Frames without titles

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

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Zoom is disabled

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 34 text elements with low contrast

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 49 images in the HTML carry an alt attribute.

  • 5 automated accessibility rules passed

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

SEO

6 to fixGoogle 10071
  • Title is short (16 characters)

    Your title is only 16 characters: “Beranda | Yokke!”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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 (“Yuk, beralih ke Yokke solusi terbaik untuk bisnis…” and “Sertifikasi ganda PCI Yokke dipercayai lebih dari…”). One clear main headline is easier for people and search engines.

  • Meta description is long (322 characters)

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

  • No XML sitemap

    No XML sitemap at https://www.yokke.co.id/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at yokke.co.id/robots.txt, the first file search crawlers ask for.

  • 58 internal links, 6 external

    The homepage links to 58 pages on yokke.co.id and 6 external pages.

2 checks passed
  • Canonical URL set

    The canonical URL is https://www.yokke.co.id/id.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

AI search readiness

1 to fix83
  • 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://www.yokke.co.id/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.

1 checks passed
  • AI answer engines may read the site

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

Other pages

5 to fix67
  • 12 pages without a title

    /, https://www.yokke.co.id/id/kategori-produk/omnichannel-platform, https://www.yokke.co.id/id/produk/yokke-biz, https://www.yokke.co.id/id/produk/yokke-biz-lite, https://www.yokke.co.id/id/kategori-produk/layanan-info-merchant and https://www.yokke.co.id/id/produk/layanan-info-mandiri and 6 others have no <title>, so Google invents the link text in results.

  • 12 linked pages hidden from search

    /, https://www.yokke.co.id/id/kategori-produk/omnichannel-platform, https://www.yokke.co.id/id/produk/yokke-biz, https://www.yokke.co.id/id/produk/yokke-biz-lite, https://www.yokke.co.id/id/kategori-produk/layanan-info-merchant and https://www.yokke.co.id/id/produk/layanan-info-mandiri and 6 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 12 pages without a meta description

    /, https://www.yokke.co.id/id/kategori-produk/omnichannel-platform, https://www.yokke.co.id/id/produk/yokke-biz, https://www.yokke.co.id/id/produk/yokke-biz-lite, https://www.yokke.co.id/id/kategori-produk/layanan-info-merchant and https://www.yokke.co.id/id/produk/layanan-info-mandiri and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages share a meta description

    https://www.yokke.co.id/id/kategori-produk/payment, https://www.yokke.co.id/id/produk/edc and https://www.yokke.co.id/id/produk/e-commerce use the same meta description. A description written for each page earns more clicks.

  • 12 pages without an H1

    /, https://www.yokke.co.id/id/kategori-produk/omnichannel-platform, https://www.yokke.co.id/id/produk/yokke-biz, https://www.yokke.co.id/id/produk/yokke-biz-lite, https://www.yokke.co.id/id/kategori-produk/layanan-info-merchant and https://www.yokke.co.id/id/produk/layanan-info-mandiri and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://www.yokke.co.id/id/kategori-produk/payment and https://www.yokke.co.id/id/produk/edc took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

Best practices

Google 92100
  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • Thin social proof

    Social proof on the homepage: 5 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 481 words of visible text.

3 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Direct contact links

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

Privacy and tracking

  • 3 cookies set on arrival

    3

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

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

Upkeep, stack and company

Stack

Hosting
Imperva

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on yokke.co.id, 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