Website review, no card needed

clipan.co.id logo

clipan.co.id website review

Visit site (opens in a new tab)Reviewed 29 October 202618 issues · 51 checks

This review found 18 issues worth fixing on clipan.co.id, 10 of them high impact, across 51 checks. The most urgent: fails Core Web Vitals for real visitors. 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
8.1 s3.5 sMay 9Oct 245.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.0 s
May 16, 20264.4 s
May 23, 20264.7 s
May 30, 20264.8 s
Jun 6, 20264.9 s
Jun 13, 20264.8 s
Jun 20, 20264.9 s
Jun 27, 20265.1 s
Jul 4, 20265.4 s
Jul 11, 20266.0 s
Jul 18, 20267.4 s
Jul 25, 20267.6 s
Aug 1, 20266.9 s
Aug 8, 20266.3 s
Aug 15, 20265.7 s
Aug 22, 20265.8 s
Aug 29, 20266.1 s
Sep 5, 20266.3 s
Sep 12, 20266.5 s
Sep 19, 20266.1 s
Sep 26, 20266.4 s
Oct 3, 20266.0 s
Oct 10, 20265.6 s
Oct 17, 20265.9 s
Oct 24, 20265.5 s
Real-visitor tap response (INP)75th percentile, phones
244 ms185 msMay 9Oct 24210 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026205 ms
May 16, 2026206 ms
May 23, 2026204 ms
May 30, 2026199 ms
Jun 6, 2026193 ms
Jun 13, 2026193 ms
Jun 20, 2026192 ms
Jun 27, 2026192 ms
Jul 4, 2026196 ms
Jul 11, 2026207 ms
Jul 18, 2026213 ms
Jul 25, 2026230 ms
Aug 1, 2026225 ms
Aug 8, 2026215 ms
Aug 15, 2026215 ms
Aug 22, 2026221 ms
Aug 29, 2026217 ms
Sep 5, 2026227 ms
Sep 12, 2026228 ms
Sep 19, 2026215 ms
Sep 26, 2026227 ms
Oct 3, 2026237 ms
Oct 10, 2026230 ms
Oct 17, 2026216 ms
Oct 24, 2026210 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 clipan.co.id (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. clipan.co.id at 0.4 s0.4 s
  2. clipan.co.id at 0.8 s0.8 s
  3. clipan.co.id at 1.1 s1.1 s
  4. clipan.co.id at 1.5 s1.5 s
  5. clipan.co.id at 1.9 s1.9 s
  6. clipan.co.id at 2.3 s2.3 s
  7. clipan.co.id at 2.6 s2.6 s
  8. clipan.co.id at 3.0 s3.0 s

Speed

100
  • Render-blocking requests

    150 ms

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

  • Use efficient cache lifetimes

    9 KiB

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

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

3 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.0 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

7 to fix0
  • 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.49

    0.49

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

  • Real-user FCP: 5.4 s

    5.4 s

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

  • Real-user TTFB: 4.8 s

    4.8 s

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

  • Real-user INP: 233 ms

    233 ms

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

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

    +35%

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

  • Tap response (INP) held steady for real visitors

    +4%

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

6 checks passed
  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.8 s

    0.8 s

    The first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 0.8 s

    0.8 s

    Your largest element renders in 0.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “This website is using a security service to protect itself …”.

  • Speed Index: 0.8 s

    0.8 s

    Visually, the page fills in at 0.8 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 0.8 s

    0.8 s

    The page is fully interactive after 0.8 s.

Images and page weight

100
  • About 0.00 g of CO₂ per visit

    0.00 g

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

1 checks passed
  • Page weight: 11 KiB in 4 requests

    11 KiB

    Your homepage downloads 11 KiB in 4 requests on a phone: stylesheets 5 KiB (1), images 4 KiB (2) and HTML 2 KiB (1). That is a lean page.

Accessibility

1 to fix96
  • 3 links without text

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

  • No main landmark

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

1 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

SEO

7 to fixGoogle 4051
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Error status code

    The page answers with an error status, so search engines may drop it.

  • No structured data

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

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

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

  • 34 internal links, 12 external

    The homepage links to 34 pages on clipan.co.id and 12 external pages.

4 checks passed
  • Title: 44 characters

    Your title is a healthy 44 characters: “Clipan Finance – Kredit Mobil Baru dan Bekas”.

  • Canonical URL set

    The canonical URL is https://clipan.co.id/.

  • 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://clipan.co.id/wp-sitemap.xml.

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://clipan.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

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

1 to fixGoogle 9693
  • 1 console error

    1 error was logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 403 (Forbidden)”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • 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 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 411 words of copy

    The homepage carries about 411 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Call Center1500 375”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

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

CMS
WordPress
Framework
jQuery
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 18 issues on clipan.co.id, including 7 speed issues, 7 SEO issues and 1 conversion gap. 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