34.9 sec in total
908 ms
33.3 sec
615 ms
Welcome to gazin.com.br homepage info - get ready to check Gazin best content for Brazil right away, or after learning these important things about gazin.com.br
Encontre na Gazin uma ampla seleção de telefonia, eletrodomésticos e muito mais. Produtos de qualidade com os melhores preços do mercado. Acesse já!
Visit gazin.com.brWe analyzed Gazin.com.br page load time and found that the first response time was 908 ms and then it took 34 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 30 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
gazin.com.br performance score
name
value
score
weighting
Value10.2 s
0/100
10%
Value14.9 s
0/100
25%
Value16.9 s
0/100
10%
Value4,550 ms
0/100
30%
Value0.334
34/100
15%
Value17.9 s
4/100
10%
908 ms
37 ms
168 ms
746 ms
1082 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 70% of them (105 requests) were addressed to the original Gazin.com.br, 13% (20 requests) were made to Static.xx.fbcdn.net and 5% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Gazin.com.br.
Page size can be reduced by 780.0 kB (23%)
3.4 MB
2.6 MB
In fact, the total size of Gazin.com.br main page is 3.4 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. 50% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 52.4 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 52.4 kB or 80% of the original size.
Potential reduce by 272.2 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. Gazin images are well optimized though.
Potential reduce by 228.4 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 228.4 kB or 71% of the original size.
Potential reduce by 227.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. Gazin.com.br needs all CSS files to be minified and compressed as it can save up to 227.0 kB or 86% of the original size.
Number of requests can be reduced by 50 (47%)
107
57
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gazin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
gazin.com.br
908 ms
css
37 ms
normalize.css
168 ms
foundation.css
746 ms
style.css
1082 ms
timeline.css
335 ms
responsive.css
339 ms
flexslider.css
338 ms
fancybox.css
375 ms
fancybox-buttons.css
510 ms
fancybox-thumbs.css
505 ms
foundation-icons.css
507 ms
jquery.js
960 ms
modernizr.js
700 ms
jquery-migrate-1.2.1.min.js
32 ms
fancybox.js
705 ms
fancybox.pack.js
703 ms
fancybox-buttons.js
870 ms
fancybox-media.js
1347 ms
fancybox-thumbs.js
872 ms
flexslider.js
1136 ms
maskedinput-1.3.min.js
1040 ms
placeholder.js
1037 ms
platform.js
93 ms
fancybox_overlay.png
196 ms
icon-cart1.png
195 ms
patner_1.png
196 ms
logo_topo.png
354 ms
icn_menu_1.png
198 ms
icn_menu_5.png
197 ms
icn_menu_4.png
342 ms
icn_menu_8.png
337 ms
icn_menu_7.png
343 ms
icn_menu_11.png
344 ms
icn_menu_10.png
345 ms
icn_menu_3.png
500 ms
icn_menu_2.png
512 ms
icn_menu_6.png
907 ms
online.jpg
910 ms
48a8d6d3d076f58539bb405eb286700e.png
19652 ms
37d37369608fd5302915ae85c64976b4.png
19652 ms
279a0a20573557fe496f2acd97efe357.png
19652 ms
f34e794dca0b1212261bcf9e4efa1f61.jpg
19654 ms
be459d8d3d775caabad6d62a8de678cd.png
19655 ms
ca354617ddd72f6c7fb6ac06b22b27ad.jpg
19655 ms
0020035adb918dbe514ef5970596e743.jpg
19656 ms
bbfd4d41eb6df15d0c0915ef0d9b2fec.jpg
19656 ms
icn_sessao_0.png
19657 ms
icn_sessao_0.hover.png
19657 ms
img_1.jpg
19657 ms
icn_sessao_1.png
19658 ms
icn_sessao_1.hover.png
19658 ms
img_2.jpg
19658 ms
icn_sessao_2.png
19659 ms
icn_sessao_2.hover.png
19659 ms
img_3.jpg
19659 ms
icn_sessao_3.png
19660 ms
icn_sessao_3.hover.png
19660 ms
img_4.jpg
19661 ms
icn_sessao_4.png
19634 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
78 ms
DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff
78 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
79 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
77 ms
EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff
78 ms
sdk.js
309 ms
widgets.js
70 ms
analytics.js
69 ms
jot
94 ms
collect
17 ms
icn_sessao_4.hover.png
19783 ms
img_5.jpg
20458 ms
icn_sessao_5.png
19795 ms
icn_sessao_5.hover.png
19970 ms
img_6.jpg
20456 ms
icn_sessao_6.png
20318 ms
icn_sessao_6.hover.png
19806 ms
img_7.jpg
19821 ms
icn_sessao_7.png
20158 ms
icn_sessao_7.hover.png
20308 ms
img_8.jpg
20302 ms
192 ms
xd_arbiter.php
235 ms
xd_arbiter.php
484 ms
icn_sessao_8.png
20155 ms
icn_sessao_8.hover.png
20143 ms
img_60.jpg
19748 ms
150
19744 ms
150
1869 ms
150
1856 ms
150
2231 ms
150
2262 ms
150
2061 ms
150
1679 ms
150
3200 ms
gazin_promo.jpg
2553 ms
img_10.jpg
2555 ms
img_11.jpg
8171 ms
img_12.jpg
4933 ms
50f368556cfef4a25750df90c627b7bb.png
3394 ms
2426f9ba12bf9f4b6b44b3f981f26e09.png
3419 ms
e3633cbba67e0c77f4ed94d399940014.png
3253 ms
8d4f7bdd889ea27df5984f7b7963b1c6.png
6054 ms
d6a9bf0c3f918dae68755c21e1b7b7fa.png
6567 ms
14a23f3bd0b8541ceefa907f0f489b35.jpg
4467 ms
36ae318b7f935a15ab6cce7b929d417a.jpg
4128 ms
09fe343e4aa6fe6e169680cb5d06c890.png
5268 ms
7e566dd71fa277cf4aee1e098699f839.png
7149 ms
9b262dda40f160624bf121097a370a9d.png
6068 ms
d6bcda4cdd4d37594525d6186e53bce5.png
8261 ms
a9ab0f49275bfff021d504ca001628cb.png
8867 ms
iconmonstr.png
5784 ms
icn_inove.png
5943 ms
icon_search.png
6110 ms
img_0.jpg
6388 ms
icn_newsletter.png
5794 ms
icn_f_facebook.jpg
5961 ms
icn_f_youtube.jpg
6130 ms
icn_f_linkedin.jpg
6300 ms
bg_direction_nav.png
721 ms
bg_direction_nav_azul.png
171 ms
like_box.php
322 ms
4zvF1Y0eZKv.css
375 ms
FrSU6IlfEX1.css
446 ms
GZeiuqs6M9H.css
517 ms
SRSW8M763HA.js
714 ms
tSWhWrlb_aI.js
733 ms
y97Ig99UVTs.js
582 ms
KHAtULXOQuz.js
585 ms
XlY_wsDnClE.js
653 ms
rR4Qw0p7TFQ.js
765 ms
ULtnh-HfQSw.js
649 ms
d_-F4IIjJo3.js
655 ms
FOagnU9QnXq.js
806 ms
Cw6QosZRsiU.js
753 ms
i8XO-4kv8i7.js
752 ms
z5eMxBRE-Ji.js
791 ms
7YklgZdHLYS.js
819 ms
12342612_999389766784911_8617029601265675410_n.png
517 ms
12688081_1029201883803699_9147617381699714581_n.png
591 ms
12346356_781393098653969_5893760751751126778_n.jpg
742 ms
12800239_818512344962115_8941966595578915546_n.jpg
921 ms
12919892_611828318968107_321345164355586119_n.jpg
778 ms
12814357_895887980528198_995487535280894806_n.jpg
744 ms
8273_975416922566407_2773022608001427694_n.jpg
921 ms
12651150_784002741705992_8077214096111228793_n.jpg
797 ms
wL6VQj7Ab77.png
82 ms
1JLnMyDN79z.png
81 ms
FASTu8Ostla.png
70 ms
VXcANLwwL5J.js
90 ms
gazin.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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
gazin.com.br best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
gazin.com.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gazin.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 Gazin.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.
gazin.com.br
Open Graph description is not detected on the main page of Gazin. 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: