Tools & Wizards About Us
my.ulm.edu screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% 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

  • 83

    SEO

    Google-friendlier than
    46% of websites

my.ulm.edu

myULM

Page Load Speed

1.8 sec in total

First Response

206 ms

Resources Loaded

1.5 sec

Page Rendered

150 ms

my.ulm.edu screenshot

About Website

Click here to check amazing My Ulm content for United States. Otherwise, check out these important facts you probably never knew about my.ulm.edu

Visit my.ulm.edu

Key Findings

We analyzed My.ulm.edu page load time and found that the first response time was 206 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

my.ulm.edu performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

69/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.3 s

73/100

10%

Network Requests Diagram

my.ulm.edu

206 ms

my.ulm.edu

383 ms

aggregator.css

62 ms

node.css

122 ms

poll.css

180 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 95% of them (41 requests) were addressed to the original My.ulm.edu, 5% (2 requests) were made to Webservices.ulm.edu. The less responsive or slowest element that took the longest time to load (419 ms) belongs to the original domain My.ulm.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.1 kB (66%)

Content Size

199.6 kB

After Optimization

67.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of My.ulm.edu main page is 199.6 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. 20% of websites need less resources to load. Javascripts take 100.9 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 13.7 kB

  • Original 18.3 kB
  • After minification 16.4 kB
  • After compression 4.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. 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 13.7 kB or 75% of the original size.

Image Optimization

-4%

Potential reduce by 795 B

  • Original 21.6 kB
  • After minification 20.8 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. My Ulm images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 68.2 kB

  • Original 100.9 kB
  • After minification 91.3 kB
  • After compression 32.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 68.2 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 49.4 kB

  • Original 58.8 kB
  • After minification 26.9 kB
  • After compression 9.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. My.ulm.edu needs all CSS files to be minified and compressed as it can save up to 49.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (61%)

Requests Now

41

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Ulm. 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 from 20 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

my.ulm.edu

my.ulm.edu

206 ms

my.ulm.edu

my.ulm.edu

383 ms

aggregator.css

aggregator.css

62 ms

node.css

node.css

122 ms

poll.css

poll.css

180 ms

defaults.css

defaults.css

185 ms

system.css

system.css

181 ms

system-menus.css

system-menus.css

190 ms

user.css

user.css

192 ms

content-module.css

content-module.css

193 ms

date.css

date.css

236 ms

wf_helper.css

wf_helper.css

236 ms

fieldgroup.css

fieldgroup.css

237 ms

nimbus_style.css

nimbus_style.css

246 ms

nimbus_noaa_weather.css

nimbus_noaa_weather.css

249 ms

html-elements.css

html-elements.css

252 ms

tabs.css

tabs.css

291 ms

messages.css

messages.css

291 ms

block-editing.css

block-editing.css

292 ms

wireframes.css

wireframes.css

302 ms

layout.css

layout.css

307 ms

druportal_zen.css

druportal_zen.css

373 ms

jquery.js

jquery.js

405 ms

drupal.js

drupal.js

347 ms

ui.core.min.js

ui.core.min.js

349 ms

ui.draggable.min.js

ui.draggable.min.js

419 ms

ui.droppable.min.js

ui.droppable.min.js

366 ms

ui.sortable.min.js

ui.sortable.min.js

417 ms

nimbus.js

nimbus.js

417 ms

myulm_greeting.html

myulm_greeting.html

340 ms

header_back.gif

header_back.gif

73 ms

top-grad.png

top-grad.png

63 ms

left-top-thing.png

left-top-thing.png

62 ms

druportal_zen_logo.gif

druportal_zen_logo.gif

61 ms

l_tab.gif

l_tab.gif

64 ms

r_tab.gif

r_tab.gif

63 ms

maximize_maroon.gif

maximize_maroon.gif

128 ms

animcloud.gif

animcloud.gif

128 ms

lightning.gif

lightning.gif

126 ms

cloud.gif

cloud.gif

127 ms

sunny.gif

sunny.gif

129 ms

bg_slice.jpg

bg_slice.jpg

131 ms

laptop.jpg

laptop.jpg

125 ms

Accessibility Review

my.ulm.edu accessibility score

100

Accessibility Issues

Best Practices

my.ulm.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

SEO Factors

my.ulm.edu SEO score

83

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 My.ulm.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 My.ulm.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

my.ulm.edu

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