Website review, no card needed

banksampoerna.com logo

banksampoerna.com website review

Visit site (opens in a new tab)Reviewed 1 November 202645 issues · 86 checks

This review found 45 issues worth fixing on banksampoerna.com, 17 of them high impact, across 86 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
1.5 s1.0 sMay 16Oct 241.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.1 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.3 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Sep 12, 20261.1 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.3 s
Oct 17, 20261.5 s
Oct 24, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
313 ms62 msJul 4Sep 19284 ms
Show as table
DateReal-visitor tap response (INP)
Jul 4, 2026120 ms
Jul 18, 2026100 ms
Aug 1, 202696 ms
Aug 8, 202693 ms
Aug 15, 202691 ms
Sep 19, 2026284 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 banksampoerna.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix55
  • Improve image delivery

    12.9 s · 14.8 MB

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

  • Use efficient cache lifetimes

    11.7 s · 12.3 MB

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

  • Reduce unused JavaScript

    1.6 s · 325 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

  • Font display

    550 ms

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

  • Google CDN adds 80 ms

    80 ms

    Google CDN costs a phone 80 ms of main-thread work and 352 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google CDN and Other Google APIs/SDKs and others), adding 599 KiB and 195 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 19 KiB

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

  • 3 long tasks on the main thread

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

  • 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

    3 KiB

    3 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.7 s

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

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 19.5 s

    19.5 s

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

  • Time to Interactive: 19.5 s

    19.5 s

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

  • Cumulative Layout Shift: 0.331

    0.331

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

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

    +70%

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

  • 51 images without width and height

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

  • Speed Index: 3.8 s

    3.8 s

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • 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 1.3 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 400 ms

    400 ms

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

  • Total Blocking Time: 75 ms

    75 ms

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

Images and page weight

3 to fix45
  • Page weight: 16.0 MB in 55 requests

    16.0 MB

    Your homepage downloads 16.0 MB in 55 requests on a phone: images 15.1 MB (31), scripts 633 KiB (8) and fonts 130 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 13.6 MB together. On a phone connection a single image that size takes seconds.

  • 14 images in older formats

    14 images (14.8 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.

  • 1 image below the first screen load straight away

    1 image further down the page (89 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 4.5 g of CO₂ per visit

    4.52 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 7789
  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 14 text elements with low contrast

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

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

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

  • 5 form fields without a label

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

  • 3 links without text

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

2 checks passed
  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

6 to fixGoogle 8570
  • No H1 headline

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

  • Title is short (22 characters)

    Your title is only 22 characters: “Bank Sahabat Sampoerna”. 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.

  • Meta description is long (312 characters)

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

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 22 internal links, 14 external

    The homepage links to 22 pages on banksampoerna.com and 14 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://banksampoerna.com/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at http://banksampoerna.com/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://banksampoerna.com/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

4 to fix76
  • 2 pages point its canonical at the homepage

    https://banksampoerna.com/setting/bahasa/42873d4d9d9bd42e572e662c0bb2c57b08802aa31a98e98d9e8de7cc90da9701a23802e12ea499a52a025f93b7f50b2e7e065ec60ac35d240ad5a4dffcd1878coAWkA0bd-MjmHO_KL2StjliuG_iWclW3PgiHNnzHgNo~/7ddfe9725dbd610195a1f33407899e8c1e51393abd990c7216b0c4e62d983ebd0a1c9929a7d9d525021e5601ef526a20e6b34ca62234004e5db389de5b45c8f3tQy26IO8RD061WRehnHd1ZZdfEmQQJRD2ymCeo-cFKJEbXTGBUl5j_tFhUX8NKVA and https://banksampoerna.com/setting/bahasa/b21d6d85cbab8b992a6c477b5551ba86ded3f7bbc2670143e03f82463f01d09a285c80224b4538f871846aa82ceffa43cb41e4e3701980d2b790c131f01add33V9QiRX6ytdvJ8E3K7oam9gBYBfUw78HDwCDP-DFnedo~/55887543cdd937b4081c59caa0193c2e5ab27a2ea8c47456c4c505926ca9121fd77c8831beefddd8ded2a40225e7870a6e13600356d4ccea6295134041f4decfQV7qhu6svED0L3Mn_Rn64LMXyMubHV1G_-90tEPfyaN6stZq096L9h2WWpmSJKip declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 5 pages share a title

    /, https://banksampoerna.com/setting/bahasa/42873d4d9d9bd42e572e662c0bb2c57b08802aa31a98e98d9e8de7cc90da9701a23802e12ea499a52a025f93b7f50b2e7e065ec60ac35d240ad5a4dffcd1878coAWkA0bd-MjmHO_KL2StjliuG_iWclW3PgiHNnzHgNo~/7ddfe9725dbd610195a1f33407899e8c1e51393abd990c7216b0c4e62d983ebd0a1c9929a7d9d525021e5601ef526a20e6b34ca62234004e5db389de5b45c8f3tQy26IO8RD061WRehnHd1ZZdfEmQQJRD2ymCeo-cFKJEbXTGBUl5j_tFhUX8NKVA, https://banksampoerna.com/setting/bahasa/b21d6d85cbab8b992a6c477b5551ba86ded3f7bbc2670143e03f82463f01d09a285c80224b4538f871846aa82ceffa43cb41e4e3701980d2b790c131f01add33V9QiRX6ytdvJ8E3K7oam9gBYBfUw78HDwCDP-DFnedo~/55887543cdd937b4081c59caa0193c2e5ab27a2ea8c47456c4c505926ca9121fd77c8831beefddd8ded2a40225e7870a6e13600356d4ccea6295134041f4decfQV7qhu6svED0L3Mn_Rn64LMXyMubHV1G_-90tEPfyaN6stZq096L9h2WWpmSJKip, https://banksampoerna.com/product and https://banksampoerna.com/office all use the title “Bank Sahabat Sampoerna”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages share a meta description

    https://banksampoerna.com/setting/bahasa/42873d4d9d9bd42e572e662c0bb2c57b08802aa31a98e98d9e8de7cc90da9701a23802e12ea499a52a025f93b7f50b2e7e065ec60ac35d240ad5a4dffcd1878coAWkA0bd-MjmHO_KL2StjliuG_iWclW3PgiHNnzHgNo~/7ddfe9725dbd610195a1f33407899e8c1e51393abd990c7216b0c4e62d983ebd0a1c9929a7d9d525021e5601ef526a20e6b34ca62234004e5db389de5b45c8f3tQy26IO8RD061WRehnHd1ZZdfEmQQJRD2ymCeo-cFKJEbXTGBUl5j_tFhUX8NKVA, https://banksampoerna.com/setting/bahasa/b21d6d85cbab8b992a6c477b5551ba86ded3f7bbc2670143e03f82463f01d09a285c80224b4538f871846aa82ceffa43cb41e4e3701980d2b790c131f01add33V9QiRX6ytdvJ8E3K7oam9gBYBfUw78HDwCDP-DFnedo~/55887543cdd937b4081c59caa0193c2e5ab27a2ea8c47456c4c505926ca9121fd77c8831beefddd8ded2a40225e7870a6e13600356d4ccea6295134041f4decfQV7qhu6svED0L3Mn_Rn64LMXyMubHV1G_-90tEPfyaN6stZq096L9h2WWpmSJKip, https://banksampoerna.com/product, https://banksampoerna.com/office and https://banksampoerna.com/about use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://banksampoerna.com/setting/bahasa/42873d4d9d9bd42e572e662c0bb2c57b08802aa31a98e98d9e8de7cc90da9701a23802e12ea499a52a025f93b7f50b2e7e065ec60ac35d240ad5a4dffcd1878coAWkA0bd-MjmHO_KL2StjliuG_iWclW3PgiHNnzHgNo~/7ddfe9725dbd610195a1f33407899e8c1e51393abd990c7216b0c4e62d983ebd0a1c9929a7d9d525021e5601ef526a20e6b34ca62234004e5db389de5b45c8f3tQy26IO8RD061WRehnHd1ZZdfEmQQJRD2ymCeo-cFKJEbXTGBUl5j_tFhUX8NKVA and https://banksampoerna.com/setting/bahasa/b21d6d85cbab8b992a6c477b5551ba86ded3f7bbc2670143e03f82463f01d09a285c80224b4538f871846aa82ceffa43cb41e4e3701980d2b790c131f01add33V9QiRX6ytdvJ8E3K7oam9gBYBfUw78HDwCDP-DFnedo~/55887543cdd937b4081c59caa0193c2e5ab27a2ea8c47456c4c505926ca9121fd77c8831beefddd8ded2a40225e7870a6e13600356d4ccea6295134041f4decfQV7qhu6svED0L3Mn_Rn64LMXyMubHV1G_-90tEPfyaN6stZq096L9h2WWpmSJKip have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://banksampoerna.com/about 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.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 6 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

3 to fixGoogle 8879
  • 16 small tap targets

    16 of 21 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

  • 1 low-resolution image

    1 image is 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

4 to fix50
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 133 words

    The homepage has only about 133 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

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

  • 3 other companies contacted

    Loading the homepage contacts 3 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 banksampoerna.com, 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 Analytics
Hosting
Google Cloud

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on banksampoerna.com, including 14 speed issues, 6 SEO issues and 4 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