4.3 sec in total
1.1 sec
2.3 sec
890 ms
Click here to check amazing Face content for Morocco. Otherwise, check out these important facts you probably never knew about face.run
The domain name face.run is for sale. Make an offer or buy it now at a set price.
Visit face.runWe analyzed Face.run page load time and found that the first response time was 1.1 sec and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
face.run performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value4.8 s
30/100
25%
Value4.3 s
75/100
10%
Value200 ms
90/100
30%
Value0.029
100/100
15%
Value6.5 s
59/100
10%
1057 ms
52 ms
39 ms
35 ms
34 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 29% of them (20 requests) were addressed to the original Face.run, 12% (8 requests) were made to S.ytimg.com and 10% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Face.run.
Page size can be reduced by 790.4 kB (56%)
1.4 MB
615.9 kB
In fact, the total size of Face.run main page is 1.4 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. 60% of websites need less resources to load. Javascripts take 621.6 kB which makes up the majority of the site volume.
Potential reduce by 47.9 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 47.9 kB or 80% of the original size.
Potential reduce by 1.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. Face images are well optimized though.
Potential reduce by 360.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 360.1 kB or 58% of the original size.
Potential reduce by 381.0 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. Face.run needs all CSS files to be minified and compressed as it can save up to 381.0 kB or 83% of the original size.
Number of requests can be reduced by 42 (67%)
63
21
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Face. 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 7 to 1 for CSS and as a result speed up the page load time.
face.run
1057 ms
bootstrap.min.css
52 ms
bootstrap-theme.min.css
39 ms
font-awesome.min.css
35 ms
style.css
34 ms
jquery.min.js
67 ms
bootstrap.min.js
40 ms
jquery.lazyloadxt.js
40 ms
jquery.carousel.js
92 ms
functions.js
39 ms
adsbygoogle.js
32 ms
platform.js
122 ms
analytics.js
106 ms
counter.js
47 ms
ca-pub-3958695326520792.js
104 ms
zrt_lookup.html
344 ms
show_ads_impl.js
195 ms
GothamRounded-Book.otf
117 ms
fontawesome-webfont.woff
105 ms
collect
225 ms
t.php
251 ms
cb=gapi.loaded_0
179 ms
cb=gapi.loaded_1
210 ms
subscribe_embed
309 ms
tqESLpRQucQ.jpg
169 ms
8PCh9wnlZAw.jpg
169 ms
6Ps_sOnPjkc.jpg
169 ms
9pgEHx4Bet8.jpg
40 ms
ads
518 ms
tPzNSHvcq6I.jpg
104 ms
osd.js
103 ms
Wclxv1GXKJ0.jpg
86 ms
89nvWWP65lk.jpg
85 ms
ID40NZbKUeI.jpg
85 ms
cE1Zw09JDAY
135 ms
ads
279 ms
postmessageRelay
96 ms
www-subscribe-embed-vflTum1sJ.css
108 ms
photo.jpg
85 ms
www-subscribe-embed.js
107 ms
www-embed-player-vflfNyN_r.css
98 ms
www-embed-player.js
98 ms
base.js
183 ms
3193398744-postmessagerelay.js
161 ms
rpc:shindig_random.js
93 ms
cb=gapi.loaded_0
78 ms
www-hitchhiker-vflvB63an.png
77 ms
abg.js
231 ms
cb=gapi.loaded_0
202 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
167 ms
ad_status.js
139 ms
m_js_controller.js
76 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
141 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
181 ms
cb=gapi.loaded_2
40 ms
favicon
130 ms
s
36 ms
googlelogo_color_112x36dp.png
130 ms
nessie_icon_tiamat_f_white.png
54 ms
x_button_blue2.png
47 ms
border_3.gif
43 ms
subscribe_embed
90 ms
spacer.gif
81 ms
border_3.gif
41 ms
bubbleSprite_3.png
80 ms
bubbleDropR_3.png
81 ms
bubbleDropB_3.png
80 ms
www-subscribe-embed-card-vflqARhQ4.css
6 ms
www-subscribe-embed-card.js
4 ms
face.run accessibility score
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-*] attributes do not match their roles
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
face.run best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
face.run 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Face.run can be misinterpreted by Google and other search engines. Our service has detected that English 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 Face.run 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.
face.run
Open Graph description is not detected on the main page of Face. 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: