10 sec in total
384 ms
9.4 sec
186 ms
Visit facemsk.com now to see the best up-to-date Facemsk content and also check out these interesting facts you probably never knew about facemsk.com
Order a FaceMSK Face Mask Now! Worldwide Delivery ✅ Cheap Delivery Rates ✅ 400+ Designs ✅ 24/7 Customer Support ✅ Same Day Shipping ✅
Visit facemsk.comWe analyzed Facemsk.com page load time and found that the first response time was 384 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
facemsk.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value12.0 s
0/100
25%
Value14.1 s
1/100
10%
Value15,930 ms
0/100
30%
Value0.136
80/100
15%
Value28.0 s
0/100
10%
384 ms
5830 ms
150 ms
252 ms
286 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 66% of them (74 requests) were addressed to the original Facemsk.com, 13% (15 requests) were made to Fonts.gstatic.com and 10% (11 requests) were made to Youtube-nocookie.com. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Facemsk.com.
Page size can be reduced by 624.8 kB (31%)
2.0 MB
1.4 MB
In fact, the total size of Facemsk.com main page is 2.0 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. 80% 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 88.4 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 88.4 kB or 83% of the original size.
Potential reduce by 17.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. Facemsk images are well optimized though.
Potential reduce by 61.9 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 61.9 kB or 35% of the original size.
Potential reduce by 457.3 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. Facemsk.com needs all CSS files to be minified and compressed as it can save up to 457.3 kB or 75% of the original size.
Number of requests can be reduced by 64 (75%)
85
21
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Facemsk. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
facemsk.com
384 ms
facemsk.com
5830 ms
wp-emoji-release.min.js
150 ms
style.min.css
252 ms
vendors-style.css
286 ms
style.css
384 ms
styles.css
289 ms
front-flex.min.css
287 ms
sow-image-default-17bc2272b535.css
286 ms
woocommerce-layout.css
345 ms
woocommerce.css
389 ms
style.css
380 ms
style.css
381 ms
admin-bar-style.css
388 ms
css
30 ms
font-awesome.min.css
448 ms
simple-line-icons.css
479 ms
owl.carousel.css
480 ms
owl.theme.css
482 ms
jquery.bxslider.min.css
476 ms
flexslider.css
482 ms
style.css
550 ms
animate.css
580 ms
jetpack.css
675 ms
jquery.js
691 ms
jquery.cookie.js
583 ms
language-cookie.js
584 ms
script.js
644 ms
gtm4wp-form-move-tracker.js
710 ms
gtm4wp-woocommerce-enhanced.js
711 ms
SmoothScroll.min.js
688 ms
wds_effects.css
785 ms
font-awesome.css
786 ms
wds_frontend.css
784 ms
scripts.js
784 ms
jquery.blockUI.min.js
785 ms
add-to-cart.min.js
783 ms
js.cookie.min.js
880 ms
e-202241.js
15 ms
woocommerce.min.js
878 ms
cart-fragments.min.js
784 ms
owl.carousel.min.js
698 ms
theia-sticky-sidebar.min.js
645 ms
jquery.matchHeight-min.js
645 ms
jquery.sticky.js
926 ms
jquery.countdown.js
924 ms
jquery.bxslider.min.js
863 ms
jquery.flexslider-min.js
830 ms
wow.min.js
831 ms
skip-link-focus-fix.js
823 ms
navigation.js
950 ms
isotope.pkgd.min.js
952 ms
imagesloaded.min.js
895 ms
buzzstorepro-custom.js
861 ms
front-scripts.min.js
864 ms
cart_widget.min.js
861 ms
wp-embed.min.js
1080 ms
jquery.mobile.js
1081 ms
wds_frontend.js
1000 ms
gtm.js
146 ms
yI7iU7X3cCU
231 ms
Check-300x300.png
1092 ms
logo_o_medium.png
811 ms
cropped-cropped-WebsiteIdentiteitv3.png
805 ms
en.png
804 ms
nl.png
804 ms
de.png
1083 ms
0.gif
1084 ms
Homepage-Header-Skull-01-EN.jpg
1178 ms
FaceMSK-Bar.jpg
1091 ms
Payment-methods-FaceMSK.png
1084 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
58 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
86 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
102 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
101 ms
fontawesome-webfont.woff
1023 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff
100 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff
99 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff
100 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff
100 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff
127 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exg.woff
127 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exg.woff
125 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWV4exg.woff
126 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exg.woff
125 ms
Simple-Line-Icons.ttf
1016 ms
analytics.js
72 ms
www-player.css
28 ms
www-embed-player.js
51 ms
base.js
87 ms
fetch-polyfill.js
48 ms
collect
32 ms
Create
195 ms
qoe
165 ms
GMxt2AoYqj2WXpyEdgkoen9XiD3znMxv6lengZkwUWM.js
158 ms
embed.js
101 ms
qoe
21 ms
log_event
1 ms
yI7iU7X3cCU
201 ms
fontawesome-webfont.woff
515 ms
facemsk.com
1548 ms
GMxt2AoYqj2WXpyEdgkoen9XiD3znMxv6lengZkwUWM.js
66 ms
embed.js
26 ms
Create
236 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
135 ms
KFOmCnqEu92Fr1Mu4mxM.woff
133 ms
Homepage-Header-Camo-01-EN.jpg
379 ms
GenerateIT
20 ms
Homepage-Header-Animal-01-EN.jpg
192 ms
Homepage-Header-Clown-01-EN.jpg
100 ms
Homepage-Header-LastShot-EN.jpg
103 ms
woocommerce-smallscreen.css
97 ms
facemsk.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.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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.
facemsk.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
facemsk.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Facemsk.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Facemsk.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.
facemsk.com
Open Graph data is detected on the main page of Facemsk. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: