Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

rcs.columbia.edu

Research Computing Services — RCS | Columbia University Information Technology

Page Load Speed

3.7 sec in total

First Response

50 ms

Resources Loaded

2.7 sec

Page Rendered

1 sec

rcs.columbia.edu screenshot

About Website

Visit rcs.columbia.edu now to see the best up-to-date RCS Columbia content for United States and also check out these interesting facts you probably never knew about rcs.columbia.edu

workshops training google cloud platform high performance computing hpc linux classes cloud computing research

Visit rcs.columbia.edu

Key Findings

We analyzed Rcs.columbia.edu page load time and found that the first response time was 50 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

rcs.columbia.edu performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.169

70/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

rcs.columbia.edu

50 ms

research-computing

125 ms

research-computing

317 ms

about-research-computing-services

109 ms

analytics.js

123 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Rcs.columbia.edu, 39% (15 requests) were made to Cuit.columbia.edu and 29% (11 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (878 ms) relates to the external source Yoda.unifyed.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 158.8 kB (58%)

Content Size

274.3 kB

After Optimization

115.6 kB

In fact, the total size of Rcs.columbia.edu main page is 274.3 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. 65% of websites need less resources to load. HTML takes 101.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 79.2 kB

  • Original 101.7 kB
  • After minification 90.9 kB
  • After compression 22.5 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 10.9 kB, which is 11% 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 79.2 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 4.2 kB

  • Original 61.5 kB
  • After minification 57.3 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. RCS Columbia images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 169 B

  • Original 22.9 kB
  • After minification 22.9 kB
  • After compression 22.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

-85%

Potential reduce by 75.2 kB

  • Original 88.3 kB
  • After minification 13.1 kB
  • After compression 13.0 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. Rcs.columbia.edu needs all CSS files to be minified and compressed as it can save up to 75.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (57%)

Requests Now

23

After Optimization

10

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

Accessibility Review

rcs.columbia.edu accessibility score

88

Accessibility Issues

ARIA

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.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

rcs.columbia.edu 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

rcs.columbia.edu SEO score

91

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

Mobile Friendly

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/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Rcs.columbia.edu 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 Rcs.columbia.edu 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

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