isdb.org website review

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

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

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

Your mobile performance score is 67 (desktop: 89). Pages that score under 90 lose visitors before the first paint.

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

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

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

5 third-party services load with your homepage (Google Tag Manager, Google Analytics and Twitter Online Conversion Tracking and others), adding 448 KiB and 208 ms of main-thread time.

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

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

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

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 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Originality and Solidarity for Intergenerational Prosperity”.

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

Real visitors wait 3.3 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.

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

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

6 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' tap response (inp) went from 125 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 7.5 MB in 60 requests on a phone: media 4.3 MB (1), images 2.0 MB (12) and scripts 909 KiB (11). Under 2 MB keeps phones on slow connections fast.

VoI_Banner_Desktop_2400x600.png weighs 1.4 MB. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example VoI_Banner_Desktop_2400x600.png at 2,400 px wide, shown at 358 px. Resized copies would save about 1.1 MB.

2 images (1.5 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 further down the page (101 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 2.12 g of CO₂e: 253.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

4 buttons have no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

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

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

2 elements have a tabindex above 0, which scrambles the keyboard order.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is 87 characters, so Google will cut it off around 60: “Islamic Development Bank | Empowering people, building partnerships, driving innovation”.

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

There are 5 <h1> headlines (“IsDB”, “Search” and “Islamic Development Bank”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 98 pages on isdb.org and 15 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.isdb.org/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.isdb.org/ar/home and https://www.isdb.org/fr/home all use the title “Islamic Development Bank | Empowering people, building partnerships, …”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.isdb.org/ar/home, https://www.isdb.org/fr/home, https://www.isdb.org/who-we-are, https://www.isdb.org/leadership/board-of-governors, https://www.isdb.org/president and https://www.isdb.org/leadership/board-of-executive-directors and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.isdb.org/ar/home, whose canonical is https://www.isdb.org/ar. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.isdb.org/ar/home 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.

https://www.isdb.org/fr/home, https://www.isdb.org/leadership/board-of-executive-directors, https://www.isdb.org/offices and https://www.isdb.org/isdb-member-countries took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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

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

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

The homepage carries about 618 words of visible text.

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

Opening the homepage sets 7 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.