Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

law.smu.edu

SMU Dedman School of Law - SMU Dedman School of Law

Page Load Speed

14.6 sec in total

First Response

178 ms

Resources Loaded

6.4 sec

Page Rendered

8.1 sec

law.smu.edu screenshot

About Website

Welcome to law.smu.edu homepage info - get ready to check Law SMU best content for United States right away, or after learning these important things about law.smu.edu

Since 1928, alumni of SMU Dedman School of Law have distinguished themselves as global leaders in law, business, and government and as prominent members of the judiciary.

Visit law.smu.edu

Key Findings

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

law.smu.edu performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value67.3 s

0/100

25%

SI (Speed Index)

Value28.4 s

0/100

10%

TBT (Total Blocking Time)

Value26,660 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value60.1 s

0/100

10%

Network Requests Diagram

law.smu.edu

178 ms

law

125 ms

law

531 ms

gtm.js

137 ms

font-awesome.min.v-kykq9xy79zvallanpsbrmw.css

78 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Law.smu.edu, 32% (35 requests) were made to Smu.edu and 10% (11 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (4.6 sec) relates to the external source Smu.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (13%)

Content Size

16.7 MB

After Optimization

14.5 MB

In fact, the total size of Law.smu.edu main page is 16.7 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 16.4 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 67.0 kB

  • Original 84.6 kB
  • After minification 71.8 kB
  • After compression 17.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 12.8 kB, which is 15% 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 67.0 kB or 79% of the original size.

Image Optimization

-13%

Potential reduce by 2.1 MB

  • Original 16.4 MB
  • After minification 14.4 MB

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, Law SMU needs image optimization as it can save up to 2.1 MB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-42%

Potential reduce by 60.4 kB

  • Original 142.8 kB
  • After minification 142.0 kB
  • After compression 82.4 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 60.4 kB or 42% of the original size.

CSS Optimization

-10%

Potential reduce by 3.9 kB

  • Original 39.8 kB
  • After minification 39.8 kB
  • After compression 36.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. Law.smu.edu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 66 (67%)

Requests Now

99

After Optimization

33

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

Accessibility Review

law.smu.edu accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

law.smu.edu best practices score

75

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

Browser errors were logged to the console

SEO Factors

law.smu.edu SEO score

89

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 Law.smu.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 Law.smu.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 Law 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: