6.1 sec in total
570 ms
5.4 sec
147 ms
Click here to check amazing Malwee content for Brazil. Otherwise, check out these important facts you probably never knew about malwee.com.br
Confira diversas opções de Moda feminina, masculina, plus size e infantil na Malwee. Compre roupas parcelando em até 10x sem juros. Saiba mais!
Visit malwee.com.brWe analyzed Malwee.com.br page load time and found that the first response time was 570 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
malwee.com.br performance score
name
value
score
weighting
Value8.2 s
0/100
10%
Value14.1 s
0/100
25%
Value13.7 s
1/100
10%
Value4,250 ms
1/100
30%
Value1.401
0/100
15%
Value20.7 s
2/100
10%
570 ms
627 ms
612 ms
461 ms
1253 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 46% of them (38 requests) were addressed to the original Malwee.com.br, 9% (7 requests) were made to Apis.google.com and 5% (4 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Malwee.com.br.
Page size can be reduced by 471.7 kB (20%)
2.3 MB
1.9 MB
In fact, the total size of Malwee.com.br main page is 2.3 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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 77.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 77.6 kB or 78% of the original size.
Potential reduce by 138.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. Malwee images are well optimized though.
Potential reduce by 214.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 214.1 kB or 60% of the original size.
Potential reduce by 41.9 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. Malwee.com.br needs all CSS files to be minified and compressed as it can save up to 41.9 kB or 78% of the original size.
Number of requests can be reduced by 34 (47%)
72
38
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Malwee. 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 as a result speed up the page load time.
malwee.com.br
570 ms
627 ms
style.min.css
612 ms
imprensa.min.css
461 ms
app.min.js
1253 ms
main.min.js
768 ms
iframe_api
85 ms
conversion.js
32 ms
pinit.js
6 ms
tm34937.js
74 ms
PinExt.png
21 ms
logo-malwee@2x.png
320 ms
facebook-icon.png
175 ms
instagram-icon.png
174 ms
loader.gif
319 ms
1.jpg
1524 ms
2.jpg
1885 ms
3.jpg
1605 ms
4.jpg
1119 ms
5.jpg
1370 ms
6.jpg
932 ms
setas-conceito.png
1087 ms
1.jpg
1244 ms
2.jpg
1430 ms
3.jpg
1553 ms
4.jpg
1673 ms
5.jpg
1588 ms
6.jpg
1680 ms
selo-abvtex.png
1709 ms
logo-euabraco.png
1898 ms
1.png
1916 ms
2.png
1829 ms
3.png
1988 ms
11.png
2014 ms
5.png
2137 ms
6.png
2040 ms
7.png
2055 ms
8.png
2074 ms
9.png
2147 ms
10.png
2323 ms
www-widgetapi.js
90 ms
71 ms
Avalon-Demi-webfont.woff
2336 ms
Avalon-Bold-webfont.woff
2202 ms
Avalon-Medium-webfont.woff
2374 ms
plusone.js
128 ms
widgets.js
87 ms
all.js
290 ms
analytics.js
45 ms
fbds.js
374 ms
usr
79 ms
pinit_main.js
32 ms
collect
91 ms
50 ms
count.json
80 ms
req
80 ms
125 ms
pixel
27 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
155 ms
sync
96 ms
cb=gapi.loaded_0
25 ms
cb=gapi.loaded_1
66 ms
fastbutton
139 ms
collect
91 ms
sync
85 ms
postmessageRelay
65 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
78 ms
api.js
77 ms
core:rpc:shindig.random:shindig.sha1.js
132 ms
2536007149-postmessagerelay.js
101 ms
cb=gapi.loaded_0
70 ms
cb=gapi.loaded_1
68 ms
xZQOmYg4x3YaWkTJi1kErvesZW2xOQ-xsNqO47m55DA.woff
121 ms
243 ms
xd_arbiter.php
221 ms
xd_arbiter.php
425 ms
248 ms
jot
117 ms
24 ms
like.php
184 ms
vpc6VNjRPXV.js
488 ms
LVx-xkvaJ0b.png
551 ms
malwee.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
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.
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 IDs are not unique
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
malwee.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
Missing source maps for large first-party JavaScript
malwee.com.br SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 doesn't use legible font sizes
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Malwee.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Malwee.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.
malwee.com.br
Open Graph data is detected on the main page of Malwee. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: