Tools & Wizards About Us
ttime.com.br screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ttime.com.br

TTime Relógios

Page Load Speed

8.6 sec in total

First Response

594 ms

Resources Loaded

7.6 sec

Page Rendered

422 ms

ttime.com.br screenshot

About Website

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

Relógios ttime, aqui você pode comprar relógios originais com toda segurança. Tudo sobre relógios você encontra na TTime, frete grátis acima de R$ 500,00 reais e parcelamento em 10x, as melhores marca...

Visit ttime.com.br

Key Findings

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

Performance Metrics

ttime.com.br performance score

0

Network Requests Diagram

ttime.com.br

594 ms

www.ttime.com.br

1926 ms

css

66 ms

css

79 ms

padroes.css

300 ms

Our browser made a total of 166 requests to load all elements on the main page. We found that 63% of them (105 requests) were addressed to the original Ttime.com.br, 6% (10 requests) were made to Static.xx.fbcdn.net and 6% (10 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Ttime.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 662.7 kB (36%)

Content Size

1.8 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ttime.com.br main page is 1.8 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. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 141.2 kB

  • Original 164.9 kB
  • After minification 124.3 kB
  • After compression 23.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 40.6 kB, which is 25% 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 141.2 kB or 86% of the original size.

Image Optimization

-13%

Potential reduce by 153.8 kB

  • Original 1.2 MB
  • After minification 1.0 MB

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, TTime needs image optimization as it can save up to 153.8 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 267.9 kB

  • Original 385.8 kB
  • After minification 342.9 kB
  • After compression 117.8 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 267.9 kB or 69% of the original size.

CSS Optimization

-81%

Potential reduce by 99.7 kB

  • Original 122.7 kB
  • After minification 92.9 kB
  • After compression 22.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. Ttime.com.br needs all CSS files to be minified and compressed as it can save up to 99.7 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

152

After Optimization

99

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ttime.com.br

ttime.com.br

594 ms

www.ttime.com.br

www.ttime.com.br

1926 ms

css

css

66 ms

css

css

79 ms

padroes.css

padroes.css

300 ms

estilo.css

estilo.css

317 ms

cabecalho.css

cabecalho.css

315 ms

rodape.css

rodape.css

319 ms

botoes.css

botoes.css

320 ms

menu.css

menu.css

316 ms

formularios.css

formularios.css

452 ms

conteudo.css

conteudo.css

466 ms

minhaNavegacao.css

minhaNavegacao.css

468 ms

listaPresentes.css

listaPresentes.css

470 ms

bannerDestaque.css

bannerDestaque.css

470 ms

destaqueHome.css

destaqueHome.css

476 ms

ie6nomore.js

ie6nomore.js

603 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

615 ms

jquery-ui-1.7.2.custom.css

jquery-ui-1.7.2.custom.css

622 ms

jquery.min.js

jquery.min.js

43 ms

jquery.lazyload.js

jquery.lazyload.js

619 ms

jquery.twitter.js

jquery.twitter.js

620 ms

jquery-ui-1.7.2.custom.min.js

jquery-ui-1.7.2.custom.min.js

955 ms

jquery.ui.datepicker-pt-BR.js

jquery.ui.datepicker-pt-BR.js

754 ms

wsrotator.js

wsrotator.js

764 ms

jquery.jcarousel.pack.js

jquery.jcarousel.pack.js

776 ms

webtrack.js

webtrack.js

694 ms

jquery.metadata.js

jquery.metadata.js

775 ms

xajax.js

xajax.js

774 ms

suggestions.css

suggestions.css

908 ms

aw.js

aw.js

32 ms

getSelo.js

getSelo.js

32 ms

conversion.js

conversion.js

26 ms

jquery.flexslider.js

jquery.flexslider.js

785 ms

seal.png

seal.png

706 ms

chat.jpg

chat.jpg

164 ms

fone.jpg

fone.jpg

163 ms

logo.png

logo.png

164 ms

lupa.jpg

lupa.jpg

178 ms

banner217.jpg

banner217.jpg

939 ms

banner207.jpg

banner207.jpg

784 ms

banner213.jpg

banner213.jpg

855 ms

banner215.jpg

banner215.jpg

871 ms

banner112.png

banner112.png

483 ms

banner113.jpg

banner113.jpg

483 ms

banner81.jpg

banner81.jpg

659 ms

35.png

35.png

658 ms

5.png

5.png

883 ms

8.png

8.png

882 ms

12.png

12.png

935 ms

7.png

7.png

938 ms

13.png

13.png

1024 ms

15.png

15.png

1037 ms

32.png

32.png

1044 ms

29.png

29.png

1091 ms

33.png

33.png

1094 ms

18.png

18.png

1096 ms

37.png

37.png

1179 ms

6.png

6.png

1192 ms

14.png

14.png

1205 ms

9.png

9.png

1246 ms

17.png

17.png

1244 ms

3.png

3.png

1246 ms

30.jpeg

30.jpeg

1334 ms

10.png

10.png

1344 ms

19.png

19.png

1365 ms

2.png

2.png

1395 ms

22.png

22.png

1397 ms

23.png

23.png

1399 ms

27.png

27.png

1489 ms

26.png

26.png

1491 ms

MG9KbUZFchDs94Tbv9U-paCWcynf_cDxXwCLxiixG1c.ttf

MG9KbUZFchDs94Tbv9U-paCWcynf_cDxXwCLxiixG1c.ttf

24 ms

SQVfzoJBbj9t3aVcmbspRonF5uFdDttMLvmWuJdhhgs.ttf

SQVfzoJBbj9t3aVcmbspRonF5uFdDttMLvmWuJdhhgs.ttf

27 ms

uDssvmXgp7Nj3i336k_dSonF5uFdDttMLvmWuJdhhgs.ttf

uDssvmXgp7Nj3i336k_dSonF5uFdDttMLvmWuJdhhgs.ttf

33 ms

gtm.js

gtm.js

23 ms

28.png

28.png

1370 ms

20.png

20.png

1396 ms

BkZwJXYnumPMepfEA344yQ.ttf

BkZwJXYnumPMepfEA344yQ.ttf

14 ms

eFfAHNfFT0YtF77QmRKRj_esZW2xOQ-xsNqO47m55DA.ttf

eFfAHNfFT0YtF77QmRKRj_esZW2xOQ-xsNqO47m55DA.ttf

15 ms

11.png

11.png

1394 ms

all.js

all.js

506 ms

banner151.jpg

banner151.jpg

1385 ms

plusone.js

plusone.js

374 ms

siteblindado_float_no_var.png

siteblindado_float_no_var.png

300 ms

81 ms

170_12145.jpeg

170_12145.jpeg

1168 ms

ga.js

ga.js

48 ms

170_12224.jpeg

170_12224.jpeg

1174 ms

96 ms

__utm.gif

__utm.gif

33 ms

73 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

22 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

53 ms

badge

badge

129 ms

51 ms

collect

collect

85 ms

postmessageRelay

postmessageRelay

58 ms

170_8722.jpeg

170_8722.jpeg

1044 ms

170_12561.jpeg

170_12561.jpeg

1057 ms

ga-audiences

ga-audiences

31 ms

api.js

api.js

70 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

144 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

77 ms

242 ms

rs=AGLTcCP3O_7Lv6wPM9DLZp_DouM8Z1J9hQ

rs=AGLTcCP3O_7Lv6wPM9DLZp_DouM8Z1J9hQ

21 ms

rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA

rs=AGLTcCNVayw58ATXmq5na_KkaQDUov7ewA

32 ms

rs=AGLTcCN83Zh9DgdfiROJBeJpzV1blLFVlA

rs=AGLTcCN83Zh9DgdfiROJBeJpzV1blLFVlA

73 ms

xd_arbiter.php

xd_arbiter.php

299 ms

xd_arbiter.php

xd_arbiter.php

512 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

103 ms

dtpHsbgPEm2lVWciJZ0P-A.ttf

dtpHsbgPEm2lVWciJZ0P-A.ttf

115 ms

bdHGHleUa-ndQCOrdpfxfw.ttf

bdHGHleUa-ndQCOrdpfxfw.ttf

127 ms

rs=AGLTcCN83Zh9DgdfiROJBeJpzV1blLFVlA

rs=AGLTcCN83Zh9DgdfiROJBeJpzV1blLFVlA

41 ms

9.png

9.png

868 ms

170_9076.jpeg

170_9076.jpeg

863 ms

170_15341.jpeg

170_15341.jpeg

941 ms

11.png

11.png

935 ms

170_9765.jpeg

170_9765.jpeg

983 ms

rs=AGLTcCN83Zh9DgdfiROJBeJpzV1blLFVlA

rs=AGLTcCN83Zh9DgdfiROJBeJpzV1blLFVlA

5 ms

170_14280.jpeg

170_14280.jpeg

936 ms

170_15993.jpeg

170_15993.jpeg

939 ms

170_8428.jpeg

170_8428.jpeg

940 ms

170_15371.jpeg

170_15371.jpeg

948 ms

170_1900.jpeg

170_1900.jpeg

940 ms

170_11307.jpeg

170_11307.jpeg

990 ms

170_3932.jpeg

170_3932.jpeg

937 ms

170_15987.jpeg

170_15987.jpeg

938 ms

170_14834.jpeg

170_14834.jpeg

940 ms

170_11112.jpeg

170_11112.jpeg

947 ms

170_15869.jpeg

170_15869.jpeg

941 ms

170_9950.jpeg

170_9950.jpeg

981 ms

170_15611.jpeg

170_15611.jpeg

952 ms

170_9548.jpeg

170_9548.jpeg

945 ms

170_10163.jpeg

170_10163.jpeg

948 ms

170_11121.jpeg

170_11121.jpeg

952 ms

170_12781.jpeg

170_12781.jpeg

946 ms

logoRodape.jpg

logoRodape.jpg

977 ms

formas-pagamento.jpg

formas-pagamento.jpg

953 ms

cadeadoSSL.jpg

cadeadoSSL.jpg

954 ms

safegoogle.jpg

safegoogle.jpg

957 ms

webstormInternet.png

webstormInternet.png

952 ms

sprites_01.png

sprites_01.png

950 ms

styleLateral.png

styleLateral.png

970 ms

Newsletter.png

Newsletter.png

951 ms

btCadastrar.jpg

btCadastrar.jpg

953 ms

voltarMarcas.png

voltarMarcas.png

964 ms

avancarMarcas.png

avancarMarcas.png

953 ms

mobile.css

mobile.css

160 ms

img_42472.png

img_42472.png

361 ms

like_box.php

like_box.php

98 ms

jTuqQ-OPDr6.css

jTuqQ-OPDr6.css

293 ms

n370yiaI2G6.css

n370yiaI2G6.css

354 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

490 ms

eqcyIzISC_n.js

eqcyIzISC_n.js

621 ms

ICDbTSzjQEg.js

ICDbTSzjQEg.js

510 ms

TTCre3391I0.js

TTCre3391I0.js

510 ms

12745412_776069049203136_4529342820506909160_n.jpg

12745412_776069049203136_4529342820506909160_n.jpg

346 ms

10169397_453783188098392_6877372923811016256_n.png

10169397_453783188098392_6877372923811016256_n.png

413 ms

11760171_1047666705245392_7925080133191047626_n.jpg

11760171_1047666705245392_7925080133191047626_n.jpg

485 ms

1012141_948794961864389_4688549599290682871_n.jpg

1012141_948794961864389_4688549599290682871_n.jpg

548 ms

14413_764239433673323_5971539737153112436_n.jpg

14413_764239433673323_5971539737153112436_n.jpg

549 ms

12745627_1698545760384411_8577257509208725425_n.jpg

12745627_1698545760384411_8577257509208725425_n.jpg

550 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

71 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

71 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

69 ms

vlXaquuXMrr.js

vlXaquuXMrr.js

71 ms

SEO Factors

ttime.com.br SEO score

0

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

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

Social Sharing Optimization

ttime.com.br

Open Graph description is not detected on the main page of TTime. 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: