Tools & Wizards About Us
wau.org screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

wau.org

Homepage | The Word Among Us

Page Load Speed

1.5 sec in total

First Response

34 ms

Resources Loaded

1.3 sec

Page Rendered

148 ms

wau.org screenshot

About Website

Click here to check amazing Wau content for United States. Otherwise, check out these important facts you probably never knew about wau.org

A Catholic Devotional Magazine based on the Daily Mass Readings

Visit wau.org

Key Findings

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

Performance Metrics

wau.org performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value1,830 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

wau.org

34 ms

wau.org

65 ms

styles-d15142134b.min.css

41 ms

js

209 ms

sdk.js

162 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 23% of them (14 requests) were addressed to the original Wau.org, 20% (12 requests) were made to S3.amazonaws.com and 15% (9 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (641 ms) relates to the external source Polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 69.4 kB (9%)

Content Size

748.8 kB

After Optimization

679.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wau.org main page is 748.8 kB. 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. Javascripts take 371.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 49.7 kB

  • Original 63.2 kB
  • After minification 53.9 kB
  • After compression 13.5 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 9.3 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 49.7 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 771 B

  • Original 228.3 kB
  • After minification 227.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. Wau images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 13.2 kB

  • Original 371.0 kB
  • After minification 371.0 kB
  • After compression 357.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 5.7 kB

  • Original 86.3 kB
  • After minification 86.3 kB
  • After compression 80.6 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. Wau.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (51%)

Requests Now

55

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wau.org

wau.org

34 ms

wau.org

wau.org

65 ms

styles-d15142134b.min.css

styles-d15142134b.min.css

41 ms

js

js

209 ms

sdk.js

sdk.js

162 ms

modernizr-2.6.2-respond-1.1.0.min.js

modernizr-2.6.2-respond-1.1.0.min.js

72 ms

jquery.min.js

jquery.min.js

163 ms

jquery-ui.min.js

jquery-ui.min.js

184 ms

plugins-67c5374edb.min.js

plugins-67c5374edb.min.js

137 ms

main-d4ecb500d4.min.js

main-d4ecb500d4.min.js

137 ms

polyfill.min.js

polyfill.min.js

641 ms

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

vedd3670a3b1c4e178fdfb0cc912d969e1713874337387

259 ms

fullarmored.jpg

fullarmored.jpg

205 ms

zTvlV2ocDrM

zTvlV2ocDrM

258 ms

logo@2x.png

logo@2x.png

99 ms

bg_info-bar.jpg

bg_info-bar.jpg

101 ms

btn_search.png

btn_search.png

119 ms

img_sub-covers@2x.jpg

img_sub-covers@2x.jpg

119 ms

twitter@2x.png

twitter@2x.png

556 ms

ps119ed.jpg

ps119ed.jpg

199 ms

fruitofspirited.jpg

fruitofspirited.jpg

196 ms

43-04_962d1f.jpg

43-04_962d1f.jpg

196 ms

43-04_SF1.jpg

43-04_SF1.jpg

196 ms

43-04_SF2.jpg

43-04_SF2.jpg

196 ms

43-04_SF3.jpg

43-04_SF3.jpg

198 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

545 ms

sdk.js

sdk.js

46 ms

analytics.js

analytics.js

55 ms

www-player.css

www-player.css

10 ms

www-embed-player.js

www-embed-player.js

31 ms

base.js

base.js

57 ms

collect

collect

55 ms

collect

collect

305 ms

vTEfc-jlr9e_tfMt-BR8Zcc1_6XGLRk25TFtjqWuknE.js

vTEfc-jlr9e_tfMt-BR8Zcc1_6XGLRk25TFtjqWuknE.js

128 ms

embed.js

embed.js

63 ms

bmtfe2.jpg

bmtfe2.jpg

167 ms

bltge0.jpg

bltge0.jpg

30 ms

bgspe0.jpg

bgspe0.jpg

31 ms

bmlhe3.jpg

bmlhe3.jpg

157 ms

BRBGE0.jpg

BRBGE0.jpg

152 ms

print-fd2c7bb99a.min.css

print-fd2c7bb99a.min.css

30 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

150 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

151 ms

page.php

page.php

147 ms

Create

Create

121 ms

u2zNh1q5aWK.css

u2zNh1q5aWK.css

91 ms

SHojUHmeyWm.js

SHojUHmeyWm.js

96 ms

xjg1QNQguf-.js

xjg1QNQguf-.js

96 ms

eQ3e44cCeXh.js

eQ3e44cCeXh.js

136 ms

qnn7MVQZYOT.js

qnn7MVQZYOT.js

134 ms

7CmGfGBVS6H.js

7CmGfGBVS6H.js

135 ms

q5lR_mVVI9t.js

q5lR_mVVI9t.js

134 ms

p55HfXW__mM.js

p55HfXW__mM.js

135 ms

GenerateIT

GenerateIT

109 ms

442378246_859611742878850_6098433481809509944_n.png

442378246_859611742878850_6098433481809509944_n.png

49 ms

441673143_859615196211838_8478617683352491212_n.jpg

441673143_859615196211838_8478617683352491212_n.jpg

51 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

14 ms

iubenda_cs.js

iubenda_cs.js

63 ms

iubenda.js

iubenda.js

30 ms

iubenda_i_badge.js

iubenda_i_badge.js

43 ms

core-cd40c5caf396e9e6430490ac6bae6c41.js

core-cd40c5caf396e9e6430490ac6bae6c41.js

52 ms

Accessibility Review

wau.org accessibility score

63

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

Image elements do not have [alt] attributes

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

wau.org best practices score

83

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

Page has valid source maps

SEO Factors

wau.org SEO score

82

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wau.org 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 Wau.org 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

wau.org

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