3.1 sec in total
743 ms
1.7 sec
611 ms
Welcome to blog.camilolopes.com.br homepage info - get ready to check Blog Camilo Lopes best content for Brazil right away, or after learning these important things about blog.camilolopes.com.br
Visit blog.camilolopes.com.brWe analyzed Blog.camilolopes.com.br page load time and found that the first response time was 743 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
blog.camilolopes.com.br performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value1.2 s
100/100
25%
Value1.5 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.2 s
100/100
10%
743 ms
53 ms
113 ms
77 ms
77 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 64% of them (61 requests) were addressed to the original Blog.camilolopes.com.br, 6% (6 requests) were made to S3.amazonaws.com and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (743 ms) belongs to the original domain Blog.camilolopes.com.br.
Page size can be reduced by 539.4 kB (34%)
1.6 MB
1.1 MB
In fact, the total size of Blog.camilolopes.com.br main page is 1.6 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. 50% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 44.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 44.0 kB or 76% of the original size.
Potential reduce by 170.3 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, Blog Camilo Lopes needs image optimization as it can save up to 170.3 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 222.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 222.0 kB or 60% of the original size.
Potential reduce by 103.2 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. Blog.camilolopes.com.br needs all CSS files to be minified and compressed as it can save up to 103.2 kB or 80% of the original size.
Number of requests can be reduced by 61 (67%)
91
30
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Camilo Lopes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
blog.camilolopes.com.br
743 ms
style.css
53 ms
jquery.min.1.2.6.js
113 ms
jqueryslidemenu.js
77 ms
google-ajax-translation.css
77 ms
crayon.min.css
86 ms
catablog.css
79 ms
styles.css
76 ms
style2-os.css
99 ms
lightbox.css
97 ms
font-awesome.css
139 ms
twitter-feed.css
137 ms
wp-syntax.css
101 ms
jquery.js
199 ms
jquery-migrate.min.js
137 ms
crayon.min.js
135 ms
jquery.min.js
74 ms
video_gallery-all.js
137 ms
site.js
33 ms
shCore.css
136 ms
shThemeDefault.css
136 ms
shCore.js
169 ms
shBrushBash.js
146 ms
shBrushCpp.js
154 ms
shBrushCSharp.js
155 ms
shBrushCss.js
146 ms
shBrushDelphi.js
172 ms
shBrushDiff.js
162 ms
shBrushGroovy.js
180 ms
shBrushJava.js
181 ms
shBrushJScript.js
178 ms
shBrushPerl.js
233 ms
shBrushPhp.js
235 ms
shBrushPlain.js
232 ms
shBrushPython.js
236 ms
shBrushRuby.js
236 ms
shBrushScala.js
239 ms
all.js
94 ms
e-201611.js
8 ms
shBrushSql.js
198 ms
shBrushVb.js
199 ms
e-201611.js
27 ms
shBrushXml.js
177 ms
jquery.translate-1.4.1.min.js
193 ms
jquery.form.min.js
218 ms
scripts.js
191 ms
bgr_html.png
211 ms
wp-emoji-release.min.js
161 ms
jquery.min.js
54 ms
8192px-Android-app-on-google-play.svg.png
145 ms
btn_donateCC_LG.gif
133 ms
small-logo.png
100 ms
bgr_main.gif
120 ms
bgr_page.png
121 ms
rss.png
101 ms
bgr_main_search.png
100 ms
button_go.gif
99 ms
bgr_board.png
231 ms
button_twitter.png
129 ms
bgr_body.gif
120 ms
bgr_post_comment.png
119 ms
transparent.gif
141 ms
capalivroangularjs-final-209x300.jpg
143 ms
GooglePlayPublishPrivateApp-1024x571.png
267 ms
ico_cat.gif
144 ms
capaTDDnaPraticaNovo1.jpg
145 ms
scjpguiasmall-214x300.jpg
190 ms
jenkinsdevops-e1441634353925.png
230 ms
bgr_footer.png
732 ms
pixel.gif
127 ms
widgets.js
132 ms
g.gif
74 ms
widgets.css
53 ms
settings
230 ms
ajax-loader.gif
87 ms
90 ms
xd_arbiter.php
80 ms
xd_arbiter.php
139 ms
ping
102 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
127 ms
like.php
75 ms
like.php
64 ms
jJhqmvSAXq3.js
137 ms
LVx-xkvaJ0b.png
148 ms
sidebar.js
14 ms
topbar.js
107 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
51 ms
152694
18 ms
152338
41 ms
main.css
33 ms
main.css
17 ms
css
56 ms
css
77 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
35 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
39 ms
jot.html
28 ms
blog.camilolopes.com.br accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
blog.camilolopes.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
blog.camilolopes.com.br SEO score
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.camilolopes.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Blog.camilolopes.com.br 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.
blog.camilolopes.com.br
Open Graph description is not detected on the main page of Blog Camilo Lopes. 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: