Tools & Wizards About Us
catalog.uncc.edu screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

catalog.uncc.edu

University of North Carolina at Charlotte - Acalog ACMS™

Page Load Speed

18.6 sec in total

First Response

44 ms

Resources Loaded

18.4 sec

Page Rendered

136 ms

catalog.uncc.edu screenshot

About Website

Visit catalog.uncc.edu now to see the best up-to-date Catalog Uncc content for United States and also check out these interesting facts you probably never knew about catalog.uncc.edu

The Catalogs provide an overview of the University’s curriculum, academic programs and courses, facilities, and educational resources.

Visit catalog.uncc.edu

Key Findings

We analyzed Catalog.uncc.edu page load time and found that the first response time was 44 ms and then it took 18.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

catalog.uncc.edu performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

catalog.uncc.edu

44 ms

catalog.charlotte.edu

17796 ms

user-styles.css

107 ms

global_styles.css

55 ms

jquery.js

65 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Catalog.uncc.edu, 42% (22 requests) were made to Acalog-clients.s3.amazonaws.com and 15% (8 requests) were made to Catalog.charlotte.edu. The less responsive or slowest element that took the longest time to load (17.8 sec) relates to the external source Catalog.charlotte.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 757.8 kB (50%)

Content Size

1.5 MB

After Optimization

763.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Catalog.uncc.edu main page is 1.5 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. 60% of websites need less resources to load. Images take 614.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 32.8 kB

  • Original 40.3 kB
  • After minification 30.4 kB
  • After compression 7.6 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 9.9 kB, which is 25% 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 32.8 kB or 81% of the original size.

Image Optimization

-14%

Potential reduce by 86.2 kB

  • Original 614.4 kB
  • After minification 528.2 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, Catalog Uncc needs image optimization as it can save up to 86.2 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-54%

Potential reduce by 194.0 kB

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

CSS Optimization

-88%

Potential reduce by 444.7 kB

  • Original 504.5 kB
  • After minification 435.2 kB
  • After compression 59.7 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. Catalog.uncc.edu needs all CSS files to be minified and compressed as it can save up to 444.7 kB or 88% of the original size.

Requests Breakdown

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

Requests Now

39

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

catalog.uncc.edu

catalog.uncc.edu

44 ms

catalog.charlotte.edu

catalog.charlotte.edu

17796 ms

user-styles.css

user-styles.css

107 ms

global_styles.css

global_styles.css

55 ms

jquery.js

jquery.js

65 ms

Tooltip.js

Tooltip.js

282 ms

javascripts.js

javascripts.js

64 ms

smlinks.js

smlinks.js

73 ms

js

js

132 ms

gateway-styles-reset.css

gateway-styles-reset.css

99 ms

gateway-styles-nojs.css

gateway-styles-nojs.css

109 ms

gateway-styles.css

gateway-styles.css

103 ms

jquery.min.js

jquery.min.js

87 ms

jquery.browser.js

jquery.browser.js

139 ms

gateway-javascript.js

gateway-javascript.js

106 ms

jquery.min.js

jquery.min.js

93 ms

select2.min.css

select2.min.css

97 ms

e35e04f508.js

e35e04f508.js

131 ms

mobile-js.js

mobile-js.js

76 ms

mobile-styles.css

mobile-styles.css

319 ms

js_WkOMkSyjg9rxsesVK2mUAVX_dhZTWbIE6jpIzuL-ygM.js

js_WkOMkSyjg9rxsesVK2mUAVX_dhZTWbIE6jpIzuL-ygM.js

115 ms

bootstrap.min.js

bootstrap.min.js

223 ms

js_k8lmLLe2oB1q8iz_q0gcxDnWSXdvAImbtynD2Q5JO5U.js

js_k8lmLLe2oB1q8iz_q0gcxDnWSXdvAImbtynD2Q5JO5U.js

129 ms

script-block-01.js

script-block-01.js

130 ms

js_Nsd0RO8Glj95042fD7wuZhdHVpdcFMgQuC6dHdWwwe0.js

js_Nsd0RO8Glj95042fD7wuZhdHVpdcFMgQuC6dHdWwwe0.js

139 ms

script-block-02.js

script-block-02.js

140 ms

script-block-03.js

script-block-03.js

135 ms

js_5idECjjAo-X5YdkT65CaIiodkWmZlZv-WjSkHlWhoYk.js

js_5idECjjAo-X5YdkT65CaIiodkWmZlZv-WjSkHlWhoYk.js

171 ms

js_L50O_PWoAuMOxVjnzZCkNSSmI0kFwhZsO1_KS8WnGKw.js

js_L50O_PWoAuMOxVjnzZCkNSSmI0kFwhZsO1_KS8WnGKw.js

153 ms

alerts.js

alerts.js

158 ms

select2.full.min.js

select2.full.min.js

97 ms

all.min.css

all.min.css

57 ms

jquery-migrate-git.min.js

jquery-migrate-git.min.js

21 ms

css

css

58 ms

analytics.js

analytics.js

122 ms

Charlotte%20C%20logo%20-%20white%20vertical%20large.png

Charlotte%20C%20logo%20-%20white%20vertical%20large.png

118 ms

Charlotte%20C%20logo%20-%20white%20horizontal.png

Charlotte%20C%20logo%20-%20white%20horizontal.png

66 ms

background_clt.jpg

background_clt.jpg

41 ms

select-arrow.png

select-arrow.png

20 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUZiYA.ttf

41 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

41 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

64 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUZiYA.ttf

77 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUZiYA.ttf

79 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUZiYA.ttf

80 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

59 ms

fa-solid-900.woff

fa-solid-900.woff

37 ms

fa-regular-400.woff

fa-regular-400.woff

38 ms

acalog-icons.ttf

acalog-icons.ttf

38 ms

fa-brands-400.woff

fa-brands-400.woff

37 ms

collect

collect

44 ms

collect

collect

53 ms

Accessibility Review

catalog.uncc.edu accessibility score

100

Accessibility Issues

Best Practices

catalog.uncc.edu best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

catalog.uncc.edu SEO score

88

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

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 Catalog.uncc.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 Catalog.uncc.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

catalog.uncc.edu

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