Tools & Wizards About Us
mobilon.me screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

mobilon.me

Mobilon

Page Load Speed

4.2 sec in total

First Response

378 ms

Resources Loaded

2.2 sec

Page Rendered

1.7 sec

mobilon.me screenshot

About Website

Visit mobilon.me now to see the best up-to-date Mobilon content and also check out these interesting facts you probably never knew about mobilon.me

Empreendedor, fundador do Tecnoblog e host do Tecnocast.

Visit mobilon.me

Key Findings

We analyzed Mobilon.me page load time and found that the first response time was 378 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

mobilon.me performance score

0

Network Requests Diagram

mobilon.me

378 ms

pre_tumblelog.js

36 ms

css

50 ms

revera.css

65 ms

jquery.min.js

102 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Mobilon.me, 11% (9 requests) were made to Apis.google.com and 11% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (597 ms) relates to the external source Ssl.google-analytics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 502.1 kB (46%)

Content Size

1.1 MB

After Optimization

590.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mobilon.me main page is 1.1 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. Javascripts take 567.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 87.8 kB

  • Original 114.7 kB
  • After minification 110.2 kB
  • After compression 27.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 87.8 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 11.7 kB

  • Original 337.3 kB
  • After minification 325.6 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. Mobilon images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 367.4 kB

  • Original 567.0 kB
  • After minification 566.6 kB
  • After compression 199.6 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 367.4 kB or 65% of the original size.

CSS Optimization

-48%

Potential reduce by 35.2 kB

  • Original 73.2 kB
  • After minification 70.2 kB
  • After compression 37.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. Mobilon.me needs all CSS files to be minified and compressed as it can save up to 35.2 kB or 48% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (63%)

Requests Now

72

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobilon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

mobilon.me

mobilon.me

378 ms

pre_tumblelog.js

pre_tumblelog.js

36 ms

css

css

50 ms

revera.css

revera.css

65 ms

jquery.min.js

jquery.min.js

102 ms

jquery.fitvids.min.js

jquery.fitvids.min.js

62 ms

responsive-nav.css

responsive-nav.css

247 ms

responsive-nav.min.js

responsive-nav.min.js

55 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

36 ms

stylesheet.css

stylesheet.css

32 ms

all.js

all.js

11 ms

jquery.fittext.js

jquery.fittext.js

56 ms

pxuphotoset.min.js

pxuphotoset.min.js

55 ms

index.js

index.js

59 ms

widgets.js

widgets.js

81 ms

tumblr_inline_nuqcmuY0pE1qzvtaz_500.jpg

tumblr_inline_nuqcmuY0pE1qzvtaz_500.jpg

52 ms

tumblr_inline_nn9xv8GMhU1qzvtaz_500.jpg

tumblr_inline_nn9xv8GMhU1qzvtaz_500.jpg

207 ms

tumblr_n183a7GFt41r85hlio1_1280.gif

tumblr_n183a7GFt41r85hlio1_1280.gif

52 ms

tumblr_inline_n8ryqylSE41qzvtaz.png

tumblr_inline_n8ryqylSE41qzvtaz.png

206 ms

syizYx7.png

syizYx7.png

52 ms

tumblr_inline_mzglheSXrs1qzvtaz.jpg

tumblr_inline_mzglheSXrs1qzvtaz.jpg

50 ms

143 ms

xd_arbiter.php

xd_arbiter.php

31 ms

xd_arbiter.php

xd_arbiter.php

126 ms

ga.js

ga.js

89 ms

count.js

count.js

86 ms

avatar_688821ab5499_128.png

avatar_688821ab5499_128.png

133 ms

gQ0PT3rPU_Et2ExNz-ahmqCWcynf_cDxXwCLxiixG1c.ttf

gQ0PT3rPU_Et2ExNz-ahmqCWcynf_cDxXwCLxiixG1c.ttf

52 ms

Eh9ZVPLDFF2xhCIl_We4NA.ttf

Eh9ZVPLDFF2xhCIl_We4NA.ttf

53 ms

w5P-SI7QJQSDqB3GziL8XaCWcynf_cDxXwCLxiixG1c.ttf

w5P-SI7QJQSDqB3GziL8XaCWcynf_cDxXwCLxiixG1c.ttf

52 ms

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf

52 ms

IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf

IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf

51 ms

revera.woff

revera.woff

53 ms

__utm.gif

__utm.gif

50 ms

count-data.js

count-data.js

298 ms

count-data.js

count-data.js

285 ms

museo_slab_500_2-webfont.woff

museo_slab_500_2-webfont.woff

13 ms

count-data.js

count-data.js

261 ms

count-data.js

count-data.js

254 ms

count-data.js

count-data.js

237 ms

count-data.js

count-data.js

233 ms

count-data.js

count-data.js

227 ms

count-data.js

count-data.js

209 ms

plusone.js

plusone.js

293 ms

HqOk7C7J1TZ5i3L-ejF0vonF5uFdDttMLvmWuJdhhgs.ttf

HqOk7C7J1TZ5i3L-ejF0vonF5uFdDttMLvmWuJdhhgs.ttf

162 ms

impixu

impixu

324 ms

ping

ping

168 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

314 ms

impixu

impixu

200 ms

analytics.html

analytics.html

171 ms

login_check.html

login_check.html

29 ms

avatar_688821ab5499_40.png

avatar_688821ab5499_40.png

94 ms

iframe_logo.png

iframe_logo.png

77 ms

like.php

like.php

179 ms

like.php

like.php

178 ms

follow.php

follow.php

237 ms

like.php

like.php

176 ms

like.php

like.php

193 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

52 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

74 ms

follow

follow

152 ms

rapid-3.36.js

rapid-3.36.js

198 ms

rapidworker-1.2.js

rapidworker-1.2.js

202 ms

postmessageRelay

postmessageRelay

144 ms

fNFEOa8-9dh.js

fNFEOa8-9dh.js

443 ms

rs=AGLTcCPbyLvHQDH65M9WM7jHn9WOI3B5hA

rs=AGLTcCPbyLvHQDH65M9WM7jHn9WOI3B5hA

73 ms

rs=AGLTcCP1XWuWX_iCC9WgWr0vKsRUFWxeag

rs=AGLTcCP1XWuWX_iCC9WgWr0vKsRUFWxeag

142 ms

rs=AGLTcCNPDRRI46HA3uIHFctvm-Ae2vfx-g

rs=AGLTcCNPDRRI46HA3uIHFctvm-Ae2vfx-g

141 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

405 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.pt.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.pt.html

343 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

444 ms

fNFEOa8-9dh.js

fNFEOa8-9dh.js

444 ms

ga.js

ga.js

597 ms

analytics.js

analytics.js

432 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

585 ms

rpc:shindig_random.js

rpc:shindig_random.js

323 ms

info.json

info.json

396 ms

cs.js

cs.js

381 ms

yql

yql

432 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

348 ms

dtpHsbgPEm2lVWciJZ0P-A.ttf

dtpHsbgPEm2lVWciJZ0P-A.ttf

371 ms

bdHGHleUa-ndQCOrdpfxfw.ttf

bdHGHleUa-ndQCOrdpfxfw.ttf

372 ms

__utm.gif

__utm.gif

41 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

cedexis.radar.js

cedexis.radar.js

11 ms

SEO Factors

mobilon.me SEO score

0

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobilon.me 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 Mobilon.me 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.

Social Sharing Optimization

mobilon.me

Open Graph data is detected on the main page of Mobilon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: