7.1 sec in total
1.4 sec
5.5 sec
217 ms
Click here to check amazing MOQLIN content. Otherwise, check out these important facts you probably never knew about moqlin.com
Visit moqlin.comWe analyzed Moqlin.com page load time and found that the first response time was 1.4 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
moqlin.com performance score
1445 ms
802 ms
362 ms
368 ms
1311 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 98% of them (58 requests) were addressed to the original Moqlin.com, 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Moqlin.com.
Page size can be reduced by 161.8 kB (69%)
235.2 kB
73.5 kB
In fact, the total size of Moqlin.com main page is 235.2 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. 35% of websites need less resources to load. Javascripts take 156.1 kB which makes up the majority of the site volume.
Potential reduce by 17.7 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 17.7 kB or 78% of the original size.
Potential reduce by 1.9 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. Obviously, MOQLIN needs image optimization as it can save up to 1.9 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 103.7 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 103.7 kB or 66% of the original size.
Potential reduce by 38.6 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. Moqlin.com needs all CSS files to be minified and compressed as it can save up to 38.6 kB or 84% of the original size.
Number of requests can be reduced by 24 (41%)
58
34
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MOQLIN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.moqlin.com
1445 ms
style.css
802 ms
styles.css
362 ms
postratings-css.css
368 ms
jquery.js
1311 ms
jquery-migrate.min.js
574 ms
usces_cart.css
540 ms
mouseover.js
550 ms
flexslider.css
561 ms
jquery.min.js
34 ms
jquery.flexslider-min.js
1073 ms
usces_cart.js
362 ms
jquery.form.min.js
379 ms
scripts.js
394 ms
postratings-js.js
544 ms
header_bg.gif
191 ms
logo.png
193 ms
membar_btn.png
185 ms
login_btn.png
189 ms
navi1.png
162 ms
navi2.png
180 ms
navi3.png
320 ms
navi4.png
359 ms
navi5.png
368 ms
navi6.png
376 ms
navi7.png
379 ms
navi8.png
384 ms
search_bg.jpg
479 ms
search_btn.png
538 ms
slider1.jpg
1101 ms
slider2.jpg
937 ms
slider3.jpg
1132 ms
slider4.jpg
1150 ms
slider5.jpg
1116 ms
bna1.jpg
716 ms
bna2.jpg
896 ms
bna3.jpg
1076 ms
title1.jpg
1125 ms
pic1.jpg
1438 ms
more_btn.jpg
1284 ms
title2.jpg
1276 ms
pic2.jpg
1311 ms
title1.jpg
1321 ms
lineup_bg.jpg
1342 ms
M_lotion-01.jpg
1437 ms
M_cream-01.jpg
1479 ms
M_trial-01.jpg
1500 ms
title1.jpg
1525 ms
mark.jpg
1533 ms
title2.jpg
1601 ms
title3.jpg
1574 ms
bna1.jpg
1506 ms
bna2.jpg
1512 ms
bna3.jpg
1535 ms
space.jpg
1540 ms
bna4.jpg
1575 ms
footer_logo.gif
1609 ms
copy.gif
1530 ms
rating_over.gif
1520 ms
moqlin.com SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Moqlin.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Moqlin.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.
moqlin.com
Open Graph description is not detected on the main page of MOQLIN. 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: