Website review, no card needed

vocasia.id logo

vocasia.id website review

Visit site (opens in a new tab)Reviewed 19 October 202653 issues · 83 checks

This review found 53 issues worth fixing on vocasia.id, 21 of them high impact, across 83 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

Full-page screenshot of vocasia.id (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. vocasia.id at 0.6 s0.6 s
  2. vocasia.id at 1.2 s1.2 s
  3. vocasia.id at 1.9 s1.9 s
  4. vocasia.id at 2.5 s2.5 s
  5. vocasia.id at 3.1 s3.1 s
  6. vocasia.id at 3.7 s3.7 s
  7. vocasia.id at 4.3 s4.3 s
  8. vocasia.id at 5.0 s5.0 s

Speed

11 to fix37
  • Improve image delivery

    1.2 s · 3.1 MB

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

  • Reduce unused JavaScript

    3.1 s · 895 KiB

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

  • Mobile performance score: 37

    37/100

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

  • Use efficient cache lifetimes

    1.3 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Google CDN and others), adding 3.0 MB and 533 ms of main-thread time.

  • Render-blocking requests

    600 ms

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

  • Google Tag Manager adds 464 ms

    464 ms

    Google Tag Manager costs a phone 464 ms of main-thread work and 888 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: 3.1 s

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

  • 13 long tasks on the main thread

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

  • noentic.com adds 0 ms

    0 ms

    noentic.com costs a phone 0 ms of main-thread work and 2.0 MB 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.

  • 1,841 HTML elements

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

  • Legacy JavaScript

    24 KiB

    Polyfills for old browsers add 24 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    22 KiB

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

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

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

6 to fix42
  • Largest Contentful Paint: 18.9 s

    18.9 s

    Your largest element takes 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Yuk cek status sertifikat kamu. Cek Status Sertifikat”.

  • Time to Interactive: 22.5 s

    22.5 s

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

  • First Contentful Paint: 6.3 s

    6.3 s

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

  • Speed Index: 8.5 s

    8.5 s

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

  • Cumulative Layout Shift: 0.207

    0.207

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

  • Total Blocking Time: 414 ms

    414 ms

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

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

Images and page weight

5 to fix18
  • Page weight: 5.5 MB in 162 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 162 requests on a phone: images 3.6 MB (38), scripts 1.6 MB (71) and other files 184 KiB (42). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    1772172543_ce7606dadecd2f9156ae.png weighs 951 KiB. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    1.0 MB

    5 images are downloaded at several times the size a phone draws them, for example 1772172543_ce7606dadecd2f9156ae.png at 1,582 px wide, shown at 358 px. Resized copies would save about 1.0 MB.

  • 6 images in older formats

    6 images (2.0 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.

  • 2 images below the first screen load straight away

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

  • About 1.6 g of CO₂ per visit

    1.56 g

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

Accessibility

10 to fixGoogle 6783
  • Invalid ARIA attributes

    20 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 12 buttons without a name

    12 buttons have no accessible name, so screen readers announce just “button”.

  • Images must have alternative text (6 elements)

    Images must have alternative text: 6 elements on the page fail this check, rated critical by axe-core.

  • 9 tap targets too small

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

  • 6 text elements with low contrast

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

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • No page language

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

1 checks passed
  • 40 automated accessibility rules passed

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

SEO

7 to fixGoogle 9175
  • 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 Join Bersama Affiliator Vocasia” and “Raih .css-1nyyqq1{color:var(--chakra-colors-red-5…”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

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

  • No XML sitemap

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

  • No robots.txt

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 16 internal links, 9 external

    The homepage links to 16 pages on vocasia.id and 9 external pages.

2 checks passed
  • Meta description: 143 characters

    Your meta description is 143 characters: “Situs kursus online bersertifikat terbaik untuk meningkatkan kemampuan & keterampilan di berbagai bidang bagi mahasiswa…”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Kursus Online Bersertifikasi Terbaik No. 1 Di Indonesia | Vocasia”.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    37%

    The HTML your server sends has 234 of the 632 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

3 to fix75
  • 3 pages without a title

    https://vocasia.id/help, https://vocasia.id/contact and https://vocasia.id/press-kit have no <title>, so Google invents the link text in results.

  • 6 pages without a meta description

    https://vocasia.id/msearch, https://vocasia.id/help, https://vocasia.id/contact, https://vocasia.id/syarat-ketentuan, https://vocasia.id/privacy-policy and https://vocasia.id/press-kit have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://vocasia.id/msearch, https://vocasia.id/help, https://vocasia.id/contact, https://vocasia.id/bootcamp/refund-policies, https://vocasia.id/syarat-ketentuan and https://vocasia.id/privacy-policy and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://vocasia.id/press-kit has 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.

  • 7 internal pages checked

    We fetched 7 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 7376
  • 6 broken images

    6 images failed to load on a phone, for example https://api.vocasia.id/uploads/system/cs-wa.png.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://blog.vocasia.id/wp-json/wp/v2/posts?per_page=4' from origin 'https://vocasia.id' has been b…”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    82 of 84 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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: 43 customer or partner logos. 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 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 632 words of copy

    The homepage carries about 632 words of visible text.

1 checks passed
  • 1 short form

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 4 cookies set on arrival

    4

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

  • 14 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Next.js
Hosting
Vercel

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on vocasia.id, including 17 speed issues, 7 SEO issues and 5 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