2.5 sec in total
58 ms
1.9 sec
562 ms
Welcome to mdig.com.br homepage info - get ready to check MDig best content for Brazil right away, or after learning these important things about mdig.com.br
Blog de entretenimento com muita curiosidade, belas paisagens, fotografias engraçadas, notícias e histórias contadas de uma forma inteligente e diferenciada de qualquer outro blog.
Visit mdig.com.brWe analyzed Mdig.com.br page load time and found that the first response time was 58 ms and then it took 2.5 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.
mdig.com.br performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value3.8 s
56/100
25%
Value7.1 s
31/100
10%
Value2,030 ms
7/100
30%
Value0.959
3/100
15%
Value13.1 s
12/100
10%
58 ms
301 ms
17 ms
11 ms
9 ms
Our browser made a total of 164 requests to load all elements on the main page. We found that 9% of them (14 requests) were addressed to the original Mdig.com.br, 15% (25 requests) were made to Tpc.googlesyndication.com and 10% (17 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (564 ms) relates to the external source Apis.google.com.
Page size can be reduced by 270.8 kB (11%)
2.4 MB
2.1 MB
In fact, the total size of Mdig.com.br main page is 2.4 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. 80% 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.0 MB which makes up the majority of the site volume.
Potential reduce by 183.7 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 183.7 kB or 89% of the original size.
Potential reduce by 39.5 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. MDig images are well optimized though.
Potential reduce by 35.5 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 35.5 kB or 21% of the original size.
Potential reduce by 12.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. Mdig.com.br needs all CSS files to be minified and compressed as it can save up to 12.1 kB or 78% of the original size.
Number of requests can be reduced by 71 (46%)
156
85
The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MDig. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
mdig.com.br
58 ms
www.mdig.com.br
301 ms
style_new.css
17 ms
show_ads.js
11 ms
adsbygoogle.js
9 ms
brand
77 ms
counter_xhtml.js
9 ms
jquery.min.js
74 ms
mdig.js
73 ms
jquery.cookie.js
72 ms
show.jsp
99 ms
sdk.js
61 ms
ca-pub-1956998301201492.js
143 ms
zrt_lookup.html
183 ms
show_ads_impl.js
74 ms
linksmn1.jpg
159 ms
like.php
300 ms
like.php
365 ms
like.php
404 ms
like.php
394 ms
like.php
388 ms
like.php
380 ms
like.php
392 ms
like.php
478 ms
like.php
521 ms
like.php
518 ms
37067mn.jpg
134 ms
37066mn.jpg
133 ms
37065mn.jpg
133 ms
37058mn.jpg
132 ms
37057mn.jpg
131 ms
37056mn.jpg
252 ms
37054mn.jpg
181 ms
37053mn.jpg
275 ms
37052mn.jpg
261 ms
cv-bg.gif
40 ms
bg_65.jpg
102 ms
navigator.jpg
38 ms
navigator_in.jpg
132 ms
line_v.jpg
130 ms
calendar.gif
130 ms
sidebar_h2.jpg
130 ms
darwin.jpg
131 ms
brand
169 ms
ads
152 ms
362 ms
osd.js
47 ms
xd_arbiter.php
67 ms
xd_arbiter.php
135 ms
ads
152 ms
ads
168 ms
ads
351 ms
ads
194 ms
t.php
105 ms
script.js
116 ms
main.js
118 ms
beacon.js
51 ms
vpc6VNjRPXV.js
29 ms
LVx-xkvaJ0b.png
27 ms
sync
7 ms
abg.js
39 ms
richmedia.js
56 ms
jquery.min.js
37 ms
sync
25 ms
m_js_controller.js
44 ms
scriptintext.js
159 ms
scriptfullpage2.jsp
107 ms
plusone.js
152 ms
ti.js
104 ms
ga.js
65 ms
widgets.js
322 ms
atrk.js
294 ms
bt_sld_box.gif
81 ms
favicon
310 ms
s
105 ms
googlelogo_color_112x36dp.png
245 ms
nessie_icon_tiamat_white.png
93 ms
x_button_blue2.png
101 ms
__utm.gif
71 ms
css
296 ms
p
198 ms
b0rieodvar4jEradbi-bpO.js
166 ms
page.php
272 ms
cb=gapi.loaded_0
181 ms
cb=gapi.loaded_1
128 ms
fastbutton
222 ms
fastbutton
222 ms
fastbutton
284 ms
fastbutton
282 ms
fastbutton
281 ms
fastbutton
248 ms
fastbutton
276 ms
fastbutton
276 ms
fastbutton
325 ms
fastbutton
564 ms
showintext.js
118 ms
like.php
111 ms
atrk.gif
104 ms
v2
80 ms
test.png
70 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
80 ms
postmessageRelay
232 ms
rs=AGLTcCNqicBbTRy2Ny4TeyhsrBuZucE7Kg
123 ms
17681916386802255250
211 ms
powered-by-google.png
69 ms
L70CG02Crze.js
201 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
106 ms
imp2.jsp
185 ms
dpx
178 ms
15513293195681568863
178 ms
imp2.jsp
178 ms
imp2.jsp
327 ms
imp2.jsp
325 ms
imp2.jsp
325 ms
roNeOY-tz5Y.css
182 ms
UHhaxo8Cs3k.css
179 ms
_rx8naC75Dy.js
182 ms
eqcyIzISC_n.js
224 ms
ICDbTSzjQEg.js
181 ms
TTCre3391I0.js
231 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
352 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
368 ms
1786464849032922596
294 ms
tweet_button.6a78875565a912489e9aef879c881358.pt.html
298 ms
10264843176284626531
291 ms
4867271879047269489
290 ms
9046947413455691853
302 ms
462322857413794958
305 ms
2352925685995486203
325 ms
17056405016389563339
323 ms
15566076911668956570
323 ms
13696033117880184613
334 ms
5224969463333178233
321 ms
5577951384829847770
309 ms
14106550757602628113
326 ms
7257027807717870628
317 ms
9686386464807677619
322 ms
api.js
248 ms
core:rpc:shindig.random:shindig.sha1.js
327 ms
2536007149-postmessagerelay.js
297 ms
1348232267114848739
338 ms
15781340999583825530
337 ms
8062214737286815227
359 ms
14523749245338216239
363 ms
cb=gapi.loaded_0
246 ms
cb=gapi.loaded_1
247 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
219 ms
10923648_819132508146772_1619612310197730868_n.png
150 ms
1653517_819132584813431_1830794123393031506_n.png
134 ms
1098206_1167025193325236_3191022404528619816_n.jpg
134 ms
10919005_759324914143794_5952124823181409820_n.jpg
135 ms
12705480_1733476416882773_3004867981526641541_n.jpg
135 ms
10274342_219097378436855_6186622619880729503_n.jpg
136 ms
10636247_846415878704831_2242761606588753207_n.jpg
137 ms
12728893_1022823284456072_9089575580366996072_n.jpg
137 ms
1544293_704151259685216_4651788579139087140_n.jpg
136 ms
wL6VQj7Ab77.png
91 ms
s7jcwEQH7Sx.png
91 ms
xrefid.xgi
14 ms
I6-MnjEovm5.js
12 ms
vlXaquuXMrr.js
12 ms
52154.gif
7 ms
ui
37 ms
jot.html
36 ms
mdig.com.br accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Links do not have a discernible name
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
mdig.com.br 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
mdig.com.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
PT
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mdig.com.br can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Portuguese. Our system also found out that Mdig.com.br main page’s claimed encoding is iso-8859-1. 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.
mdig.com.br
Open Graph data is detected on the main page of MDig. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: