6.2 sec in total
421 ms
4.8 sec
942 ms
Click here to check amazing Gregoriano content for Brazil. Otherwise, check out these important facts you probably never knew about gregoriano.org.br
musicas gregorianas, partituras de canto gregoriano, videos de canto gregoriano, gregorian chant videos and scores.
Visit gregoriano.org.brWe analyzed Gregoriano.org.br page load time and found that the first response time was 421 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
gregoriano.org.br performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value4.0 s
50/100
25%
Value3.7 s
86/100
10%
Value70 ms
99/100
30%
Value0
100/100
15%
Value3.1 s
95/100
10%
421 ms
106 ms
110 ms
203 ms
345 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 7% of them (8 requests) were addressed to the original Gregoriano.org.br, 14% (16 requests) were made to Lognplay.com and 10% (12 requests) were made to Freehostedscripts.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Geoloc9.geovisite.com.
Page size can be reduced by 1.1 MB (66%)
1.7 MB
593.2 kB
In fact, the total size of Gregoriano.org.br main page is 1.7 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. 70% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 99.6 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 99.6 kB or 74% of the original size.
Potential reduce by 34.1 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, Gregoriano needs image optimization as it can save up to 34.1 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 763.3 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 763.3 kB or 67% of the original size.
Potential reduce by 249.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. Gregoriano.org.br needs all CSS files to be minified and compressed as it can save up to 249.9 kB or 73% of the original size.
Number of requests can be reduced by 80 (73%)
109
29
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gregoriano. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
gregoriano.org.br
421 ms
back.jpg
106 ms
element.js
110 ms
fhstrans.php
203 ms
bandeirainglesa.gif
345 ms
partitura.jpg
502 ms
seminario.jpg
433 ms
portinhas1.jpg
260 ms
player_completo.js
769 ms
369 ms
friendconnect.js
132 ms
i.gif
96 ms
414 ms
geocounter.js
380 ms
addthis_widget.js
227 ms
Gregorian_chant.gif
361 ms
new3.gif
270 ms
Loader_558727.js
210 ms
translateelement.css
209 ms
main.js
251 ms
v1.js
101 ms
fhstrans.js
66 ms
element_main.js
145 ms
arabic.png
38 ms
chinese.png
63 ms
deutch.png
60 ms
espanol.png
65 ms
french.png
61 ms
italian.png
59 ms
japanese.png
64 ms
korean.png
97 ms
portuguese.png
96 ms
russian.png
95 ms
ifr_player_completo.asp
91 ms
inj_tf.css
78 ms
370 ms
373 ms
geral.css
340 ms
quiz.css
352 ms
niftyCorners.css
351 ms
jquery-ui.css
80 ms
jquery.min.js
399 ms
jquery-ui.min.js
467 ms
jquery.ui.datepicker-pt-BR-2.js
333 ms
contencao_jquery.js
348 ms
abas.js
347 ms
niftycube.js
443 ms
jscolor.js
507 ms
funcoes.js
741 ms
funcoes_quiz.js
508 ms
swfobject.js
505 ms
plusone.js
421 ms
s10.g
279 ms
pointeur.gif
404 ms
geocounter_iframe_css_64.php
1055 ms
ifr
469 ms
ga.js
111 ms
b1_D09100_BFCADE.png
130 ms
tf.html
128 ms
overlay.png
130 ms
overlay2.png
220 ms
us.png
220 ms
br.png
324 ms
dc.js
225 ms
__utm.gif
136 ms
jquery.min.js
160 ms
300lo.json
147 ms
counter.edf852b124cbbd1dcd84.js
121 ms
cb=gapi.loaded_0
84 ms
quizmania485x60.gif
292 ms
Quiz2.png
191 ms
sh.953eb77977227bfd253ee158.html
124 ms
__utm.gif
137 ms
translate_24dp.png
220 ms
l
139 ms
shares.json
163 ms
googlelogo_color_42x16dp.png
257 ms
niftyCorners.css
148 ms
font-awesome.min.css
523 ms
cleardot.gif
166 ms
te_ctrl3.gif
118 ms
googlelogo_color_68x28dp.png
117 ms
loading.gif
149 ms
geobackgroundperso.jpg
113 ms
loupe30.cur
492 ms
loupe30.png
494 ms
te_bk.gif
84 ms
sdk.js
356 ms
widgets.js
31 ms
platform.js
97 ms
page.js
117 ms
1TF2XTZ
106 ms
button.65b4bc8f0d6592fdc51d322b3f197660.js
164 ms
1px.png
145 ms
cb=gapi.loaded_1
123 ms
fastbutton
240 ms
sm13.html
159 ms
icons.15.svg.css
239 ms
postmessageRelay
349 ms
ga.js
482 ms
cb=gapi.loaded_0
275 ms
cb=gapi.loaded_1
274 ms
pJeswbKZO4XwVR0035gpgvesZW2xOQ-xsNqO47m55DA.ttf
517 ms
477 ms
3193398744-postmessagerelay.js
369 ms
rpc:shindig_random.js
263 ms
tweet_button.64a917b4a230f163048902c783e1530f.en.html
159 ms
xd_arbiter.php
514 ms
xd_arbiter.php
782 ms
__utm.gif
243 ms
cb=gapi.loaded_0
64 ms
jot
298 ms
like.php
209 ms
Of-YZRAFweH.js
643 ms
FEppCFCt76d.png
718 ms
gregoriano.org.br accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
gregoriano.org.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
gregoriano.org.br SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
PT
N/A
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gregoriano.org.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Gregoriano.org.br main page’s claimed encoding is windows-1252. 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.
gregoriano.org.br
Open Graph description is not detected on the main page of Gregoriano. 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: