20.8 sec in total
2.1 sec
13.5 sec
5.2 sec
Click here to check amazing Movimento content for Brazil. Otherwise, check out these important facts you probably never knew about movimento.com
Seu portal de música clássica
Visit movimento.comWe analyzed Movimento.com page load time and found that the first response time was 2.1 sec and then it took 18.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
movimento.com performance score
2076 ms
3006 ms
489 ms
88 ms
325 ms
Our browser made a total of 162 requests to load all elements on the main page. We found that 52% of them (84 requests) were addressed to the original Movimento.com, 12% (20 requests) were made to Apis.google.com and 9% (15 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Movimento.com.
Page size can be reduced by 892.8 kB (41%)
2.2 MB
1.3 MB
In fact, the total size of Movimento.com main page is 2.2 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. 75% 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 995.9 kB which makes up the majority of the site volume.
Potential reduce by 242.8 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 242.8 kB or 83% of the original size.
Potential reduce by 43.7 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. Movimento images are well optimized though.
Potential reduce by 495.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 495.8 kB or 65% of the original size.
Potential reduce by 110.4 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. Movimento.com needs all CSS files to be minified and compressed as it can save up to 110.4 kB or 82% of the original size.
Number of requests can be reduced by 79 (49%)
160
81
The browser has sent 160 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Movimento. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
movimento.com
2076 ms
www.movimento.com
3006 ms
style.css
489 ms
css
88 ms
searchforms.css
325 ms
cat-posts.css
326 ms
public.css
325 ms
magnific-popup.css
326 ms
style.css
485 ms
twitter-feed.css
696 ms
style.css
702 ms
shortcodes.css
869 ms
addthis_wordpress_public.min.css
707 ms
wp-paginate.css
862 ms
jquery.fancybox-1.3.4.css
865 ms
page_templates.css
1693 ms
jquery.js
3134 ms
jquery-migrate.min.js
1059 ms
jquery.magnific-popup.min.js
1360 ms
jquery.cookie.js
1213 ms
public.js
1211 ms
cufon-yui.js
1213 ms
League_Gothic_400.font.js
1392 ms
superfish.js
1227 ms
custom.js
1391 ms
core.min.js
1410 ms
widget.min.js
1541 ms
position.min.js
1538 ms
menu.min.js
1570 ms
autocomplete.min.js
1727 ms
mouse.min.js
1728 ms
sortable.min.js
2793 ms
admin-ajax.php
3987 ms
addthis_widget.js
360 ms
jquery.easing-1.3.pack.js
1911 ms
jquery.fancybox-1.3.4.pack.js
1911 ms
et-ptemplates-frontend.js
2091 ms
wp-embed.min.js
2091 ms
wp-emoji-release.min.js
2239 ms
font-awesome.css
284 ms
bottom-bg.png
200 ms
top-bg.png
202 ms
MOSAICO-277929_1300x465.jpg
2858 ms
readmore.png
202 ms
%C3%93peras-para-2016-227489_1300x465.jpg
4435 ms
menu-bg.png
347 ms
menu-bar.png
350 ms
movimento-logo.png
349 ms
current-bg.png
515 ms
dropdown-bg.png
518 ms
switcher_shadow.png
511 ms
switcher_left.png
684 ms
switcher_right.png
684 ms
switcher_bg.png
692 ms
switcher-item-active.png
863 ms
switcher-item.png
862 ms
content-bg.png
872 ms
imagem-sesc-partituras-post.jpg
2010 ms
duo-600.jpg
2011 ms
19e60d9t4g42ujpg-597x200.jpg
1011 ms
quarteto-UFF.jpg
2037 ms
OSMG-600.jpg
2041 ms
POP-600.jpg
2018 ms
leticia-600.jpg
2019 ms
Boheme-600.jpg
2036 ms
Sheherazade1.jpg
2038 ms
Dmitry-Masleev1.jpg
2042 ms
Santoro.jpg
2039 ms
Bernadete-Lou2.jpg
2041 ms
testimonials-bg.png
2041 ms
bottom-widget-bg.png
2090 ms
content-testimonials-bg.png
2091 ms
rss-transparent.png
2092 ms
sidebar-feeds.png
2093 ms
all.js
400 ms
imagem-sesc-partituras-post-500x167.jpg
2312 ms
ga.js
154 ms
duo-600-500x167.jpg
2161 ms
19e60d9t4g42ujpg-500x168.jpg
2157 ms
quarteto-UFF-500x167.jpg
2159 ms
__utm.gif
23 ms
OSMG-600-500x167.jpg
2228 ms
Boheme-600-500x167.jpg
2505 ms
Sheherazade1-500x167.jpg
2506 ms
Dmitry-Masleev1-500x167.jpg
2070 ms
Santoro-210x70.jpg
2068 ms
281 ms
Bernadete-Lou2-500x167.jpg
2312 ms
xd_arbiter.php
394 ms
xd_arbiter.php
1474 ms
sidebar-bullet.png
2180 ms
bottom-shadow.png
2181 ms
footer-bg.png
2174 ms
ping
180 ms
300lo.json
103 ms
pt.js
96 ms
sh.953eb77977227bfd253ee158.html
229 ms
layers.486057f6e3ab422798c9.js
279 ms
page.php
227 ms
foTD7Ql5gTP.css
569 ms
ik8d09sCUBr.css
728 ms
SRSW8M763HA.js
972 ms
OBgB8J2m8Ye.js
1854 ms
XokP-R2tSzH.js
1853 ms
widgets.js
230 ms
pinit00.png
223 ms
plusone.js
226 ms
counter.270bdfcf33bafb0fc8fc.js
222 ms
button.71000885400e222c3c0eec823f8f93f0.js
363 ms
shares.json
345 ms
shares.json
339 ms
shares.json
330 ms
shares.json
323 ms
shares.json
321 ms
shares.json
316 ms
shares.json
313 ms
shares.json
308 ms
shares.json
307 ms
shares.json
363 ms
shares.json
357 ms
shares.json
350 ms
cb=gapi.loaded_0
881 ms
cb=gapi.loaded_1
881 ms
fastbutton
1351 ms
fastbutton
1497 ms
fastbutton
1655 ms
fastbutton
1720 ms
fastbutton
1717 ms
fastbutton
1645 ms
fastbutton
1640 ms
fastbutton
1629 ms
fastbutton
1982 ms
fastbutton
1977 ms
fastbutton
1955 ms
fastbutton
1945 ms
like.php
408 ms
like.php
820 ms
like.php
840 ms
like.php
1277 ms
like.php
1273 ms
like.php
1415 ms
like.php
1145 ms
like.php
1270 ms
like.php
1267 ms
like.php
1644 ms
like.php
1646 ms
like.php
1642 ms
tweet_button.fd774b599f565016d763dd860cb31c79.pt.html
479 ms
b22D4kZ6oZJ.js
1352 ms
LVx-xkvaJ0b.png
931 ms
postmessageRelay
857 ms
rs=AGLTcCMyLcvNMRO1OqsHIKvnNXauc5OVnQ
463 ms
R9GKCzjAnbk.js
500 ms
AWWjhOengNF.js
496 ms
YnSasnyq68i.js
500 ms
kQf_jlUv-kX.js
500 ms
cb=gapi.loaded_0
320 ms
cb=gapi.loaded_1
312 ms
1077434459-postmessagerelay.js
468 ms
rpc:shindig_random.js
326 ms
jot.html
28 ms
cb=gapi.loaded_0
25 ms
movimento.com SEO score
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Movimento.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 Movimento.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.
movimento.com
Open Graph data is detected on the main page of Movimento. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: