Website review, no card needed

ibnsinatrust.com logo

ibnsinatrust.com website review

Visit site (opens in a new tab)Reviewed 1 November 202643 issues · 92 checks

This review found 43 issues worth fixing on ibnsinatrust.com, 7 of them high impact, across 92 checks. The most urgent: fails Core Web Vitals for real visitors. 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
2.6 s2.0 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.0 s
May 16, 20262.2 s
May 23, 20262.3 s
May 30, 20262.4 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.4 s
Jun 27, 20262.4 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.4 s
Jul 25, 20262.3 s
Aug 1, 20262.3 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
94 ms83 msMay 9Oct 2487 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202693 ms
May 16, 202692 ms
May 23, 202691 ms
May 30, 202690 ms
Jun 6, 202687 ms
Jun 13, 202685 ms
Jun 20, 202684 ms
Jun 27, 202684 ms
Jul 4, 202685 ms
Jul 11, 202686 ms
Jul 18, 202691 ms
Jul 25, 202692 ms
Aug 1, 202692 ms
Aug 8, 202692 ms
Aug 15, 202690 ms
Aug 22, 202689 ms
Aug 29, 202688 ms
Sep 5, 202686 ms
Sep 12, 202685 ms
Sep 19, 202686 ms
Sep 26, 202686 ms
Oct 3, 202686 ms
Oct 10, 202686 ms
Oct 17, 202686 ms
Oct 24, 202687 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 ibnsinatrust.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix92
  • Improve image delivery

    1.1 MB

    15 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    800 ms

    13 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

  • Reduce unused CSS

    310 ms · 66 KiB

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

  • 1,676 HTML elements

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 77 ms. During a long task the page ignores taps.

  • Font display

    50 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Cloudflare, Cloudflare CDN and cdnfonts.com and others), adding 224 KiB and 8 ms of main-thread time.

  • Use efficient cache lifetimes

    16 KiB

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

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

  • Minify CSS

    9 KiB

    9 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

3 checks passed
  • Mobile performance score: 92

    92/100

    Your mobile performance score is 92. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.5 s

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

  • Server response: 35 ms

    35 ms

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

Core Web Vitals

8 to fix67
  • 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.

  • Speed Index: 6.1 s

    6.1 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • 33 images without width and height

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

  • Time to Interactive: 5.7 s

    5.7 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) got 14% slower for real visitors

    +14%

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

5 checks passed
  • Real-user INP: 103 ms

    103 ms

    Real visitors wait 103 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “এতদ্বারা সকলের অবগতির জন্য জানানো যাচ্ছে যে, ইবনে সিনা ট্রা…”.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • Total Blocking Time: 14 ms

    14 ms

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

Images and page weight

5 to fix28
  • Page weight: 5.8 MB in 82 requests

    5.8 MB

    Your homepage downloads 5.8 MB in 82 requests on a phone: images 5.5 MB (49), scripts 146 KiB (14) and stylesheets 113 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.

  • 20 images in older formats

    20 images (5.1 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.

  • 17 images below the first screen load straight away

    17 images further down the page (3.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    448 KiB

    1 image is downloaded at several times the size a phone draws it, for example NABH.png at 1,920 px wide, shown at 390 px. Resized copies would save about 448 KiB.

  • About 1.6 g of CO₂ per visit

    1.65 g

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

Accessibility

8 to fixGoogle 8490
  • 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.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (8 elements)

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails 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.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 15 links without text

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

  • 4 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 42 automated accessibility rules passed

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

SEO

7 to fixGoogle 7580
  • No structured data

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

  • No canonical URL

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

  • Meta description is long (275 characters)

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

  • No social preview image

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 2 links crawlers can't follow

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

  • 2 links with vague text

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 193 internal links, 19 external

    The homepage links to 193 pages on ibnsinatrust.com and 19 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “সতর্কীকরণ বিজ্ঞপ্তি:”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “Home | The Ibn Sina Trust | pioneer in Healthcare”.

  • robots.txt in place

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.ibnsinatrust.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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://ibnsinatrust.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.

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,774 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 16 pages share a title

    /, https://ibnsinatrust.com/About_Ibn_Sina.php, https://ibnsinatrust.com/Mission_Vision.php, https://ibnsinatrust.com/Board_of_Trustee.php, https://ibnsinatrust.com/Awards.php and https://ibnsinatrust.com/Welfare_Activities.php and 10 others all use the title “Home | The Ibn Sina Trust | pioneer in Healthcare”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://ibnsinatrust.com/About_Ibn_Sina.php, https://ibnsinatrust.com/Mission_Vision.php, https://ibnsinatrust.com/Board_of_Trustee.php, https://ibnsinatrust.com/Awards.php, https://ibnsinatrust.com/Welfare_Activities.php and https://ibnsinatrust.com/Quality_Policy.php and 9 others use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 54 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://ibnsinatrust.com/css.css' because its MIME type ('text/html') is not a supported s…”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix63
  • 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.

  • Local business without LocalBusiness data

    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.

  • No phone number on the homepage

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

  • Thin social proof

    Social proof on the homepage: 51 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

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

  • No opening hours

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

  • No map or directions link

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

  • 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 1,408 words of copy

    The homepage carries about 1,408 words of visible text.

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Download zakat Book”, “Contact Us” and “Learn More”.

  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

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

  • 5 other companies contacted

    Loading the homepage contacts 5 hosts 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 ibnsinatrust.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
Hosting
Cloudflare

Company

Founded
1980
Headquarters
Dhanmondi Thana

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on ibnsinatrust.com, including 12 speed issues, 7 SEO issues and 5 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