Tools & Wizards About Us
imissal.com screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

imissal.com

iMissal - Catholic App and Roman Missal for iPhone, iPad, Android, Windows Phone, Blackberry and Kindle Fire. Missal, Missalette, Calendar, Mass Readi...

Page Load Speed

799 ms in total

First Response

34 ms

Resources Loaded

394 ms

Page Rendered

371 ms

imissal.com screenshot

About Website

Visit imissal.com now to see the best up-to-date IMissal content and also check out these interesting facts you probably never knew about imissal.com

iMissal is a Catholic App and Missal for iPhone, iPad, Android, Blackberry, Kindle Fire and Windows Phone Devices. This app includes a full Liturgical Catholic Calendar, Missal (Missalette), Lectionar...

Visit imissal.com

Key Findings

We analyzed Imissal.com page load time and found that the first response time was 34 ms and then it took 765 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

imissal.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0.183

66/100

15%

TTI (Time to Interactive)

Value5.7 s

67/100

10%

Network Requests Diagram

imissal.com

34 ms

www.imissal.com

18 ms

style.css

26 ms

jquery-1.3.2.min.js

21 ms

dropdown.js

5 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 87% of them (48 requests) were addressed to the original Imissal.com, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (118 ms) relates to the external source Google-analytics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 596.2 kB (45%)

Content Size

1.3 MB

After Optimization

718.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imissal.com main page is 1.3 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. 60% of websites need less resources to load. Images take 974.8 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 34.7 kB

  • Original 41.6 kB
  • After minification 34.8 kB
  • After compression 6.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 6.8 kB, which is 16% 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 34.7 kB or 83% of the original size.

Image Optimization

-36%

Potential reduce by 350.3 kB

  • Original 974.8 kB
  • After minification 624.5 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, IMissal needs image optimization as it can save up to 350.3 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 186.3 kB

  • Original 268.4 kB
  • After minification 264.8 kB
  • After compression 82.0 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 186.3 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 24.8 kB

  • Original 29.8 kB
  • After minification 23.9 kB
  • After compression 4.9 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. Imissal.com needs all CSS files to be minified and compressed as it can save up to 24.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (32%)

Requests Now

50

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

imissal.com

imissal.com

34 ms

www.imissal.com

www.imissal.com

18 ms

style.css

style.css

26 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

21 ms

dropdown.js

dropdown.js

5 ms

jquery.tweet.js

jquery.tweet.js

8 ms

jquery.cycle.all.js

jquery.cycle.all.js

15 ms

cufon-yui.js

cufon-yui.js

11 ms

Hattori_Hanzo_300-Hattori_Hanzo_italic_300.font.js

Hattori_Hanzo_300-Hattori_Hanzo_italic_300.font.js

39 ms

ga.js

ga.js

118 ms

091.png

091.png

115 ms

search.json

search.json

58 ms

bg-body.gif

bg-body.gif

12 ms

bg-topcontainer.gif

bg-topcontainer.gif

13 ms

topbg.gif

topbg.gif

43 ms

logo.png

logo.png

42 ms

icon-fb.png

icon-fb.png

42 ms

icon-twitter.png

icon-twitter.png

43 ms

amazonappstore.png

amazonappstore.png

42 ms

slidefire.png

slidefire.png

42 ms

appstore.png

appstore.png

56 ms

slideapple.png

slideapple.png

63 ms

androidmarket.png

androidmarket.png

56 ms

slideandroid.png

slideandroid.png

62 ms

bg-intro.gif

bg-intro.gif

56 ms

undermenuarrow.png

undermenuarrow.png

57 ms

bg-intro-bottom.gif

bg-intro-bottom.gif

57 ms

appstore1.png

appstore1.png

58 ms

androidstore1.png

androidstore1.png

58 ms

amazonstore1.png

amazonstore1.png

59 ms

missal.png

missal.png

64 ms

dailybread.png

dailybread.png

63 ms

prayers.png

prayers.png

63 ms

saintaday.png

saintaday.png

66 ms

readerschoice.png

readerschoice.png

64 ms

but.gif

but.gif

63 ms

line2.gif

line2.gif

64 ms

imissalbible.png

imissalbible.png

75 ms

easter.png

easter.png

76 ms

massaudio.png

massaudio.png

73 ms

bg-boxrepeat.gif

bg-boxrepeat.gif

64 ms

bg-boxbottom.gif

bg-boxbottom.gif

75 ms

bg-boxtop.gif

bg-boxtop.gif

75 ms

twitterbird.png

twitterbird.png

72 ms

bg-bottomcontainer.gif

bg-bottomcontainer.gif

76 ms

bg-footercontainer.gif

bg-footercontainer.gif

75 ms

bg-footer.gif

bg-footer.gif

80 ms

cantcha-logo.png

cantcha-logo.png

80 ms

like.php

like.php

97 ms

slidenav-active.png

slidenav-active.png

75 ms

__utm.gif

__utm.gif

22 ms

slidenav.png

slidenav.png

49 ms

loading-contact.gif

loading-contact.gif

46 ms

jCCajyPZ8S-.js

jCCajyPZ8S-.js

56 ms

FEppCFCt76d.png

FEppCFCt76d.png

72 ms

Accessibility Review

imissal.com accessibility score

78

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

imissal.com best practices score

58

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

High

Browser errors were logged to the console

SEO Factors

imissal.com SEO score

77

Search Engine Optimization Advices

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 Imissal.com 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 Imissal.com 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

imissal.com

Open Graph data is detected on the main page of IMissal. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: