Tools & Wizards About Us
telefonescelulares.com.br screenshot

Report Summary

  • 77

    Performance

    Renders faster than
    85% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

telefonescelulares.com.br

Telefones Celulares | Apps e produtividade no celular!

Page Load Speed

3 sec in total

First Response

353 ms

Resources Loaded

2.4 sec

Page Rendered

301 ms

telefonescelulares.com.br screenshot

About Website

Click here to check amazing Telefones Celulares content for Brazil. Otherwise, check out these important facts you probably never knew about telefonescelulares.com.br

Dicas de apps para Android, iPhone, Windows Mobile, comparador de celulares, marcas, planos e operadoras.

Visit telefonescelulares.com.br

Key Findings

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

Performance Metrics

telefonescelulares.com.br performance score

77

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

94/100

10%

LCP (Largest Contentful Paint)

Value1.6 s

99/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

www.telefonescelulares.com.br

353 ms

all_b427_1494.css

253 ms

adsbygoogle.js

11 ms

all_b427_1494.js

371 ms

wp-embed.min.js

1183 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 26% of them (20 requests) were addressed to the original Telefonescelulares.com.br, 10% (8 requests) were made to Googleads.g.doubleclick.net and 9% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Telefonescelulares.com.br.

Page Optimization Overview & Recommendations

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

Content Size

450.3 kB

After Optimization

244.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Telefonescelulares.com.br main page is 450.3 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. 70% of websites need less resources to load. Javascripts take 129.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 50.0 kB

  • Original 64.9 kB
  • After minification 64.6 kB
  • After compression 14.9 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 50.0 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 4.0 kB

  • Original 128.9 kB
  • After minification 124.8 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. Telefones Celulares images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 47.0 kB

  • Original 129.0 kB
  • After minification 128.8 kB
  • After compression 82.0 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 47.0 kB or 36% of the original size.

CSS Optimization

-82%

Potential reduce by 105.1 kB

  • Original 127.6 kB
  • After minification 126.0 kB
  • After compression 22.4 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. Telefonescelulares.com.br needs all CSS files to be minified and compressed as it can save up to 105.1 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (40%)

Requests Now

73

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.telefonescelulares.com.br

www.telefonescelulares.com.br

353 ms

all_b427_1494.css

all_b427_1494.css

253 ms

adsbygoogle.js

adsbygoogle.js

11 ms

all_b427_1494.js

all_b427_1494.js

371 ms

wp-embed.min.js

wp-embed.min.js

1183 ms

logo.png

logo.png

80 ms

celular-quebrado-100x100.jpg

celular-quebrado-100x100.jpg

1124 ms

windows-phone-100x100.jpg

windows-phone-100x100.jpg

1124 ms

celular-travando-100x100.jpg

celular-travando-100x100.jpg

1062 ms

teste-bateria-100x100.jpg

teste-bateria-100x100.jpg

194 ms

whatsapp-100x100.jpg

whatsapp-100x100.jpg

242 ms

smartphone-100x100.png

smartphone-100x100.png

349 ms

kit-lentes-100x100.jpg

kit-lentes-100x100.jpg

332 ms

iris-100x100.jpg

iris-100x100.jpg

397 ms

broadcast-100x100.jpeg

broadcast-100x100.jpeg

437 ms

erro-google-100x100.jpg

erro-google-100x100.jpg

444 ms

digito-100x100.jpg

digito-100x100.jpg

490 ms

celular-100x100.jpg

celular-100x100.jpg

556 ms

ca-pub-1863532356489327.js

ca-pub-1863532356489327.js

58 ms

zrt_lookup.html

zrt_lookup.html

62 ms

show_ads_impl.js

show_ads_impl.js

85 ms

glyphicons-halflings.png

glyphicons-halflings.png

535 ms

yt-btn.png

yt-btn.png

618 ms

widgets.js

widgets.js

12 ms

feed.png

feed.png

684 ms

sdk.js

sdk.js

113 ms

platform.js

platform.js

210 ms

cse.js

cse.js

29 ms

analytics.js

analytics.js

76 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

133 ms

cse.js

cse.js

221 ms

pla

pla

83 ms

collect

collect

70 ms

collect

collect

233 ms

ads

ads

327 ms

osd.js

osd.js

48 ms

ads

ads

253 ms

ads

ads

292 ms

176 ms

ads

ads

246 ms

xd_arbiter.php

xd_arbiter.php

161 ms

xd_arbiter.php

xd_arbiter.php

247 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

96 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

120 ms

fastbutton

fastbutton

186 ms

follow_button.6a78875565a912489e9aef879c881358.pt.html

follow_button.6a78875565a912489e9aef879c881358.pt.html

58 ms

tweet_button.6a78875565a912489e9aef879c881358.pt.html

tweet_button.6a78875565a912489e9aef879c881358.pt.html

67 ms

ads

ads

385 ms

jsapi

jsapi

126 ms

ads

ads

360 ms

postmessageRelay

postmessageRelay

103 ms

abg.js

abg.js

100 ms

default+pt_PT.css

default+pt_PT.css

41 ms

default.css

default.css

84 ms

default+pt_PT.I.js

default+pt_PT.I.js

106 ms

m_js_controller.js

m_js_controller.js

107 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

269 ms

378784852393342141

378784852393342141

101 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

89 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

88 ms

api.js

api.js

76 ms

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

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

255 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

251 ms

default.css

default.css

126 ms

x_button_blue2.png

x_button_blue2.png

27 ms

s

s

25 ms

redir.html

redir.html

216 ms

favicon

favicon

214 ms

nessie_icon_thin_arrow_big_white.png

nessie_icon_thin_arrow_big_white.png

137 ms

async-ads.js

async-ads.js

199 ms

small-logo.png

small-logo.png

98 ms

favicon

favicon

104 ms

2202933171254811509

2202933171254811509

38 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

17 ms

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

28 ms

iframe.html

iframe.html

30 ms

jot.html

jot.html

45 ms

Accessibility Review

telefonescelulares.com.br accessibility score

100

Accessibility Issues

Best Practices

telefonescelulares.com.br best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

telefonescelulares.com.br SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Telefonescelulares.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Telefonescelulares.com.br 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

telefonescelulares.com.br

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