9.1 sec in total
2 sec
6.9 sec
230 ms
Click here to check amazing Com Eback content. Otherwise, check out these important facts you probably never knew about comeback.com.br
Bluehost - Top rated web hosting provider - Free 1 click installs For blogs, shopping carts, and more. Get a free domain name, real NON-outsourced 24/7 support, and superior speed. web hosting provide...
Visit comeback.com.brWe analyzed Comeback.com.br page load time and found that the first response time was 2 sec and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
comeback.com.br performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value1.4 s
100/100
25%
Value1.3 s
100/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value1.7 s
100/100
10%
2020 ms
159 ms
155 ms
281 ms
280 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 16% of them (22 requests) were addressed to the original Comeback.com.br, 9% (12 requests) were made to 4236808.fls.doubleclick.net and 8% (11 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Comeback.com.br.
Page size can be reduced by 619.2 kB (63%)
980.4 kB
361.2 kB
In fact, the total size of Comeback.com.br main page is 980.4 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. 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 680.3 kB which makes up the majority of the site volume.
Potential reduce by 41.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 41.7 kB or 77% of the original size.
Potential reduce by 4.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. Com Eback images are well optimized though.
Potential reduce by 463.7 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 463.7 kB or 68% of the original size.
Potential reduce by 109.2 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. Comeback.com.br needs all CSS files to be minified and compressed as it can save up to 109.2 kB or 75% of the original size.
Number of requests can be reduced by 75 (58%)
129
54
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Com Eback. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.comeback.com.br
2020 ms
wp-emoji-release.min.js
159 ms
widget.css
155 ms
gtranslate-style16.css
281 ms
thickbox.css
280 ms
wpsc-default.css
295 ms
compatibility.css
293 ms
adsns.css
305 ms
main.min.css
297 ms
css
75 ms
genericons.css
547 ms
style.css
412 ms
style.css
452 ms
jquery.js
604 ms
jquery-migrate.min.js
426 ms
wp-e-commerce.js
600 ms
jquery.livequery.js
549 ms
user.js
582 ms
thickbox.js
599 ms
pagination.css
687 ms
show_ads.js
17 ms
masonry.min.js
683 ms
jquery.masonry.min.js
727 ms
functions.js
794 ms
widgets.js
96 ms
all.js
19 ms
plusone.js
44 ms
ga.js
5 ms
__utm.gif
54 ms
ca-pub-5019863710843141.js
296 ms
zrt_lookup.html
291 ms
show_ads_impl.js
136 ms
1bHRUMxmJHoup12DnI9XmQ.woff
289 ms
kU6VHbqMAZhaN_nXCmLQsQ.woff
352 ms
I1Pn3gihk5vyP0Yw5GqKsQ.woff
389 ms
7DI7Kjvwfuz8m3ExKe6m-Q.woff
441 ms
VqvVqv1mv0Gr1Gr9Frul7xuyp+V8XvqnTyb1UoNRm4Af+FsAGNAEuwCFBYsQEBjlmxRgYrWCGwEFlLsBRSWCGwgFkdsAYrXFhZsBQrAAAAAVLP0T8AAA==
11 ms
analytics.js
132 ms
all.js
217 ms
cb=gapi.loaded_0
271 ms
cb=gapi.loaded_1
343 ms
fastbutton
446 ms
fastbutton
444 ms
fastbutton
455 ms
ads
279 ms
264 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
267 ms
osd.js
75 ms
collect
87 ms
245 ms
xd_arbiter.php
113 ms
xd_arbiter.php
242 ms
ads
254 ms
ads
283 ms
collect
235 ms
xd_arbiter.php
56 ms
like.php
113 ms
278 ms
adj
233 ms
beacon
265 ms
postmessageRelay
212 ms
like.php
161 ms
like.php
183 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
92 ms
229 ms
adj
187 ms
beacon
176 ms
qeKvIRsJabD.js
206 ms
rs=AGLTcCMmxxv5a__MjyaVcD74l1XyH_kiOQ
67 ms
LVx-xkvaJ0b.png
255 ms
182 ms
adj
190 ms
beacon
174 ms
cb=gapi.loaded_0
70 ms
cb=gapi.loaded_1
69 ms
grlryt2bdKIyfMSOhzd1eA.woff
56 ms
3193398744-postmessagerelay.js
102 ms
rpc:shindig_random.js
48 ms
102 ms
activityi;src=4236808;type=invmedia;cat=aoyjbkr6;ord=-1273246650
271 ms
activityi;src=4236808;type=invmedia;cat=ijhardnr;ord=-1273246650
265 ms
activityi;src=4236808;type=invmedia;cat=4ztf2oue;ord=-1273246650
267 ms
activityi;src=4236808;type=invmedia;cat=qk1cfvwl;ord=-1273246650
269 ms
0
258 ms
surly.js
177 ms
115 ms
activityi;src=4236808;type=invmedia;cat=ijhardnr;ord=-82181537
228 ms
activityi;src=4236808;type=invmedia;cat=qk1cfvwl;ord=-82181537
240 ms
activityi;src=4236808;type=invmedia;cat=4ztf2oue;ord=-82181537
290 ms
activityi;src=4236808;type=invmedia;cat=aoyjbkr6;ord=-82181537
301 ms
107 ms
activityi;src=4236808;type=invmedia;cat=4ztf2oue;ord=907728558
295 ms
activityi;src=4236808;type=invmedia;cat=ijhardnr;ord=907728558
292 ms
activityi;src=4236808;type=invmedia;cat=aoyjbkr6;ord=907728558
284 ms
activityi;src=4236808;type=invmedia;cat=qk1cfvwl;ord=907728558
285 ms
cb=gapi.loaded_0
89 ms
index.html
412 ms
verify_selector.js
272 ms
blank.gif
276 ms
index.html
528 ms
verify_selector.js
237 ms
bapi
361 ms
blank.gif
235 ms
index.html
525 ms
verify_selector.js
264 ms
blank.gif
227 ms
ba.html
88 ms
pixel
113 ms
pixel
115 ms
pixel
113 ms
4.gif
110 ms
lidar.js
79 ms
sbhK2lTE.js
138 ms
4311.js
32 ms
pixel
97 ms
pixel
110 ms
jot.html
61 ms
cTrvNaRi.html
41 ms
verifyr.js
144 ms
verifyr.js
167 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
13 ms
verifyr.js
183 ms
beacon.js
204 ms
0
168 ms
bg.png
176 ms
adchoices.en.png
160 ms
dbapi
136 ms
dt
148 ms
sd
52 ms
Rejuvenation_300x250_logo.gif
62 ms
MommyMakeover_300x250_bg.jpg
60 ms
dt
112 ms
BreastAugmentation_300x250_logo.png
65 ms
BreastAugmentation_300x250_bg2.jpg
64 ms
BreastAugmentation_300x250_bg1.jpg
64 ms
FaceBody_300x250_logo.gif
117 ms
FaceBody_300x250_bg.jpg
118 ms
box_19_top-right.png
43 ms
ci.png
41 ms
comeback.com.br accessibility score
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
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
comeback.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
comeback.com.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
robots.txt is not valid
EN
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Comeback.com.br can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Portuguese language. Our system also found out that Comeback.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.
comeback.com.br
Open Graph data is detected on the main page of Com Eback. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: