Website review, no card needed

bcasyariah.co.id logo

bcasyariah.co.id website review

Visit site (opens in a new tab)Reviewed 26 October 202642 issues · 77 checks

This review found 42 issues worth fixing on bcasyariah.co.id, 22 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. 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.3 s3.8 sMay 9Oct 245.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.1 s
May 16, 20265.9 s
May 23, 20264.4 s
May 30, 20264.2 s
Jun 6, 20264.1 s
Jun 13, 20264.1 s
Jun 20, 20264.2 s
Jun 27, 20264.8 s
Jul 4, 20265.0 s
Jul 11, 20265.0 s
Jul 18, 20266.0 s
Aug 8, 20265.4 s
Aug 15, 20266.0 s
Aug 22, 20266.0 s
Aug 29, 20265.5 s
Sep 5, 20265.8 s
Sep 12, 20264.8 s
Sep 19, 20264.8 s
Sep 26, 20264.8 s
Oct 3, 20264.9 s
Oct 10, 20265.0 s
Oct 17, 20265.1 s
Oct 24, 20265.4 s
Real-visitor tap response (INP)75th percentile, phones
225 ms120 msMay 23Oct 24172 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026132 ms
May 30, 2026152 ms
Jun 6, 2026177 ms
Jun 13, 2026179 ms
Jun 20, 2026159 ms
Jun 27, 2026149 ms
Jul 4, 2026134 ms
Jul 11, 2026141 ms
Aug 29, 2026198 ms
Sep 5, 2026213 ms
Sep 12, 2026176 ms
Sep 19, 2026194 ms
Sep 26, 2026193 ms
Oct 3, 2026192 ms
Oct 10, 2026201 ms
Oct 17, 2026187 ms
Oct 24, 2026172 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 bcasyariah.co.id (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bcasyariah.co.id at 2.0 s2.0 s
  2. bcasyariah.co.id at 4.0 s4.0 s
  3. bcasyariah.co.id at 6.1 s6.1 s
  4. bcasyariah.co.id at 8.1 s8.1 s
  5. bcasyariah.co.id at 10.1 s10.1 s
  6. bcasyariah.co.id at 12.1 s12.1 s
  7. bcasyariah.co.id at 14.1 s14.1 s
  8. bcasyariah.co.id at 16.2 s16.2 s

Speed

15 to fix25
  • Use efficient cache lifetimes

    20.8 s · 5.9 MB

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

  • Render-blocking requests

    13.9 s

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

  • Reduce unused JavaScript

    7.2 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.2 s faster on a phone.

  • Improve image delivery

    4.1 s · 2.4 MB

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

  • Reduce unused CSS

    4.4 s · 800 KiB

    About 800 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.4 s faster on a phone.

  • Minify CSS

    3.7 s · 662 KiB

    662 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3.3 s · 527 KiB

    527 KiB could be saved by minifying JavaScript.

  • Font display

    2.5 s

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

  • Mobile performance score: 25

    25/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 931 KiB and 641 ms of main-thread time.

  • Document request latency

    550 ms · 78 KiB

    The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    572 ms

    Reduce initial server response time. Google estimates savings of 572 ms on a phone.

  • Google Tag Manager adds 388 ms

    388 ms

    Google Tag Manager costs a phone 388 ms of main-thread work and 510 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.2 s

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

  • Server response: 672 ms

    672 ms

    Your server takes 672 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    21 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Core Web Vitals

12 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.1 s

    6.1 s

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

  • Real-user CLS: 0.92

    0.92

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

  • Real-user FCP: 4.3 s

    4.3 s

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

  • First Contentful Paint: 14.8 s

    14.8 s

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

  • Largest Contentful Paint: 34.8 s

    34.8 s

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

  • Speed Index: 22.2 s

    22.2 s

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

  • Time to Interactive: 38.7 s

    38.7 s

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

  • Cumulative Layout Shift: 0.902

    0.902

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

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

    +26%

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

  • 54 images without width and height

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

  • Total Blocking Time: 268 ms

    268 ms

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

Images and page weight

1 to fix33
  • Page weight: 6.8 MB in 127 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 127 requests on a phone: images 3.7 MB (66), scripts 2.1 MB (19) and stylesheets 855 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 1.9 g of CO₂ per visit

    1.93 g

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

Accessibility

6 to fixGoogle 7865
  • 20 images without alt text

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

  • No main landmark

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

  • Zoom is disabled

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

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

  • 20 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

1 checks passed
  • 4 automated accessibility rules passed

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

SEO

3 to fixGoogle 9282
  • No H1 headline

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

  • No canonical URL

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

  • No XML sitemap

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

  • 264 internal links, 11 external

    The homepage links to 264 pages on bcasyariah.co.id and 11 external pages.

5 checks passed
  • Meta description: 137 characters

    Your meta description is 137 characters: “BCA Syariah berkomitmen untuk melayani Anda dengan lebih baik melalui ragam produk dan fasilitas perbankan syariah yang…”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “BCA Syariah - Andalan dan Pilihan Masyarakat”.

  • Structured data in place

    Structured data found: WebSite.

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

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.

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

2 to fix90
  • 1 page without a meta description

    https://bcasyariah.co.id/sahabatberkahmu has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://bcasyariah.co.id/sahabatberkahmu and https://bcasyariah.co.id/bsya-bcasyariah have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://bcasyariah.co.id/sahabatberkahmu and https://bcasyariah.co.id/bsya-bcasyariah took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    2 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has a title

    All 2 pages that loaded have a <title>.

Best practices

1 to fixGoogle 8892
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.bcasyariah.co.id/front/css/select2.min.css' from origin 'https://bcasyariah.co…”.

  • 2 low-resolution images

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

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 983 words of copy

    The homepage carries about 983 words of visible text.

5 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Download”.

  • 3 short forms

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

  • Social proof on the page

    Social proof on the homepage: 4 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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

  • 1 other company contacted

    Loading the homepage contacts 1 host 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 bcasyariah.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

Company

Founded
1991
Headquarters
East Jakarta

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on bcasyariah.co.id, including 27 speed issues, 3 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