sibs.com website review

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

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

Cookiebot costs a phone 1.0 s of main-thread work and 198 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

3 third-party services load with your homepage (Cookiebot, Google Tag Manager and Google Fonts), adding 542 KiB and 1.7 s of main-thread time.

About 782 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

About 538 KiB of CSS is downloaded but never applied on this page.

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

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

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

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

14 KiB could be saved by minifying CSS.

Desktop scores 80 but mobile only 35. A gap that wide usually means heavy scripts and images that hit phones hardest.

8 KiB could be saved by minifying JavaScript.

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.

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

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

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

Your largest element takes 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Empowering businesses around the world for more than 150M p…”.

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

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

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

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

12 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-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 59.6 MB in 123 requests on a phone: media 55.7 MB (18), scripts 1.8 MB (28) and stylesheets 1.0 MB (13). Under 2 MB keeps phones on slow connections fast.

2 images further down the page (68 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

9 tap targets are too small or too close together to hit reliably with a finger.

2 frames have no title, so screen-reader users cannot tell what they contain.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is only 26 characters: “SIBS - Partner in Payments”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 206 pages on sibs.com and 11 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

https://www.sibs.com/worldwide, https://www.sibs.com/contact-sibs, https://www.sibs.com/online-payments, https://www.sibs.com/in-and-out-store-payments, https://www.sibs.com/omnichannel-backoffice and https://www.sibs.com/data-and-analytics and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.sibs.com/payments-app-and-sdk, https://www.sibs.com/authentication-app, https://www.sibs.com/loyalty-solutions and https://www.sibs.com/digital-business-cards took over 3 s to send their HTML from our server.

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

6 images failed to load on a phone, for example https://www.sibs.com/wp-content/uploads/2025/05/sibs_ico_-06.svg.

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

1 error was logged to the browser console while the page loaded, for example “Applying inline style violates the following Content Security Policy directive 'style-src-elem 'self' https://selo.conf…”.

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

Social proof on the homepage: 13 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage carries about 638 words of visible text.

Opening the homepage sets 1 cookie (measured from a US location before any click).

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