robinsonsbank.com.ph website review

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

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

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

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

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

17 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.

Polyfills for old browsers add 25 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

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

6 third-party services load with your homepage (Adobe Scene7, Evergage and site.com and others), adding 371 KiB and 446 ms of main-thread time.

36 KiB could be saved by minifying JavaScript.

About 27 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.

2 images could be 25 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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.

Your largest element takes 11.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “RBANK WEBSITE MOCK UP_”.

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

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

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

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

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

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

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

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

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

2 images (218 KiB) 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 further down the page (140 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

ARIA roles used must conform to valid values: 5 elements on the page fail this check, rated critical by axe-core.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

1 element has a tabindex above 0, which scrambles the keyboard order.

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

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

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

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 94 pages on robinsonsbank.com.ph and 27 external pages.

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.

There is no https://www.bpi.com.ph/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.

https://www.bpi.com.ph/institutional-banking, https://www.bpi.com.ph/about-bpi/overview, https://www.bpi.com.ph/group/bpiwealth, https://www.bpi.com.ph/about-bpi/subsidiaries/bpi-capital and https://www.bpi.com.ph/europe have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.bpi.com.ph/wealth-hk, whose canonical is https://www.bpi.com.ph/ifl-hk. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.bpi.com.ph/wealth/preferred/gold, https://www.bpi.com.ph/wealth/preferred, https://www.bpi.com.ph/sme-banking, https://www.bpi.com.ph/institutional-banking and https://www.bpi.com.ph/about-bpi took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://bpicc.my.site.com/ESWBEAEnhanced1773772119568/assets/styles/bootstrap.min.css' fro…”.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 4 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.