Tools & Wizards About Us
torpedofree.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

torpedofree.com

Torpedo Free - Torpedo SMS Grátis para qualquer operadora!

Page Load Speed

3.1 sec in total

First Response

70 ms

Resources Loaded

2.7 sec

Page Rendered

353 ms

torpedofree.com screenshot

About Website

Visit torpedofree.com now to see the best up-to-date Torpedo Free content for Brazil and also check out these interesting facts you probably never knew about torpedofree.com

Envie torpedos SMS para todas as operadoras gratuitamente, Vivo, Claro, Tim, CTBC, Nextel e Oi, de forma descomplicada e rápida.

Visit torpedofree.com

Key Findings

We analyzed Torpedofree.com page load time and found that the first response time was 70 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

torpedofree.com performance score

0

Network Requests Diagram

torpedofree.com

70 ms

style.css

30 ms

lytebox.css

52 ms

lytebox.js

55 ms

jquery.js

81 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 19% of them (17 requests) were addressed to the original Torpedofree.com, 16% (14 requests) were made to Scontent.xx.fbcdn.net and 13% (12 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (986 ms) relates to the external source Scontent.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 191.4 kB (40%)

Content Size

472.9 kB

After Optimization

281.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Torpedofree.com main page is 472.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Images take 214.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 31.5 kB

  • Original 39.2 kB
  • After minification 33.5 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 5.7 kB, which is 15% 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 31.5 kB or 80% of the original size.

Image Optimization

-8%

Potential reduce by 16.2 kB

  • Original 214.7 kB
  • After minification 198.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. Torpedo Free images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 137.0 kB

  • Original 210.3 kB
  • After minification 179.0 kB
  • After compression 73.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 137.0 kB or 65% of the original size.

CSS Optimization

-77%

Potential reduce by 6.7 kB

  • Original 8.7 kB
  • After minification 7.6 kB
  • After compression 2.0 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. Torpedofree.com needs all CSS files to be minified and compressed as it can save up to 6.7 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (53%)

Requests Now

86

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

torpedofree.com

torpedofree.com

70 ms

style.css

style.css

30 ms

lytebox.css

lytebox.css

52 ms

lytebox.js

lytebox.js

55 ms

jquery.js

jquery.js

81 ms

maskedinput.js

maskedinput.js

58 ms

form.js

form.js

67 ms

funcoes.js

funcoes.js

67 ms

show_ads.js

show_ads.js

26 ms

widgets.js

widgets.js

4 ms

urchin.js

urchin.js

30 ms

plusone.js

plusone.js

63 ms

ca-pub-4546573265438173.js

ca-pub-4546573265438173.js

140 ms

zrt_lookup.html

zrt_lookup.html

160 ms

show_ads_impl.js

show_ads_impl.js

71 ms

all.js

all.js

300 ms

__utm.gif

__utm.gif

38 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

98 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

116 ms

fastbutton

fastbutton

182 ms

LuijJY

LuijJY

142 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

137 ms

bgPage.jpg

bgPage.jpg

104 ms

topHeader.gif

topHeader.gif

103 ms

bgConteiner.jpg

bgConteiner.jpg

102 ms

torpedoFree.jpg

torpedoFree.jpg

102 ms

barOperadoras.png

barOperadoras.png

102 ms

bgTorpedo.jpg

bgTorpedo.jpg

103 ms

captcha.php

captcha.php

135 ms

enviar.png

enviar.png

134 ms

bgFooter.gif

bgFooter.gif

135 ms

ads

ads

251 ms

osd.js

osd.js

51 ms

ads

ads

167 ms

postmessageRelay

postmessageRelay

96 ms

ads

ads

245 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

68 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

53 ms

ads

ads

284 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

100 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

44 ms

ads

ads

219 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

99 ms

rpc:shindig_random.js

rpc:shindig_random.js

60 ms

244 ms

xd_arbiter.php

xd_arbiter.php

279 ms

xd_arbiter.php

xd_arbiter.php

522 ms

abg.js

abg.js

66 ms

m_js_controller.js

m_js_controller.js

89 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

120 ms

9419100539759835693

9419100539759835693

120 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

11 ms

s

s

68 ms

x_button_blue2.png

x_button_blue2.png

64 ms

jot

jot

219 ms

13385851423361767057

13385851423361767057

82 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

30 ms

10516069097106542847

10516069097106542847

38 ms

ui

ui

31 ms

like.php

like.php

95 ms

like_box.php

like_box.php

182 ms

nb2KQdOt9D0.js

nb2KQdOt9D0.js

489 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

348 ms

ebiMDO3r-8l.css

ebiMDO3r-8l.css

212 ms

jGc-59L_9lo.css

jGc-59L_9lo.css

205 ms

TKuNj0xVh4A.js

TKuNj0xVh4A.js

277 ms

VvsfEObxnnn.js

VvsfEObxnnn.js

339 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

271 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

297 ms

297306_264384046925506_413238708_n.jpg

297306_264384046925506_413238708_n.jpg

460 ms

47245_1002169756525946_5257628118132587123_n.jpg

47245_1002169756525946_5257628118132587123_n.jpg

523 ms

12565477_1675094129439026_9176573778566066336_n.jpg

12565477_1675094129439026_9176573778566066336_n.jpg

593 ms

12809605_1074320639297477_5404953235140347575_n.jpg

12809605_1074320639297477_5404953235140347575_n.jpg

721 ms

1238877_957623570988714_8224831122817816920_n.jpg

1238877_957623570988714_8224831122817816920_n.jpg

662 ms

10405375_936420839812931_8345111664181562437_n.jpg

10405375_936420839812931_8345111664181562437_n.jpg

845 ms

10958924_724849624279142_1120672359694537519_n.jpg

10958924_724849624279142_1120672359694537519_n.jpg

869 ms

12729346_974659495943115_8160915390130322483_n.jpg

12729346_974659495943115_8160915390130322483_n.jpg

722 ms

10155826_759162630775165_111812521_n.jpg

10155826_759162630775165_111812521_n.jpg

700 ms

10407830_655471914508690_3710521677741667222_n.jpg

10407830_655471914508690_3710521677741667222_n.jpg

789 ms

12806134_973493896079301_9199480510300208110_n.jpg

12806134_973493896079301_9199480510300208110_n.jpg

829 ms

10665158_389061137918152_3070103766003312310_n.jpg

10665158_389061137918152_3070103766003312310_n.jpg

856 ms

12805889_973898446032500_4410116908795718878_n.jpg

12805889_973898446032500_4410116908795718878_n.jpg

986 ms

10371517_10204437475096276_7512248997425236353_n.jpg

10371517_10204437475096276_7512248997425236353_n.jpg

854 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

70 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

69 ms

activeview

activeview

13 ms

activeview

activeview

14 ms

activeview

activeview

19 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

70 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

136 ms

SEO Factors

torpedofree.com 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 Torpedofree.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 Torpedofree.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.

Social Sharing Optimization

torpedofree.com

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