Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

outage.smu.edu

Website Unavailable – Website outage site for SMU

Page Load Speed

4.6 sec in total

First Response

2.1 sec

Resources Loaded

2.4 sec

Page Rendered

96 ms

outage.smu.edu screenshot

About Website

Visit outage.smu.edu now to see the best up-to-date Outage SMU content for United States and also check out these interesting facts you probably never knew about outage.smu.edu

Visit outage.smu.edu

Key Findings

We analyzed Outage.smu.edu page load time and found that the first response time was 2.1 sec and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

outage.smu.edu performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value4.1 s

80/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.049

99/100

15%

TTI (Time to Interactive)

Value8.9 s

34/100

10%

Network Requests Diagram

outage.smu.edu

2112 ms

dreamweaver.css

92 ms

structure.css

95 ms

presentation.css

95 ms

sharethis.css

93 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that all of those requests were addressed to Outage.smu.edu and no external sources were called. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Outage.smu.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.4 kB (67%)

Content Size

28.8 kB

After Optimization

9.4 kB

In fact, the total size of Outage.smu.edu main page is 28.8 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. CSS take 20.1 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 3.2 kB

  • Original 5.1 kB
  • After minification 4.9 kB
  • After compression 1.9 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 3.2 kB or 63% of the original size.

Image Optimization

-11%

Potential reduce by 395 B

  • Original 3.6 kB
  • After minification 3.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, Outage SMU needs image optimization as it can save up to 395 B or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-79%

Potential reduce by 15.8 kB

  • Original 20.1 kB
  • After minification 13.3 kB
  • After compression 4.3 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. Outage.smu.edu needs all CSS files to be minified and compressed as it can save up to 15.8 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (36%)

Requests Now

11

After Optimization

7

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

Accessibility Review

outage.smu.edu accessibility score

100

Accessibility Issues

Best Practices

outage.smu.edu best practices score

92

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

Page has valid source maps

SEO Factors

outage.smu.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

Page is blocked from indexing

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

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Outage.smu.edu can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Outage.smu.edu main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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