Access rntu.ac.in. Welcome to - Rabindranath Tagore University

rntu.ac.in screenshot

12

Performance

Renders faster than
25% of other websites
67

Accessibility

Visual factors better than
that of 32% of websites
58

Best Practices

More advanced features
available than in
20% of websites
85

SEO

Google-friendlier than
55% of websites

First Response

483 ms

Resources Loaded

11.2 sec

Page Rendered

1.1 sec

rntu.ac.in screenshot

About Website

Visit rntu.ac.in now to see the best up-to-date Rntu content for India and also check out these interesting facts you probably never knew about rntu.ac.in

Home Description

Visit rntu.ac.in

Key Findings

We analyzed Rntu.ac.in page load time and found that the first response time was 483 ms and then it took 12.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value18.9 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value1,900 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.306

38/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

rntu.ac.in

483 ms

rntu.ac.in

4064 ms

js

80 ms

all.css

371 ms

styles.css

560 ms

Our browser made a total of 199 requests to load all elements on the main page. We found that 89% of them (177 requests) were addressed to the original Rntu.ac.in, 5% (9 requests) were made to Fonts.gstatic.com and 2% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Rntu.ac.in.

Content Size

8.9 MB

After Optimization

8.1 MB

In fact, the total size of Rntu.ac.in main page is 8.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 8.3 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 409.6 kB

Original 449.5 kB
After minification 290.6 kB
After compression 39.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 158.9 kB, which is 35% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 409.6 kB or 91% of the original size.

Image Optimization

-5%

Potential reduce by 437.2 kB

Original 8.3 MB
After minification 7.9 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Rntu images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 5.5 kB

Original 55.2 kB
After minification 54.9 kB
After compression 49.7 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-8%

Potential reduce by 9.2 kB

Original 110.6 kB
After minification 110.6 kB
After compression 101.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Rntu.ac.in has all CSS files already compressed.

Requests Now

187

After Optimization

163

The browser has sent 187 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rntu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA IDs are not unique

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rntu.ac.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Rntu.ac.in main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

rntu.ac.in

Open Graph description is not detected on the main page of Rntu. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: