Website review, no card needed

smsfinance.co.id logo

smsfinance.co.id website review

Visit site (opens in a new tab)Reviewed 3 November 202646 issues · 82 checks

This review found 46 issues worth fixing on smsfinance.co.id, 18 of them high impact, across 82 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
6.4 s1.7 sMay 16Oct 315.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.7 s
May 23, 20262.6 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.8 s
Jun 20, 20262.7 s
Jun 27, 20263.0 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.7 s
Jul 25, 20263.1 s
Aug 1, 20262.5 s
Aug 8, 20262.3 s
Aug 15, 20263.0 s
Aug 22, 20264.5 s
Aug 29, 20264.9 s
Sep 5, 20265.1 s
Sep 12, 20265.0 s
Sep 19, 20264.5 s
Sep 26, 20263.8 s
Oct 3, 20263.5 s
Oct 10, 20263.8 s
Oct 17, 20264.9 s
Oct 24, 20265.6 s
Oct 31, 20265.9 s
Real-visitor tap response (INP)75th percentile, phones
395 ms170 msMay 16Oct 31369 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026207 ms
May 23, 2026203 ms
May 30, 2026206 ms
Jun 6, 2026196 ms
Jun 13, 2026205 ms
Jun 20, 2026207 ms
Jun 27, 2026225 ms
Jul 4, 2026266 ms
Jul 11, 2026283 ms
Jul 18, 2026286 ms
Jul 25, 2026259 ms
Aug 1, 2026222 ms
Aug 8, 2026209 ms
Aug 15, 2026250 ms
Aug 22, 2026340 ms
Aug 29, 2026355 ms
Sep 5, 2026357 ms
Sep 12, 2026346 ms
Sep 19, 2026302 ms
Sep 26, 2026271 ms
Oct 3, 2026260 ms
Oct 10, 2026271 ms
Oct 17, 2026329 ms
Oct 24, 2026357 ms
Oct 31, 2026369 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 smsfinance.co.id (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. smsfinance.co.id at 0.9 s0.9 s
  2. smsfinance.co.id at 1.8 s1.8 s
  3. smsfinance.co.id at 2.6 s2.6 s
  4. smsfinance.co.id at 3.5 s3.5 s
  5. smsfinance.co.id at 4.4 s4.4 s
  6. smsfinance.co.id at 5.2 s5.2 s
  7. smsfinance.co.id at 6.1 s6.1 s
  8. smsfinance.co.id at 7.0 s7.0 s

Speed

8 to fix46
  • Improve image delivery

    2.5 s · 1.7 MB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 46

    46/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, TikTok and Google/Doubleclick Ads and others), adding 677 KiB and 656 ms of main-thread time.

  • Google Tag Manager adds 536 ms

    536 ms

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

  • Font display

    500 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).

  • 5 long tasks on the main thread

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

  • Reduce unused JavaScript

    275 KiB

    About 275 KiB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    160 ms · 46 KiB

    About 46 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.

  • Minify JavaScript

    160 ms · 25 KiB

    25 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    16 KiB

    Polyfills for old browsers add 16 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.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

  • Use efficient cache lifetimes

    1 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

2 checks passed
  • Main-thread work: 1.5 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

14 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 CLS: 0.31

    0.31

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

  • Largest Contentful Paint: 10.2 s

    10.2 s

    Your largest element takes 10.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: 16.7 s

    16.7 s

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

  • Speed Index: 9.7 s

    9.7 s

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

  • Cumulative Layout Shift: 0.278

    0.278

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user INP: 206 ms

    206 ms

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

  • Tap response (INP) got 77% slower for real visitors

    +77%

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

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

    +118%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

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

  • 3 images without width and height

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

1 checks passed
  • First Contentful Paint: 1.7 s

    1.7 s

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

Images and page weight

5 to fix43
  • 1 image over 500 KB

    Waspada-Black-Mold-di-Rumah-Bahaya-untuk-Kesehatan-SMS.png weighs 1.2 MB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.4 MB in 62 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 62 requests on a phone: images 2.1 MB (13), scripts 846 KiB (18) and fonts 435 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

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

  • 4 images below the first screen load straight away

    4 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 5 images far larger than shown

    283 KiB

    5 images are downloaded at several times the size a phone draws them, for example Waspada-Black-Mold-di-Rumah-Bahaya-untuk-Kesehatan-SMS.png at 1,086 px wide, shown at 360 px. Resized copies would save about 283 KiB.

  • About 1.0 g of CO₂ per visit

    0.98 g

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

Accessibility

10 to fixGoogle 7185
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 4 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • 7 images without alt text

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

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

    All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.

  • 14 links without text

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

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (6 elements)

    Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 8589
  • No structured data

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

  • 7 H1 headlines

    There are 7 <h1> headlines (“”, “” and “Solusi Pembiayaan Anda”). One clear main headline is easier for people and search engines.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 72 internal links, 15 external

    The homepage links to 72 pages on smsfinance.co.id and 15 external pages.

6 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Butuh pinjaman dana mendesak atau kredit mobil bekas? Ajukan sekarang juga di SMS Finance. Proses mudah, cepat, dan bun…”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “SMS Finance - Pinjaman dengan Jaminan BPKB Mobil Cepat”.

  • Canonical URL set

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

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.smsfinance.co.id/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://www.smsfinance.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.

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 (510 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

1 to fixGoogle 9293
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Loading the script 'https://static.cloudflareinsights.com/beacon.min.js/vce701823e78c4301a35b7e07294d87301792088814092'…”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    30 of 32 tappable elements near the top are at least 24 px.

  • 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: 1 customer or partner logo. 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 306 words of copy

    The homepage carries about 306 words of visible text.

3 checks passed
  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager 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
  • 4 trackers load before any consent

    4

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

  • 9 cookies set on arrival

    9

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

  • 8 other companies contacted

    Loading the homepage contacts 8 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 smsfinance.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

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Cloudflare

Hiring

Hiring
2 open roles
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on smsfinance.co.id, including 22 speed issues, 3 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