Tools & Wizards About Us
inworks.org screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

inworks.org

Home | Inworks Innovation Initiative | Research, Labs, Programs

Page Load Speed

1.8 sec in total

First Response

39 ms

Resources Loaded

1.6 sec

Page Rendered

116 ms

inworks.org screenshot

About Website

Visit inworks.org now to see the best up-to-date Inworks content and also check out these interesting facts you probably never knew about inworks.org

Inworks is home to top-of-the-line labs/workspaces, valuable degree/certification programs, and many cutting-edge research projects at CU Denver.

Visit inworks.org

Key Findings

We analyzed Inworks.org page load time and found that the first response time was 39 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

inworks.org performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value780 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.348

32/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

inworks.org

39 ms

inworks

364 ms

main.min-ff7da9d747.css

163 ms

CUDual.min-206787e925.css

503 ms

CULayout02.min-4e5f668f7b.css

141 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Inworks.org, 69% (18 requests) were made to Engineering.ucdenver.edu and 4% (1 request) were made to Kit.fontawesome.com. The less responsive or slowest element that took the longest time to load (503 ms) relates to the external source Engineering.ucdenver.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 144.3 kB (41%)

Content Size

351.8 kB

After Optimization

207.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inworks.org main page is 351.8 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. CSS take 151.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 39.2 kB

  • Original 50.0 kB
  • After minification 44.3 kB
  • After compression 10.8 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 5.7 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 39.2 kB or 78% of the original size.

Image Optimization

-41%

Potential reduce by 52.1 kB

  • Original 127.0 kB
  • After minification 74.9 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. Obviously, Inworks needs image optimization as it can save up to 52.1 kB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-19%

Potential reduce by 4.3 kB

  • Original 23.1 kB
  • After minification 23.1 kB
  • After compression 18.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 4.3 kB or 19% of the original size.

CSS Optimization

-32%

Potential reduce by 48.6 kB

  • Original 151.7 kB
  • After minification 151.7 kB
  • After compression 103.1 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. Inworks.org needs all CSS files to be minified and compressed as it can save up to 48.6 kB or 32% of the original size.

Requests Breakdown

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

Requests Now

24

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inworks.org

inworks.org

39 ms

inworks

inworks

364 ms

main.min-ff7da9d747.css

main.min-ff7da9d747.css

163 ms

CUDual.min-206787e925.css

CUDual.min-206787e925.css

503 ms

CULayout02.min-4e5f668f7b.css

CULayout02.min-4e5f668f7b.css

141 ms

905b77de1f.js

905b77de1f.js

53 ms

ScriptResource.axd

ScriptResource.axd

346 ms

ScriptResource.axd

ScriptResource.axd

194 ms

ScriptResource.axd

ScriptResource.axd

492 ms

bootstrap.bundle.js

bootstrap.bundle.js

34 ms

aos.min.js

aos.min.js

241 ms

CUBase.min-1fe8f3630c.js

CUBase.min-1fe8f3630c.js

221 ms

WebResource.axd

WebResource.axd

247 ms

cu-denver-dual.svg

cu-denver-dual.svg

104 ms

cu-denver-dual-short.svg

cu-denver-dual-short.svg

106 ms

dual-split.svg

dual-split.svg

107 ms

cu-anschutz-dual.svg

cu-anschutz-dual.svg

99 ms

cu-anschutz-dual-short.svg

cu-anschutz-dual-short.svg

101 ms

cu-denver_inworksinnovationinitiative_h_color_rgb.svg

cu-denver_inworksinnovationinitiative_h_color_rgb.svg

101 ms

screen-shot-2023-10-03-at-3-15-00-pm.png

screen-shot-2023-10-03-at-3-15-00-pm.png

314 ms

css2

css2

113 ms

gtm.js

gtm.js

152 ms

siteanalyze_66356229.js

siteanalyze_66356229.js

66 ms

font

font

39 ms

image.aspx

image.aspx

40 ms

aos.min.css

aos.min.css

56 ms

Accessibility Review

inworks.org accessibility score

94

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

[aria-*] attributes do not match their roles

Best Practices

inworks.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

inworks.org SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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 Inworks.org 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 Inworks.org 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

inworks.org

Open Graph data is detected on the main page of Inworks. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: