Tools & Wizards About Us
mobile.lmu.edu screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    79% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

mobile.lmu.edu

Loyola Marymount University

Page Load Speed

4.7 sec in total

First Response

1.5 sec

Resources Loaded

2.9 sec

Page Rendered

309 ms

mobile.lmu.edu screenshot

About Website

Visit mobile.lmu.edu now to see the best up-to-date Mobile Lmu content for United States and also check out these interesting facts you probably never knew about mobile.lmu.edu

LMU is a top-ranked Catholic university rooted in the Jesuit and Marymount traditions. We offer a rigorous academic experience to ambitious students committed to lives of meaning and purpose.

Visit mobile.lmu.edu

Key Findings

We analyzed Mobile.lmu.edu page load time and found that the first response time was 1.5 sec and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

mobile.lmu.edu performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.097

90/100

15%

TTI (Time to Interactive)

Value5.5 s

71/100

10%

Network Requests Diagram

mobile.lmu.edu

1451 ms

wp-emoji-release.min.js

42 ms

layerslider.css

77 ms

css

26 ms

style.css

115 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 47% of them (44 requests) were addressed to the original Mobile.lmu.edu, 20% (19 requests) were made to Lmumobile.wpengine.com and 16% (15 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Mobile.lmu.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (19%)

Content Size

6.1 MB

After Optimization

5.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mobile.lmu.edu main page is 6.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. 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 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 35.9 kB

  • Original 43.8 kB
  • After minification 38.9 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 4.9 kB, which is 11% 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 35.9 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 215.0 kB

  • Original 4.9 MB
  • After minification 4.7 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. Mobile Lmu images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 562.8 kB

  • Original 817.1 kB
  • After minification 757.2 kB
  • After compression 254.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 562.8 kB or 69% of the original size.

CSS Optimization

-81%

Potential reduce by 321.6 kB

  • Original 399.3 kB
  • After minification 369.7 kB
  • After compression 77.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. Mobile.lmu.edu needs all CSS files to be minified and compressed as it can save up to 321.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (62%)

Requests Now

76

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mobile.lmu.edu

mobile.lmu.edu

1451 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

42 ms

layerslider.css

layerslider.css

77 ms

css

css

26 ms

style.css

style.css

115 ms

flexslider.css

flexslider.css

84 ms

font-awesome.min.css

font-awesome.min.css

79 ms

fontello.css

fontello.css

85 ms

animation.css

animation.css

87 ms

genericons.css

genericons.css

149 ms

magnific-popup.css

magnific-popup.css

119 ms

responsive.css

responsive.css

119 ms

supersized.css

supersized.css

121 ms

skin.css

skin.css

121 ms

jquery.js

jquery.js

223 ms

jquery-migrate.min.js

jquery-migrate.min.js

155 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

197 ms

greensock.js

greensock.js

194 ms

layerslider.transitions.js

layerslider.transitions.js

159 ms

css

css

35 ms

css

css

42 ms

jquery.tubular.1.0.js

jquery.tubular.1.0.js

193 ms

ddsmoothmenu.js

ddsmoothmenu.js

198 ms

purl.js

purl.js

311 ms

jquery.fitvids.js

jquery.fitvids.js

311 ms

jquery.imagesloaded.min.js

jquery.imagesloaded.min.js

311 ms

jquery.isotope.min.js

jquery.isotope.min.js

311 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

312 ms

jquery.easing-1.3.js

jquery.easing-1.3.js

312 ms

jquery.parallax-1.1.3.js

jquery.parallax-1.1.3.js

312 ms

jquery.localscroll-1.2.7-min.js

jquery.localscroll-1.2.7-min.js

313 ms

jquery.scrollTo-1.4.3.1-min.js

jquery.scrollTo-1.4.3.1-min.js

312 ms

jquery.flexslider.js

jquery.flexslider.js

313 ms

jquery.scrollorama.js

jquery.scrollorama.js

313 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

313 ms

supersized.3.2.7.min.js

supersized.3.2.7.min.js

313 ms

supersized.shutter.min.js

supersized.shutter.min.js

345 ms

shortcodes.js

shortcodes.js

345 ms

theone.js

theone.js

345 ms

comment-reply.min.js

comment-reply.min.js

314 ms

wp-embed.min.js

wp-embed.min.js

286 ms

mobile_web_logo.png

mobile_web_logo.png

268 ms

iPhone1.png

iPhone1.png

308 ms

HTC1.png

HTC1.png

270 ms

iPad-Air1.png

iPad-Air1.png

310 ms

Screen-shot-2014-10-29-at-5.48.35-PM.png

Screen-shot-2014-10-29-at-5.48.35-PM.png

267 ms

Screen-Shot-2014-10-29-at-3.49.02-PM-copy.png

Screen-Shot-2014-10-29-at-3.49.02-PM-copy.png

268 ms

Screen-Shot-2014-10-29-at-3.46.53-PM-copy.png

Screen-Shot-2014-10-29-at-3.46.53-PM-copy.png

270 ms

tapingo.png

tapingo.png

307 ms

Screen-Shot-2014-10-29-at-3.47.02-PM-copy.png

Screen-Shot-2014-10-29-at-3.47.02-PM-copy.png

308 ms

Screen-shot-2014-10-30-at-10.13.00-AM.png

Screen-shot-2014-10-30-at-10.13.00-AM.png

305 ms

Screen-Shot-2014-10-29-at-3.44.45-PM.png

Screen-Shot-2014-10-29-at-3.44.45-PM.png

343 ms

qbot.png

qbot.png

383 ms

Screen-Shot-2014-10-29-at-3.49.37-PM-copy.png

Screen-Shot-2014-10-29-at-3.49.37-PM-copy.png

384 ms

Screen-Shot-2014-10-29-at-3.48.21-PM-copy.png

Screen-Shot-2014-10-29-at-3.48.21-PM-copy.png

343 ms

Screen-shot-2014-10-30-at-10.16.30-AM.png

Screen-shot-2014-10-30-at-10.16.30-AM.png

308 ms

Screen-shot-2014-10-30-at-10.25.01-AM.png

Screen-shot-2014-10-30-at-10.25.01-AM.png

382 ms

Screen-shot-2014-10-30-at-10.54.56-AM.png

Screen-shot-2014-10-30-at-10.54.56-AM.png

383 ms

FYEIcon.jpg

FYEIcon.jpg

383 ms

Screen-Shot-2014-10-29-at-3.45.38-PM-copy.png

Screen-Shot-2014-10-29-at-3.45.38-PM-copy.png

417 ms

downarrow.png

downarrow.png

67 ms

YouVisit.jpg

YouVisit.jpg

258 ms

Parallax-Photos-lmu-live1.jpg

Parallax-Photos-lmu-live1.jpg

1141 ms

parallax-overlay.png

parallax-overlay.png

240 ms

Parallax-Photos-lmu-live2.jpg

Parallax-Photos-lmu-live2.jpg

633 ms

BVtM30trf7q_jfqYeHfjtA.woff

BVtM30trf7q_jfqYeHfjtA.woff

36 ms

7DI7Kjvwfuz8m3ExKe6m-Q.woff

7DI7Kjvwfuz8m3ExKe6m-Q.woff

35 ms

wkfQbvfT_02e2IWO3yYueQ.woff

wkfQbvfT_02e2IWO3yYueQ.woff

34 ms

I1Pn3gihk5vyP0Yw5GqKsQ.woff

I1Pn3gihk5vyP0Yw5GqKsQ.woff

36 ms

9k-RPmcnxYEPm8CNFsH2gg.woff

9k-RPmcnxYEPm8CNFsH2gg.woff

36 ms

1bHRUMxmJHoup12DnI9XmQ.woff

1bHRUMxmJHoup12DnI9XmQ.woff

36 ms

KT3KS9Aol4WfR6Vas8kNcg.woff

KT3KS9Aol4WfR6Vas8kNcg.woff

36 ms

kU6VHbqMAZhaN_nXCmLQsQ.woff

kU6VHbqMAZhaN_nXCmLQsQ.woff

37 ms

boeCNmOCCh-EWFLSfVffDg.woff

boeCNmOCCh-EWFLSfVffDg.woff

37 ms

kAYTUNvBOXlHHqglRQ0Nlg.woff

kAYTUNvBOXlHHqglRQ0Nlg.woff

36 ms

GS1885NGn8e1-T6Cki4rBA.woff

GS1885NGn8e1-T6Cki4rBA.woff

36 ms

HbO-zuQO1IEgFTkv_Mtv2fesZW2xOQ-xsNqO47m55DA.woff

HbO-zuQO1IEgFTkv_Mtv2fesZW2xOQ-xsNqO47m55DA.woff

37 ms

fontello.woff

fontello.woff

235 ms

QLCfAFhOzPEIhGJYdEyiwg.woff

QLCfAFhOzPEIhGJYdEyiwg.woff

36 ms

analytics.js

analytics.js

27 ms

siteanalyze_66356583.js

siteanalyze_66356583.js

219 ms

iframe_api

iframe_api

219 ms

collect

collect

37 ms

www-widgetapi.js

www-widgetapi.js

18 ms

image.aspx

image.aspx

32 ms

PHPDk1sp7LY

PHPDk1sp7LY

92 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

29 ms

www-embed-player.js

www-embed-player.js

54 ms

base.js

base.js

96 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

43 ms

ad_status.js

ad_status.js

35 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

32 ms

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff

34 ms

Accessibility Review

mobile.lmu.edu accessibility score

100

Accessibility Issues

Best Practices

mobile.lmu.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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

mobile.lmu.edu SEO score

77

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

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

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 Mobile.lmu.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 Mobile.lmu.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

mobile.lmu.edu

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