6.5 sec in total
336 ms
5.5 sec
690 ms
Welcome to mrolo.com homepage info - get ready to check Mrolo best content right away, or after learning these important things about mrolo.com
A MRolo Manequins é distribuidor líder de manequins e equipamento comercial para as indústrias da moda e retalho. Conheça as nossas criativas soluções.
Visit mrolo.comWe analyzed Mrolo.com page load time and found that the first response time was 336 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
mrolo.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value14.8 s
0/100
25%
Value14.0 s
1/100
10%
Value2,260 ms
6/100
30%
Value0.002
100/100
15%
Value26.7 s
0/100
10%
336 ms
3001 ms
131 ms
555 ms
344 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 81% of them (73 requests) were addressed to the original Mrolo.com, 4% (4 requests) were made to Gstatic.com and 3% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Mrolo.com.
Page size can be reduced by 1.4 MB (56%)
2.5 MB
1.1 MB
In fact, the total size of Mrolo.com main page is 2.5 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. 55% of websites need less resources to load. Javascripts take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 147.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 147.5 kB or 83% of the original size.
Potential reduce by 1.3 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. Mrolo images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 52% of the original size.
Potential reduce by 195.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. Mrolo.com needs all CSS files to be minified and compressed as it can save up to 195.9 kB or 68% of the original size.
Number of requests can be reduced by 59 (83%)
71
12
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mrolo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
mrolo.com
336 ms
mrolo.com
3001 ms
egoimmerce.js
131 ms
dashicons.min.css
555 ms
jquery-ui-dialog.min.css
344 ms
classic-themes.min.css
329 ms
styles.css
330 ms
egoi-for-wp-public.css
336 ms
wpcf7-redirect-frontend.min.css
355 ms
cookieblocker.min.css
431 ms
if-menu-site.css
435 ms
style.css
548 ms
flatsome.css
777 ms
flatsome-shop.css
583 ms
style.css
539 ms
egoi-for-wp-canvas.js
543 ms
jquery.min.js
674 ms
jquery-migrate.min.js
648 ms
language-cookie.js
652 ms
collect
493 ms
core.min.js
339 ms
mouse.min.js
378 ms
resizable.min.js
436 ms
draggable.min.js
649 ms
controlgroup.min.js
449 ms
checkboxradio.min.js
639 ms
button.min.js
639 ms
dialog.min.js
647 ms
index.js
647 ms
index.js
647 ms
jquery.blockUI.min.js
646 ms
add-to-cart.min.js
646 ms
js.cookie.min.js
750 ms
woocommerce.min.js
756 ms
cart-fragments.min.js
753 ms
wpcf7r-fe.js
751 ms
front-scripts.min.js
754 ms
cart_widget.min.js
751 ms
index.js
860 ms
api.js
72 ms
regenerator-runtime.min.js
861 ms
api.js
89 ms
wp-polyfill.min.js
862 ms
index.js
866 ms
hoverIntent.min.js
866 ms
flatsome.js
974 ms
flatsome-lazy-load.js
941 ms
infinite-scroll.pkgd.min.js
865 ms
flatsome-infinite-scroll.js
864 ms
woocommerce.js
849 ms
complianz.min.js
765 ms
zxcvbn-async.min.js
861 ms
hooks.min.js
856 ms
i18n.min.js
825 ms
password-strength-meter.min.js
762 ms
password-strength-meter.min.js
765 ms
hmsb4awdbr
228 ms
pt-pt.png
616 ms
es.png
673 ms
en.png
672 ms
img-logo-header.png
677 ms
barra_feder-800x103.jpg
682 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXx-p7K4GLs.woff
564 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXx-p7K4GLvztg.woff
583 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw2aXx-p7K4GLvztg.woff
658 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXx-p7K4GLvztg.woff
655 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw0aXx-p7K4GLvztg.woff
677 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXx-p7K4GLs.woff
677 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXx-p7K4GLvztg.woff
677 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w2aXx-p7K4GLvztg.woff
710 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXx-p7K4GLvztg.woff
778 ms
insight.min.js
29 ms
insight_tag_errors.gif
159 ms
clarity.js
16 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w0aXx-p7K4GLvztg.woff
659 ms
fl-icons.ttf
674 ms
EJRSQgYoZZY2vCFuvAnt66qSVy3Vp8NA.woff
673 ms
EJRSQgYoZZY2vCFuvAnt66qcVy3Vp8NAyIw.woff
701 ms
EJRSQgYoZZY2vCFuvAnt66qWVy3Vp8NAyIw.woff
700 ms
EJRSQgYoZZY2vCFuvAnt66qfVy3Vp8NAyIw.woff
761 ms
recaptcha__en.js
26 ms
recaptcha__pt_pt.js
39 ms
zxcvbn.min.js
547 ms
fallback
20 ms
c.gif
7 ms
fallback__ltr.css
3 ms
css
28 ms
logo_48.png
3 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
20 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
23 ms
mrolo.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
mrolo.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
mrolo.com 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
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mrolo.com 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 Mrolo.com 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.
mrolo.com
Open Graph data is detected on the main page of Mrolo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: