Tools & Wizards About Us
scholar.utc.edu screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

scholar.utc.edu

UTC Scholar | Preserving and Sharing the University of Tennessee at Chattanooga's Knowledge

Page Load Speed

1.8 sec in total

First Response

178 ms

Resources Loaded

1.5 sec

Page Rendered

100 ms

scholar.utc.edu screenshot

About Website

Visit scholar.utc.edu now to see the best up-to-date Scholar UTC content for United States and also check out these interesting facts you probably never knew about scholar.utc.edu

UTC Scholar is a service dedicated to preserving and providing open access to the scholarly and creative work of the University of Tennessee at Chattanooga.

Visit scholar.utc.edu

Key Findings

We analyzed Scholar.utc.edu page load time and found that the first response time was 178 ms and then it took 1.6 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

scholar.utc.edu performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.59

11/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

scholar.utc.edu

178 ms

scholar.utc.edu

348 ms

yui-min.js

58 ms

jquery.min.js

54 ms

launch-d525bb0064d8.min.js

50 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 52% of them (42 requests) were addressed to the original Scholar.utc.edu, 25% (20 requests) were made to Cdnjs.cloudflare.com and 4% (3 requests) were made to Cdn.cookielaw.org. The less responsive or slowest element that took the longest time to load (361 ms) relates to the external source Assets.bepress.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 107.8 kB (17%)

Content Size

642.3 kB

After Optimization

534.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Scholar.utc.edu main page is 642.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. 55% of websites need less resources to load. Javascripts take 308.1 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 61.5 kB

  • Original 80.6 kB
  • After minification 74.8 kB
  • After compression 19.2 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 61.5 kB or 76% of the original size.

Image Optimization

-6%

Potential reduce by 12.2 kB

  • Original 188.3 kB
  • After minification 176.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. Scholar UTC images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 9.8 kB

  • Original 308.1 kB
  • After minification 308.1 kB
  • After compression 298.3 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

-37%

Potential reduce by 24.3 kB

  • Original 65.3 kB
  • After minification 64.9 kB
  • After compression 41.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. Scholar.utc.edu needs all CSS files to be minified and compressed as it can save up to 24.3 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (79%)

Requests Now

75

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

scholar.utc.edu

scholar.utc.edu

178 ms

scholar.utc.edu

scholar.utc.edu

348 ms

yui-min.js

yui-min.js

58 ms

jquery.min.js

jquery.min.js

54 ms

launch-d525bb0064d8.min.js

launch-d525bb0064d8.min.js

50 ms

nr_browser_production.js

nr_browser_production.js

129 ms

ir-style.css

ir-style.css

193 ms

ir-custom.css

ir-custom.css

195 ms

ir-local.css

ir-local.css

255 ms

jsUtilities.js

jsUtilities.js

259 ms

footnoteLinks.js

footnoteLinks.js

266 ms

dc-responsive-nav.js

dc-responsive-nav.js

326 ms

dc-mobile-nav.js

dc-mobile-nav.js

273 ms

rdr.js

rdr.js

285 ms

floatbox.css

floatbox.css

361 ms

floatbox.js

floatbox.js

277 ms

js

js

102 ms

bpbootstrap-20160726.pack.js

bpbootstrap-20160726.pack.js

315 ms

AppMeasurement.min.js

AppMeasurement.min.js

12 ms

otSDKStub.js

otSDKStub.js

42 ms

243605e3-552c-483b-b139-00f1727d7599-test.json

243605e3-552c-483b-b139-00f1727d7599-test.json

107 ms

ir-reset.css

ir-reset.css

132 ms

ir-layout.css

ir-layout.css

202 ms

ir-assets.css

ir-assets.css

145 ms

ir-left.css

ir-left.css

152 ms

ir-submit.css

ir-submit.css

189 ms

ir-article.css

ir-article.css

196 ms

ir-feed.css

ir-feed.css

195 ms

ir-network.css

ir-network.css

207 ms

ir-adapt.css

ir-adapt.css

287 ms

dc-mobile-nav.css

dc-mobile-nav.css

251 ms

location

location

33 ms

css

css

34 ms

otBannerSdk.js

otBannerSdk.js

18 ms

ir-deprecate.css

ir-deprecate.css

127 ms

global-alert.css

global-alert.css

71 ms

grid.css

grid.css

65 ms

ir-utilities.css

ir-utilities.css

131 ms

css

css

19 ms

css

css

24 ms

ir-print.css

ir-print.css

117 ms

oop-min.js

oop-min.js

82 ms

event-custom-base-min.js

event-custom-base-min.js

123 ms

dom-core-min.js

dom-core-min.js

123 ms

dom-base-min.js

dom-base-min.js

123 ms

selector-native-min.js

selector-native-min.js

122 ms

selector-min.js

selector-min.js

122 ms

node-core-min.js

node-core-min.js

122 ms

node-base-min.js

node-base-min.js

134 ms

event-base-min.js

event-base-min.js

134 ms

event-delegate-min.js

event-delegate-min.js

134 ms

node-event-delegate-min.js

node-event-delegate-min.js

134 ms

pluginhost-base-min.js

pluginhost-base-min.js

133 ms

pluginhost-config-min.js

pluginhost-config-min.js

133 ms

node-pluginhost-min.js

node-pluginhost-min.js

153 ms

dom-style-min.js

dom-style-min.js

153 ms

dom-screen-min.js

dom-screen-min.js

152 ms

node-screen-min.js

node-screen-min.js

154 ms

node-style-min.js

node-style-min.js

152 ms

cookie-min.js

cookie-min.js

152 ms

54239167eb107bcf489e8b5a9f7f4191.png

54239167eb107bcf489e8b5a9f7f4191.png

149 ms

8e240588cf8cd3a028768d4294acd7d3.png

8e240588cf8cd3a028768d4294acd7d3.png

151 ms

gtm.js

gtm.js

103 ms

db39012c4ba98812b15d86c8d2e3307d.png

db39012c4ba98812b15d86c8d2e3307d.png

222 ms

7068d2ef7043ff27f11af787b7694d8d.png

7068d2ef7043ff27f11af787b7694d8d.png

118 ms

aeeab633ebdc9b56abeeb81715972c66.gif

aeeab633ebdc9b56abeeb81715972c66.gif

125 ms

6197118cedce33f9540b59d8fe2afdbe.gif

6197118cedce33f9540b59d8fe2afdbe.gif

119 ms

font

font

88 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

161 ms

responsivenav.ttf

responsivenav.ttf

184 ms

orn.gif

orn.gif

138 ms

font

font

125 ms

font

font

70 ms

json

json

305 ms

c6d9c04cd0e51b11fed4a896c3b40cb7.gif

c6d9c04cd0e51b11fed4a896c3b40cb7.gif

125 ms

8824738003ed620c1c8c58a37612c5c7.gif

8824738003ed620c1c8c58a37612c5c7.gif

152 ms

fbOptions.js

fbOptions.js

157 ms

core.js

core.js

66 ms

blank.gif

blank.gif

65 ms

wait.gif

wait.gif

65 ms

nr-spa-1216.min.js

nr-spa-1216.min.js

13 ms

Accessibility Review

scholar.utc.edu accessibility score

100

Accessibility Issues

Best Practices

scholar.utc.edu best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

scholar.utc.edu SEO score

97

Search Engine Optimization Advices

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 Scholar.utc.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 Scholar.utc.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

scholar.utc.edu

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