Tools & Wizards About Us
intu.ntu.edu.sg screenshot

Report Summary

  • 90

    Performance

    Renders faster than
    91% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

intu.ntu.edu.sg

Service Busy

Page Load Speed

8.4 sec in total

First Response

910 ms

Resources Loaded

7.4 sec

Page Rendered

115 ms

intu.ntu.edu.sg screenshot

About Website

Click here to check amazing Intu Ntu content for Singapore. Otherwise, check out these important facts you probably never knew about intu.ntu.edu.sg

Visit intu.ntu.edu.sg

Key Findings

We analyzed Intu.ntu.edu.sg page load time and found that the first response time was 910 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

intu.ntu.edu.sg performance score

90

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.1 s

99/100

10%

Network Requests Diagram

intu.ntu.edu.sg

910 ms

Authenticate.aspx

232 ms

default.aspx

238 ms

default.aspx

248 ms

layouts.css

262 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 71% of them (27 requests) were addressed to the original Intu.ntu.edu.sg, 26% (10 requests) were made to Webcam.ntu.edu.sg and 3% (1 request) were made to Sp.ntu.edu.sg. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Webcam.ntu.edu.sg.

Page Optimization Overview & Recommendations

Page size can be reduced by 397.0 kB (42%)

Content Size

948.2 kB

After Optimization

551.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Intu.ntu.edu.sg main page is 948.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 477.0 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 11.7 kB

  • Original 15.8 kB
  • After minification 12.2 kB
  • After compression 4.0 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 3.5 kB, which is 22% 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 11.7 kB or 74% of the original size.

Image Optimization

-6%

Potential reduce by 27.0 kB

  • Original 477.0 kB
  • After minification 450.1 kB

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. Intu Ntu images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 165.6 kB

  • Original 234.3 kB
  • After minification 227.2 kB
  • After compression 68.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 165.6 kB or 71% of the original size.

CSS Optimization

-87%

Potential reduce by 192.6 kB

  • Original 221.1 kB
  • After minification 156.6 kB
  • After compression 28.4 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. Intu.ntu.edu.sg needs all CSS files to be minified and compressed as it can save up to 192.6 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (18%)

Requests Now

34

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

intu.ntu.edu.sg

intu.ntu.edu.sg

910 ms

Authenticate.aspx

Authenticate.aspx

232 ms

default.aspx

default.aspx

238 ms

default.aspx

default.aspx

248 ms

layouts.css

layouts.css

262 ms

corev4.css

corev4.css

1368 ms

WebResource.axd

WebResource.axd

889 ms

blank.js

blank.js

667 ms

WebResource.axd

WebResource.axd

670 ms

atq_custom_login.css

atq_custom_login.css

678 ms

init.js

init.js

489 ms

ScriptResource.axd

ScriptResource.axd

234 ms

ScriptResource.axd

ScriptResource.axd

454 ms

errorIcon.png

errorIcon.png

239 ms

iNTULogin_Header.html

iNTULogin_Header.html

233 ms

iNTULogin_LeftNav.html

iNTULogin_LeftNav.html

238 ms

home.html

home.html

1346 ms

NTUWebCamControl.aspx

NTUWebCamControl.aspx

1378 ms

iNTULogin_Content.html

iNTULogin_Content.html

247 ms

iNTULogin_Footer.html

iNTULogin_Footer.html

239 ms

login-orange-windows.png

login-orange-windows.png

241 ms

btn-webcam.jpg

btn-webcam.jpg

467 ms

logo-ntu.png

logo-ntu.png

244 ms

logo.png

logo.png

246 ms

btn-tour.jpg

btn-tour.jpg

243 ms

btn-trouble.jpg

btn-trouble.jpg

241 ms

btn-faq.jpg

btn-faq.jpg

242 ms

bg-logincontent.png

bg-logincontent.png

465 ms

img-login.jpg

img-login.jpg

687 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

890 ms

adm.jpg

adm.jpg

232 ms

fastfood.jpg

fastfood.jpg

461 ms

foodcourt.jpg

foodcourt.jpg

690 ms

lwn-inside.jpg

lwn-inside.jpg

1559 ms

quad.jpg

quad.jpg

1564 ms

WalkwaybetweenNorthAndSouthSpines.jpg

WalkwaybetweenNorthAndSouthSpines.jpg

1563 ms

canteenB.jpg

canteenB.jpg

1343 ms

onestop_sac.jpg

onestop_sac.jpg

1561 ms

Accessibility Review

intu.ntu.edu.sg accessibility score

59

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

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.

Impact

Issue

High

Image elements do not have [alt] attributes

Best Practices

intu.ntu.edu.sg best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

intu.ntu.edu.sg SEO score

58

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Intu.ntu.edu.sg 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 Intu.ntu.edu.sg 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

intu.ntu.edu.sg

Open Graph description is not detected on the main page of Intu Ntu. 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: