mgu.edu.in website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Facebook and others), adding 1.1 MB and 885 ms of main-thread time.

Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

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

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

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

JSDelivr CDN costs a phone 274 ms of main-thread work and 233 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.

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

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

13 KiB could be saved by minifying CSS.

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.

Your largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “MGU Campus”.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 37.3 MB in 120 requests on a phone: media 22.6 MB (6), images 13.5 MB (56) and scripts 940 KiB (14). Under 2 MB keeps phones on slow connections fast.

11 images weigh 7.1 MB together. On a phone connection a single image that size takes seconds.

28 images are downloaded at several times the size a phone draws them, for example Home page 1.jpg at 1,900 px wide, shown at 390 px. Resized copies would save about 5.5 MB.

25 images (10.0 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.

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

5 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 17 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.

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

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

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

The homepage links to 123 pages on mgu.edu.in and 29 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://mgu.edu.in/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://mgu.edu.in/programs/program-details/1 and https://mgu.edu.in/programs/program-details/5 all use the title “program details”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mgu.edu.in/programs/program-details/1 and https://mgu.edu.in/programs/program-details/5 have no meta description, so Google writes the search snippet from whatever text it finds.

https://mgu.edu.in/about/the-university, https://mgu.edu.in/about/act_and_statutes_or_moa, https://mgu.edu.in/about/institutional_development_plan, https://mgu.edu.in/about/mission-and-vision, https://mgu.edu.in/about/governance and https://mgu.edu.in/about/approval-and-recognition and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://mgu.edu.in/blog took over 3 s to send its HTML from our server.

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

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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 732 words of visible text.

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