5.5 sec in total
780 ms
4 sec
717 ms
Visit afront.com.br now to see the best up-to-date Afront content and also check out these interesting facts you probably never knew about afront.com.br
A marca AFRONT JEANS entrou para o mundo da moda meados de 2003 com o objetivo de confeccionar produtos de excelência no mercado têxtil traduzindo as principais tendências da moda nacional e internaci...
Visit afront.com.brWe analyzed Afront.com.br page load time and found that the first response time was 780 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
afront.com.br performance score
780 ms
75 ms
86 ms
47 ms
252 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 47% of them (56 requests) were addressed to the original Afront.com.br, 12% (14 requests) were made to Maps.googleapis.com and 10% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Afront.com.br.
Page size can be reduced by 1.1 MB (10%)
10.6 MB
9.6 MB
In fact, the total size of Afront.com.br main page is 10.6 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. 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. Images take 9.2 MB which makes up the majority of the site volume.
Potential reduce by 40.5 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 40.5 kB or 80% of the original size.
Potential reduce by 56.4 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. Afront images are well optimized though.
Potential reduce by 771.1 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 771.1 kB or 68% of the original size.
Potential reduce by 183.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. Afront.com.br needs all CSS files to be minified and compressed as it can save up to 183.4 kB or 84% of the original size.
Number of requests can be reduced by 41 (39%)
106
65
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Afront. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
afront.com.br
780 ms
css
75 ms
css
86 ms
bootstrap.min.css
47 ms
style.css
252 ms
jquery.min.js
72 ms
styles.css
382 ms
sb-instagram.css
294 ms
font-awesome.min.css
35 ms
settings.css
388 ms
jquery.fancybox-1.3.7.min.css
395 ms
jquery.js
655 ms
jquery-migrate.min.js
376 ms
jquery.themepunch.tools.min.js
648 ms
jquery.themepunch.revolution.min.js
641 ms
jquery.form.min.js
518 ms
scripts.js
398 ms
sb-instagram.js
529 ms
wp-embed.min.js
525 ms
jquery.fancybox-1.3.7.min.js
668 ms
jquery.easing.pack.js
673 ms
jquery.mousewheel.min.js
672 ms
wp-emoji-release.min.js
506 ms
logo.png
301 ms
logo2.png
301 ms
facebook.png
300 ms
instagram.png
299 ms
youtube.png
298 ms
topo1-1.jpg
1243 ms
topo2-1.jpg
1253 ms
topo3-1.jpg
1241 ms
embed
277 ms
bgmarca.jpg
1195 ms
capa.jpg
985 ms
pagina2.jpg
1228 ms
pagina3.jpg
1389 ms
pagina4.jpg
1710 ms
pagina5.jpg
1606 ms
pagina6.jpg
1617 ms
pagina7.jpg
1629 ms
pagina8.jpg
1638 ms
pagina9.jpg
1651 ms
pagina10.jpg
1868 ms
pagina11.jpg
1882 ms
pagina12.jpg
2022 ms
pagina13.jpg
2028 ms
pagina14.jpg
1916 ms
pagina15.jpg
1968 ms
pagina16.jpg
2195 ms
pagina17.jpg
2166 ms
pagina18.jpg
2344 ms
pagina19.jpg
2428 ms
pagina20.jpg
2440 ms
contracapa.jpg
2204 ms
logocampanha.jpg
2307 ms
minitube.png
2456 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
258 ms
1ImRNPx4870-D9a1EBUdPC3USBnSvpkopQaUR-2r7iU.ttf
257 ms
PKCRbVvRfd5n7BTjtGiFZC3USBnSvpkopQaUR-2r7iU.ttf
260 ms
xkvoNo9fC8O2RDydKj12by3USBnSvpkopQaUR-2r7iU.ttf
261 ms
CcKI4k9un7TZVWzRVT-T8y3USBnSvpkopQaUR-2r7iU.ttf
260 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
260 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
283 ms
XVTNnV8ZlWWAo1TkpAuMaA.ttf
282 ms
loader.png
2287 ms
seguir.png
2378 ms
529958560
151 ms
recent
235 ms
529958560
178 ms
recent
234 ms
loader.gif
2234 ms
large_left.png
2234 ms
js
128 ms
init_embed.js
83 ms
large_right.png
2290 ms
ajax-loader.gif
2301 ms
11821803_436103643249449_2031859446_n.jpg
546 ms
10584741_543742842475256_1519516212_n.jpg
833 ms
925706_439619622903364_614260692_n.jpg
909 ms
12816902_1196853386999391_1378585864_n.jpg
1104 ms
917429_1147421701968944_1524059154_n.jpg
921 ms
11821803_436103643249449_2031859446_n.jpg
932 ms
10584741_543742842475256_1519516212_n.jpg
947 ms
925706_439619622903364_614260692_n.jpg
1054 ms
12816902_1196853386999391_1378585864_n.jpg
1369 ms
917429_1147421701968944_1524059154_n.jpg
1214 ms
common.js
107 ms
map.js
109 ms
google4.png
46 ms
overlay.js
43 ms
util.js
45 ms
onion.js
41 ms
search_impl.js
207 ms
StaticMapService.GetMapImage
189 ms
stats.js
89 ms
openhand_8_8.cur
76 ms
ViewportInfoService.GetViewportInfo
53 ms
ViewportInfoService.GetViewportInfo
42 ms
transparent.png
25 ms
kh
159 ms
controls.js
52 ms
ViewportInfoService.GetViewportInfo
115 ms
vt
111 ms
vt
138 ms
vt
146 ms
vt
153 ms
vt
164 ms
vt
149 ms
vt
150 ms
css
88 ms
entity11.png
83 ms
mapcnt6.png
72 ms
sv5.png
75 ms
tmapctrl.png
63 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
9 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
18 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
18 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
18 ms
AuthenticationService.Authenticate
29 ms
afront.com.br SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Afront.com.br can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Afront.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.
afront.com.br
Open Graph description is not detected on the main page of Afront. 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: