4.1 sec in total
46 ms
3.3 sec
739 ms
Click here to check amazing Danosse content for Brazil. Otherwise, check out these important facts you probably never knew about danosse.com
Blog de humor e entretenimento que a 15 anos baixa a produtividade de todos.
Visit danosse.comWe analyzed Danosse.com page load time and found that the first response time was 46 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
danosse.com performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value3.0 s
78/100
25%
Value8.7 s
16/100
10%
Value8,600 ms
0/100
30%
Value0.021
100/100
15%
Value23.3 s
1/100
10%
46 ms
90 ms
29 ms
68 ms
116 ms
Our browser made a total of 178 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Danosse.com, 19% (34 requests) were made to Static.xx.fbcdn.net and 8% (14 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 2.3 MB (44%)
5.2 MB
2.9 MB
In fact, the total size of Danosse.com main page is 5.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. 85% 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 2.8 MB which makes up the majority of the site volume.
Potential reduce by 186.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 40.6 kB, which is 18% 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 186.5 kB or 81% of the original size.
Potential reduce by 714.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, Danosse needs image optimization as it can save up to 714.1 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.1 MB
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 1.1 MB or 62% of the original size.
Potential reduce by 308.1 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. Danosse.com needs all CSS files to be minified and compressed as it can save up to 308.1 kB or 80% of the original size.
Number of requests can be reduced by 89 (52%)
170
81
The browser has sent 170 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Danosse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 59 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
danosse.com
46 ms
www.danosse.com
90 ms
css
29 ms
1708208307-widget_css_bundle.css
68 ms
authorization.css
116 ms
addthis_widget.js
11 ms
jquery.min.js
35 ms
midcontent_min.js
7 ms
counter_xhtml.js
29 ms
adcreate.jsp
612 ms
page-nav.js
41 ms
310590189-widgets.js
102 ms
plusone.js
107 ms
main-bg-teste02.png
72 ms
background-teste09.png
104 ms
icon18_wrench_allbkg.png
79 ms
label.png
69 ms
comment-teste01.png
70 ms
w1rz9swaVaU
174 ms
icon18_edit_allbkg.gif
84 ms
1DUPI0FoSPo
167 ms
MxARqpiCMTc
165 ms
tme_keYfS5g
168 ms
default.jpg
166 ms
160222_sindrome_lagartixa.jpg
162 ms
160222_filme_solteira.jpg
177 ms
160222_filme_zumbis.jpg
184 ms
sidebar-head-teste03.png
55 ms
140506_ditados_populares_emoticons.jpg
97 ms
160222_lambendo_bunda.jpg
149 ms
151016_dvd_mundo_bita.jpg
54 ms
140112_problema_da_balanca.jpg
98 ms
160222_lambendo_bunda.jpg
157 ms
160222_nao_pagou_pedagio.jpg
157 ms
160222_filme_pressagios_crime.jpg
161 ms
redes_sociais-teste03.png
53 ms
150425_bairros_recife_emoticons.jpg
96 ms
140429_quais_sao_as_bandas.jpg
96 ms
user-teste1.png
96 ms
blockquote.png
96 ms
search_arrow-teste06.png
94 ms
Windows%2B10%2Btodas%2Bas%2Bversoes.jpg
96 ms
Galinha+Pintadinha+4.jpg
97 ms
www-embed-player-vflZsBgOl.css
73 ms
www-embed-player.js
103 ms
base.js
169 ms
d93e757e1104.png
23 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
90 ms
ad_status.js
131 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
172 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
172 ms
hotjar-131872.js
162 ms
bH_lHLlLSw0
93 ms
65 ms
foot-bg-teste05.png
63 ms
bgRodape.gif
149 ms
topRodape.gif
148 ms
tituloRodape.gif
161 ms
text.php
198 ms
combined.css
93 ms
smoothDivScroll.css
90 ms
stack_161235.js
147 ms
jquery.min.js
90 ms
cf5f02a7dec1.png
89 ms
likebox.php
391 ms
50 ms
modules-1f5c71aea63f8df71401422ed80fbe5f.js
109 ms
analytics.js
77 ms
12783199_1116995358334771_186950021_n.jpg
332 ms
play_small.png
32 ms
10838646_1563870133903247_1576494330_n.jpg
311 ms
12751161_1041716739205147_1449731116_n.jpg
307 ms
12728663_461557567375052_1379878053_n.jpg
315 ms
12106002_1046829605373406_1593393184_n.jpg
313 ms
12716605_843071692470004_1024766562_n.jpg
317 ms
12797933_1523990147904625_1714146970_n.jpg
317 ms
12725180_916921598428640_540053048_n.jpg
315 ms
12716487_1683823318554245_1137646215_n.jpg
389 ms
10632106_1654217124845401_1163964783_n.jpg
390 ms
css
69 ms
font-awesome.min.css
70 ms
d54a46cae9caa2c552db64ce4e6ace15.css
76 ms
a8ae990ecc31f4787d610688ef5cfa85.js
119 ms
ima3.js
331 ms
format9_g.html
911 ms
loadofr.jsp
406 ms
summary
162 ms
collect
238 ms
collect
352 ms
collect
242 ms
pql
238 ms
pql
202 ms
pql
195 ms
pql
188 ms
pql
180 ms
cb=gapi.loaded_0
141 ms
300lo.json
116 ms
sh.7c7179124ea24ac6ba46caac.html
59 ms
roNeOY-tz5Y.css
545 ms
UHhaxo8Cs3k.css
547 ms
dbNRhrdsQao.css
634 ms
1ssvpqNRk1L.css
759 ms
O8DK6hTywHD.css
782 ms
QMWjEuGlqGQ.css
771 ms
H-92Cz4DIPN.css
706 ms
_rx8naC75Dy.js
769 ms
x5F9OMjKyLw.js
831 ms
ICDbTSzjQEg.js
817 ms
TTCre3391I0.js
830 ms
njO1TPvGzoR.js
847 ms
b_6HNn_J2BZ.js
848 ms
7cm7D75Y0Sf.js
902 ms
rFmE1g6Dkoz.js
1035 ms
W0OV23mIOyO.js
891 ms
hdPYw5PFPz4.js
964 ms
D6JJJzT-tB6.js
911 ms
NPuyGQIfUx-.js
969 ms
JMI5tmJvZMw.js
958 ms
36TdwhIHusi.js
968 ms
DusqSB58d-B.js
1010 ms
ZNPAadQNc33.js
1025 ms
DKRU1bYTkTw.js
1032 ms
336JejShbZp.js
1071 ms
popunder.js
625 ms
beacon.js
39 ms
nr-852.min.js
52 ms
layers.3643cb2e25fb91c29386.js
41 ms
collect
31 ms
collect
64 ms
collect
64 ms
collect
66 ms
collect
66 ms
collect
63 ms
203 ms
bridge3.123.0_en.html
269 ms
client.js
173 ms
blp.css
386 ms
a53393d12f
157 ms
282.e0306c23072913fd0749.js
123 ms
fql
168 ms
shares.json
135 ms
fql
209 ms
shares.json
124 ms
fql
203 ms
shares.json
123 ms
fql
209 ms
shares.json
121 ms
fql
198 ms
shares.json
114 ms
gen.js
274 ms
fb.js
277 ms
uolsigainit.min.js
269 ms
uolsigaretarget.min.js
271 ms
11898913_946128938764034_5675569269042896005_n.png
355 ms
1385047_615877731789158_713149014_n.jpg
415 ms
12278640_109372479431091_6417844718909486367_n.jpg
664 ms
12540570_138269476549390_7862759332233896911_n.jpg
576 ms
12799152_1698997777013446_2790693708513937294_n.jpg
556 ms
12522912_944037219024892_419966535389981156_n.jpg
553 ms
16777_405461849627939_5375264543174818715_n.jpg
556 ms
12573919_1654914484758776_5235081195947034316_n.jpg
593 ms
10367194_877379455609856_730148754801342526_n.jpg
678 ms
12717966_1038166006226993_6861982558308488780_n.jpg
619 ms
12472551_1037474306296163_6548114594384210512_n.jpg
620 ms
12419719_935054799917224_869727034_n.jpg
640 ms
12744464_1036263359750591_3047932905210586433_n.jpg
724 ms
10677946_844223278985919_1273555754_n.jpg
686 ms
wL6VQj7Ab77.png
83 ms
s7jcwEQH7Sx.png
84 ms
QDwYpIaRyfG.png
83 ms
l5aPruN9xMM.png
83 ms
a-ZN6WoEOje.png
84 ms
tIFXiEZJgab.js
80 ms
Fl1c2TVhCj-.png
69 ms
I6-MnjEovm5.js
108 ms
vlXaquuXMrr.js
135 ms
306752634-lightbox_bundle.css
12 ms
278391951-lbx__pt_br.js
40 ms
danosse.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
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
danosse.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
danosse.com SEO score
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Danosse.com 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 Danosse.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.
danosse.com
Open Graph description is not detected on the main page of Danosse. 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: