mans.edu.eg website review

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

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

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

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

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

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

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

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

13 images could be 293 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

5 third-party services load with your homepage (Google Tag Manager, Google Fonts and Cloudinary and others), adding 384 KiB and 292 ms of main-thread time.

8 KiB could be saved by minifying CSS.

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

84 KiB could be saved by minifying JavaScript.

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

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 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “جامعة المنصورة”. Most of its time is resource load delay (7.0 s).

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

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

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

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

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

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

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

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

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

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

13 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 245 ms to 266 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.8 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.0 MB in 129 requests on a phone: images 1.6 MB (68), scripts 798 KiB (29) and fonts 360 KiB (6). Under 2 MB keeps phones on slow connections fast.

10 images (1.3 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.

9 images further down the page (1.1 MB) 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 0.84 g of CO₂e: 100.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

1 element hidden from screen readers can still receive keyboard focus.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

There are 4 <h1> headlines (“جامعة المنصورة”, “جامعة المنصورة VR 360°” and “القرية الأولمبية”). One clear main headline is easier for people and search engines.

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

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

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

The homepage links to 127 pages on mans.edu.eg and 174 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.mans.edu.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.

https://www.mans.edu.eg/fr has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mans.edu.eg/employment-portal, https://www.mans.edu.eg/index.php/about/connect, https://www.mans.edu.eg/about/2025-09-01-09-48-42, https://www.mans.edu.eg/about/info/president-message, https://www.mans.edu.eg/about/info/facts-figures and https://www.mans.edu.eg/about/info/university-vision and 5 others use the same meta description. A description written for each page earns more clicks.

https://www.mans.edu.eg/employment-portal and https://www.mans.edu.eg/index.php/about/connect have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mans.edu.eg/employment-portal, https://www.mans.edu.eg/index.php/about/connect, https://www.mans.edu.eg/about/2025-09-01-09-48-42, https://www.mans.edu.eg/about/info/president-message, https://www.mans.edu.eg/about/info/history and https://www.mans.edu.eg/about/info/facts-figures and 7 others have 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.mans.edu.eg/about/2025-09-01-09-48-42 and https://www.mans.edu.eg/about/info/president-message took over 3 s to send their HTML from our server.

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

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a map 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 36 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.

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

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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 3 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.