Report Summary

  • 84

    Performance

    Renders faster than
    88% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

my.olemiss.edu

SAP NetWeaver Portal

Page Load Speed

15.4 sec in total

First Response

130 ms

Resources Loaded

10 sec

Page Rendered

5.2 sec

my.olemiss.edu screenshot

About Website

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

Visit my.olemiss.edu

Key Findings

We analyzed My.olemiss.edu page load time and found that the first response time was 130 ms and then it took 15.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

my.olemiss.edu performance score

84

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

39/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value3.4 s

90/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

portal

130 ms

prtl_std_nn7.css

100 ms

js13_epcf.js

1454 ms

ur_nn7.css

1453 ms

ur_nn6.css

1452 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 28% of them (5 requests) were addressed to the original My.olemiss.edu, 61% (11 requests) were made to Common.olemiss.edu and 11% (2 requests) were made to Umap.olemiss.edu. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source Umap.olemiss.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 808.8 kB (74%)

Content Size

1.1 MB

After Optimization

287.4 kB

In fact, the total size of My.olemiss.edu main page is 1.1 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. 30% of websites need less resources to load. CSS take 879.6 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 18.5 kB

  • Original 25.6 kB
  • After minification 24.7 kB
  • After compression 7.1 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 18.5 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 26.3 kB
  • After minification 26.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. My Olemiss images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 106.1 kB

  • Original 164.7 kB
  • After minification 156.3 kB
  • After compression 58.5 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 106.1 kB or 64% of the original size.

CSS Optimization

-78%

Potential reduce by 684.1 kB

  • Original 879.6 kB
  • After minification 845.9 kB
  • After compression 195.5 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.olemiss.edu needs all CSS files to be minified and compressed as it can save up to 684.1 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (64%)

Requests Now

14

After Optimization

5

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

Accessibility Review

my.olemiss.edu accessibility score

97

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

my.olemiss.edu SEO score

67

Search Engine Optimization Advices

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.olemiss.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.olemiss.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 My Olemiss. 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: