Website review, no card needed

cbe.org.eg logo

cbe.org.eg website review

Visit site (opens in a new tab)Reviewed 27 October 202657 issues · 79 checks

This review found 57 issues worth fixing on cbe.org.eg, 22 of them high impact, across 79 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
4.3 s3.0 sMay 9Oct 243.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.1 s
May 16, 20264.0 s
May 23, 20263.9 s
May 30, 20263.9 s
Jun 6, 20263.9 s
Jun 13, 20263.8 s
Jun 20, 20263.7 s
Jun 27, 20263.4 s
Jul 4, 20263.9 s
Jul 11, 20263.9 s
Jul 18, 20263.9 s
Jul 25, 20263.9 s
Aug 1, 20263.7 s
Aug 8, 20263.4 s
Aug 15, 20263.4 s
Aug 22, 20263.4 s
Aug 29, 20263.4 s
Sep 5, 20263.4 s
Sep 12, 20263.4 s
Sep 19, 20263.3 s
Sep 26, 20263.3 s
Oct 3, 20263.3 s
Oct 10, 20263.2 s
Oct 17, 20263.3 s
Oct 24, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
167 ms73 msMay 9Oct 24154 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026121 ms
May 16, 2026121 ms
May 23, 2026117 ms
May 30, 2026117 ms
Jun 6, 2026117 ms
Jun 13, 2026122 ms
Jun 20, 2026123 ms
Jun 27, 2026137 ms
Jul 4, 202686 ms
Jul 11, 202685 ms
Jul 18, 202685 ms
Jul 25, 202684 ms
Aug 1, 202688 ms
Aug 8, 202694 ms
Aug 15, 202694 ms
Aug 22, 2026101 ms
Aug 29, 2026111 ms
Sep 5, 2026127 ms
Sep 12, 2026144 ms
Sep 19, 2026156 ms
Sep 26, 2026146 ms
Oct 3, 2026149 ms
Oct 10, 2026144 ms
Oct 17, 2026149 ms
Oct 24, 2026154 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 cbe.org.eg (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cbe.org.eg at 0.8 s0.8 s
  2. cbe.org.eg at 1.5 s1.5 s
  3. cbe.org.eg at 2.3 s2.3 s
  4. cbe.org.eg at 3.0 s3.0 s
  5. cbe.org.eg at 3.8 s3.8 s
  6. cbe.org.eg at 4.5 s4.5 s
  7. cbe.org.eg at 5.3 s5.3 s
  8. cbe.org.eg at 6.0 s6.0 s

Speed

9 to fix37
  • Improve image delivery

    7.0 s · 6.6 MB

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

  • Use efficient cache lifetimes

    3.2 s · 1.3 MB

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

  • Mobile performance score: 37

    37/100

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

  • Reduce unused CSS

    750 ms · 138 KiB

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

  • Reduce unused JavaScript

    750 ms · 127 KiB

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

  • Render-blocking requests

    700 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 700 ms.

  • Main-thread work: 3.1 s

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

  • 10 long tasks on the main thread

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

  • 1,583 HTML elements

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

  • Font display

    50 ms

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (YouTube and Cloudflare CDN), adding 163 KiB and 5 ms of main-thread time.

  • Phones get a much slower page than desktops

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

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

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 35.7 s

    35.7 s

    Your largest element takes 35.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slide 1”.

  • Time to Interactive: 37.5 s

    37.5 s

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

  • Speed Index: 13.6 s

    13.6 s

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

  • Cumulative Layout Shift: 0.442

    0.442

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Real-user LCP: 3.7 s

    3.7 s

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

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

    +25%

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • 2 images without width and height

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

4 checks passed
  • Real-user INP: 171 ms

    171 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • Largest content (LCP) got 20% faster for real visitors

    -20%

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

  • Total Blocking Time: 155 ms

    155 ms

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

Images and page weight

5 to fix28
  • Page weight: 9.8 MB in 98 requests

    9.8 MB

    Your homepage downloads 9.8 MB in 98 requests on a phone: images 8.5 MB (59), scripts 882 KiB (23) and fonts 270 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 1.4 MB together. On a phone connection a single image that size takes seconds.

  • 34 images in older formats

    34 images (8.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.

  • 29 images below the first screen load straight away

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

  • 3 images far larger than shown

    295 KiB

    3 images are downloaded at several times the size a phone draws them, for example تدريب-2024.png at 1,089 px wide, shown at 324 px. Resized copies would save about 295 KiB.

  • About 2.8 g of CO₂ per visit

    2.78 g

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

Accessibility

10 to fixGoogle 8186
  • 3 buttons without a name

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

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 21 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

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

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

  • Heading levels should only increase by one (3 elements)

    Heading levels should only increase by one: 3 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.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 41 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: 41 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

11 to fixGoogle 8550
  • No meta description

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

  • No H1 headline

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

  • Title is short (16 characters)

    Your title is only 16 characters: “Request Rejected”. 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.

  • No canonical URL

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

  • 23 links crawlers can't follow

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

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

  • No XML sitemap

    No XML sitemap at https://cbe.org.eg/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at cbe.org.eg/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

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

  • No X (Twitter) card tag

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

AI search readiness

2 to fix42
  • Most text only appears after JavaScript runs

    9%

    A phone browser shows 188 words, but the HTML your server sends has only 17. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://cbe.org.eg/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.

Best practices

3 to fixGoogle 10063
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 26 small tap targets

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

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

Content and conversion

6 to fix25
  • 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.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • Only about 188 words

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

  • No form on the homepage

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

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

Privacy and tracking

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 1 of them by other companies (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.

  • 2 other companies contacted

    Loading the homepage contacts 2 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 cbe.org.eg, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Hosting
F5

Company

Founded
1898
Headquarters
Cairo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 57 issues on cbe.org.eg, including 20 speed issues, 11 SEO issues and 6 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