Tools & Wizards About Us
afeexplicada.wordpress.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

afeexplicada.wordpress.com

A Fé Explicada | Blog de Formação Doutrinária Católica

Page Load Speed

3.8 sec in total

First Response

8 ms

Resources Loaded

1.8 sec

Page Rendered

2 sec

afeexplicada.wordpress.com screenshot

About Website

Click here to check amazing Afe Explicada Wordpress content for United States. Otherwise, check out these important facts you probably never knew about afeexplicada.wordpress.com

Blog de Formação Doutrinária Católica

Visit afeexplicada.wordpress.com

Key Findings

We analyzed Afeexplicada.wordpress.com page load time and found that the first response time was 8 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

afeexplicada.wordpress.com performance score

0

Network Requests Diagram

afeexplicada.wordpress.com

8 ms

afeexplicada.wordpress.com

541 ms

95 ms

101 ms

100 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Afeexplicada.wordpress.com, 22% (16 requests) were made to S0.wp.com and 19% (14 requests) were made to Afeexplicada.files.wordpress.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source I0.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 725.4 kB (11%)

Content Size

6.8 MB

After Optimization

6.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Afeexplicada.wordpress.com main page is 6.8 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. 55% of websites need less resources to load. Images take 5.8 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 100.2 kB

  • Original 135.2 kB
  • After minification 132.6 kB
  • After compression 35.0 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 100.2 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 132.7 kB

  • Original 5.8 MB
  • After minification 5.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. Afe Explicada Wordpress images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 338.4 kB

  • Original 460.5 kB
  • After minification 366.8 kB
  • After compression 122.1 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 338.4 kB or 73% of the original size.

CSS Optimization

-41%

Potential reduce by 154.1 kB

  • Original 371.6 kB
  • After minification 369.5 kB
  • After compression 217.5 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. Afeexplicada.wordpress.com needs all CSS files to be minified and compressed as it can save up to 154.1 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (46%)

Requests Now

72

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

afeexplicada.wordpress.com

afeexplicada.wordpress.com

8 ms

afeexplicada.wordpress.com

afeexplicada.wordpress.com

541 ms

95 ms

101 ms

100 ms

style.css

style.css

100 ms

global-print.css

global-print.css

153 ms

gprofiles.js

gprofiles.js

304 ms

wpgroho.js

wpgroho.js

133 ms

134 ms

141 ms

tiled-gallery.css

tiled-gallery.css

131 ms

146 ms

widgets.js

widgets.js

169 ms

134 ms

725X1342.skimlinks.js

725X1342.skimlinks.js

196 ms

w.js

w.js

167 ms

ec4e4-dsc01684.jpg

ec4e4-dsc01684.jpg

391 ms

o-altar.jpg

o-altar.jpg

378 ms

S%C3%A9_de_Elvas_-_capela-mor.jpg

S%C3%A9_de_Elvas_-_capela-mor.jpg

501 ms

apocrifos.jpg

apocrifos.jpg

1053 ms

images

images

407 ms

pppontifex10102013.jpg

pppontifex10102013.jpg

410 ms

CD-01a.jpg

CD-01a.jpg

384 ms

415 ms

sdk.js

sdk.js

684 ms

geomap.php

geomap.php

480 ms

078a6bb56f1b22a4ccffaa6876299849.png

078a6bb56f1b22a4ccffaa6876299849.png

370 ms

geocounter.php

geocounter.php

477 ms

site_papa_francisco_620.jpg

site_papa_francisco_620.jpg

672 ms

portifolio-arquidiocese-olinda-recife.jpg

portifolio-arquidiocese-olinda-recife.jpg

693 ms

main-bg.jpg

main-bg.jpg

46 ms

ico-rss.png

ico-rss.png

45 ms

main-top.jpg

main-top.jpg

44 ms

main-bot.jpg

main-bot.jpg

88 ms

post-bg.gif

post-bg.gif

87 ms

date.png

date.png

88 ms

meta-top.gif

meta-top.gif

87 ms

meta-bg.gif

meta-bg.gif

87 ms

meta-comments-num.gif

meta-comments-num.gif

88 ms

meta-bot.gif

meta-bot.gif

174 ms

widgettitle.jpg

widgettitle.jpg

174 ms

searchform-field.gif

searchform-field.gif

175 ms

sidebar-list-arr.gif

sidebar-list-arr.gif

173 ms

Escudo-Fiel_Catolico-fd_pt-fosco-web-mn.jpg

Escudo-Fiel_Catolico-fd_pt-fosco-web-mn.jpg

397 ms

2ac08-ambc3a3onovosc3a3opedro3.jpg

2ac08-ambc3a3onovosc3a3opedro3.jpg

350 ms

5ae40-3.jpg

5ae40-3.jpg

359 ms

9a581-mantra-japones.jpg

9a581-mantra-japones.jpg

486 ms

estados_unidos.jpg

estados_unidos.jpg

360 ms

espanha3.jpg

espanha3.jpg

384 ms

bandeira_italiana.jpg

bandeira_italiana.jpg

370 ms

franca1.jpg

franca1.jpg

380 ms

alemanha.jpg

alemanha.jpg

384 ms

bandeira_japao.jpg

bandeira_japao.jpg

383 ms

china.jpg

china.jpg

389 ms

bandeira_russia1.jpg

bandeira_russia1.jpg

393 ms

bandeira-polonia-gr.jpg

bandeira-polonia-gr.jpg

393 ms

bandeira_grecia1.jpg

bandeira_grecia1.jpg

393 ms

156 ms

hovercard.css

hovercard.css

137 ms

services.css

services.css

162 ms

62 ms

g.gif

g.gif

57 ms

g.gif

g.gif

57 ms

g.gif

g.gif

56 ms

interstate-0ab59479718c8235122cad6b16a66953d725c43a.css

interstate-0ab59479718c8235122cad6b16a66953d725c43a.css

239 ms

widget-0511d506.css

widget-0511d506.css

101 ms

widget-d9304090.js

widget-d9304090.js

205 ms

logo-200x120-177df3dd.png

logo-200x120-177df3dd.png

36 ms

139 ms

logo_grey-377f1b9e.png

logo_grey-377f1b9e.png

28 ms

xd_arbiter.php

xd_arbiter.php

444 ms

link

link

44 ms

track.php

track.php

45 ms

SEO Factors

afeexplicada.wordpress.com SEO score

0

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Afeexplicada.wordpress.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Afeexplicada.wordpress.com 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

afeexplicada.wordpress.com

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