isme.in website review

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

About 1.4 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 7.1 s faster on a phone.

About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Google CDN and others), adding 3.8 MB and 1.8 s of main-thread time.

20 long tasks block the main thread while loading, the longest for 1.4 s. During a long task the page ignores taps.

YouTube costs a phone 703 ms of main-thread work and 1.9 MB 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.

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

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

Polyfills for old browsers add 67 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

Google CDN costs a phone 312 ms of main-thread work and 742 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.

58 KiB could be saved by minifying JavaScript.

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.

2 KiB could be saved by minifying CSS.

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 7.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 61.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BE A PART OF THE 4i DIFFERENCE 4i: Institutional Excellence…”.

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

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

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

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

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

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

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

18 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 243 ms to 244 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 3.3 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 40.2 MB in 515 requests on a phone: images 31.2 MB (334), scripts 4.9 MB (91) and other files 1.9 MB (45). Under 2 MB keeps phones on slow connections fast.

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

15 images are downloaded at several times the size a phone draws them, for example FP-PGDM-2024-26_08072026-03.jpg at 2,123 px wide, shown at 635 px. Resized copies would save about 1.6 MB.

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

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

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

ARIA input fields must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

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

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Headings should not be empty: 6 elements on the page fail this check, rated minor by axe-core.

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

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

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

No XML sitemap at https://www.isme.in/, so Google discovers your pages only by following links.

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

The homepage links to 249 pages on isme.in and 79 external pages.

https://www.isme.in/statutory-commitees-ug-2026 and https://www.isme.in/statutory-commitees-pg-2026 have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.isme.in/aboutus, https://www.isme.in/about-isme/award, https://www.isme.in/faculty-message, https://www.isme.in/statutory-commitees-ug-2024 and https://www.isme.in/statutory-commitees-pg-2024 took over 3 s to send their HTML from our server.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

4 errors were logged to the browser console while the page loaded, for example “Bootstrap's JavaScript requires jQuery version 1.9.1 or higher, but lower than version 3”.

Chrome logged issues while loading the page (“Cookie”).

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

The homepage carries about 2,729 words of visible text.

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