3.4 sec in total
324 ms
2.8 sec
344 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 324 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
gazin.com.br performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value16.1 s
0/100
25%
Value13.1 s
2/100
10%
Value12,040 ms
0/100
30%
Value0.269
46/100
15%
Value26.0 s
0/100
10%
324 ms
1331 ms
706 ms
487 ms
598 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 71% of them (36 requests) were addressed to the original Gazin.com.br, 29% (15 requests) were made to Gazin-images.gazin.com.br. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Gazin.com.br.
Page size can be reduced by 290.6 kB (64%)
455.6 kB
165.0 kB
In fact, the total size of Gazin.com.br main page is 455.6 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. 50% of websites need less resources to load. HTML takes 357.8 kB which makes up the majority of the site volume.
Potential reduce by 290.6 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 290.6 kB or 81% of the original size.
Potential reduce by 0 B
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.
Number of requests can be reduced by 16 (33%)
49
33
The browser has sent 49 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 17 to 1 for JavaScripts and as a result speed up the page load time.
gazin.com.br
324 ms
www.gazin.com.br
1331 ms
c02b3261e5c4b583.css
706 ms
6f05ebba79ec67b1.css
487 ms
polyfills-c67a75d1b6f99dc8.js
598 ms
webpack-bea180ee3d28b04c.js
477 ms
framework-b78bc773b89d3272.js
804 ms
main-0b9464953898b529.js
804 ms
_app-5e501164f571de23.js
1560 ms
0c428ae2-292ad0f09a18e870.js
811 ms
fec483df-1002bcbfd44070ed.js
812 ms
3883-5637c4053c4c24f9.js
943 ms
6310-33ed757c7f16baf5.js
924 ms
5108-bddc75b7541e27ec.js
925 ms
4679-0ead4a4a6db7994e.js
938 ms
1883-9fa794757aacd803.js
1076 ms
335-d7a985da14421583.js
1045 ms
924-a3a971d00e98b074.js
1073 ms
index-95304ff57acaccb5.js
1092 ms
_buildManifest.js
1072 ms
_ssgManifest.js
1163 ms
banner-5479-102405390230.png
884 ms
user.svg
994 ms
image
966 ms
bag-cart.svg
973 ms
banner-2212-112405450240.png
942 ms
banner-2214-112405500218.png
943 ms
banner-2215-112405410308.png
944 ms
banner-2217-162404062900.png
945 ms
banner-2216-162404012939.png
942 ms
banner-2218-162404082914.png
1161 ms
banner-2219-162404142947.png
1285 ms
banner-2220-112405540258.png
1441 ms
banner-2213-152404512958.png
1443 ms
banner-2222-162404232932.png
1333 ms
banner-5467-162404452952.png
1178 ms
image
760 ms
icone-casamento.svg
871 ms
image
865 ms
icone-consorcio.svg
869 ms
image
881 ms
icon-seguros.svg
890 ms
image
984 ms
icone-credito.svg
1017 ms
image
995 ms
icone-atacado.svg
1004 ms
icon-seguranca.svg
1011 ms
banner-5466-162404442934.png
1159 ms
banner-5465-162404422955.png
1275 ms
banner-5464-162404272906.png
1283 ms
image
1018 ms
gazin.com.br accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[role] values are not valid
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
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
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
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
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: