6.1 sec in total
1.7 sec
3.7 sec
712 ms
Click here to check amazing FACES content for Saudi Arabia. Otherwise, check out these important facts you probably never knew about faces.com
Discover the largest selection of Beauty products in UAE
Visit faces.comWe analyzed Faces.com page load time and found that the first response time was 1.7 sec and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
faces.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value7.2 s
5/100
25%
Value13.7 s
2/100
10%
Value4,620 ms
0/100
30%
Value0.755
6/100
15%
Value32.5 s
0/100
10%
1703 ms
261 ms
567 ms
72 ms
231 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 23% of them (15 requests) were addressed to the original Faces.com, 17% (11 requests) were made to Cdn0.faces.com and 11% (7 requests) were made to Cdn2.faces.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Faces.com.
Page size can be reduced by 54.0 kB (19%)
288.5 kB
234.5 kB
In fact, the total size of Faces.com main page is 288.5 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. 60% of websites need less resources to load. Images take 243.4 kB which makes up the majority of the site volume.
Potential reduce by 14.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 14.9 kB or 75% of the original size.
Potential reduce by 34.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. Obviously, FACES needs image optimization as it can save up to 34.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 4.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 4.7 kB or 19% of the original size.
Number of requests can be reduced by 9 (15%)
60
51
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FACES. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
faces.com
1703 ms
261 ms
567 ms
ga.js
72 ms
logo.png
231 ms
5bc7f0a4.jpg
249 ms
9864760.jpg
247 ms
307731b4.jpg
402 ms
aaf4b11c.jpg
400 ms
ca1c2a7a.jpg
243 ms
ad7a3564.JPG
396 ms
81a35bd4.JPG
392 ms
9943914.jpg
387 ms
713c2574.jpg
388 ms
599e78f9.jpg
232 ms
b481d56c.jpg
232 ms
b230694e.jpg
231 ms
a1fea6a8.jpg
231 ms
8236182.jpg
231 ms
cd97c06c.jpg
393 ms
join_now.png
231 ms
18+.jpg
226 ms
2410ddd9.jpg
381 ms
9829435.jpg
381 ms
9847200.jpg
383 ms
6729b77d.jpg
378 ms
67af0fa5.jpg
377 ms
6994995.jpg
521 ms
5c7ebce5.jpg
521 ms
ab472cf2.jpg
515 ms
229e4e3c.jpg
516 ms
5fe7ed88.jpeg
516 ms
female.jpg
192 ms
9645929.jpg
217 ms
ad4409.jpg
217 ms
3e073938.jpg
218 ms
055a2a22.jpg
217 ms
c6493b36.jpg
203 ms
1210ad45.jpg
201 ms
9660fd.jpg
201 ms
2f65eaa9.jpg
202 ms
bdcd6bb5.jpg
222 ms
__utm.gif
42 ms
header.png
183 ms
login.png
183 ms
go.png
184 ms
normal.png
179 ms
plusone.js
130 ms
background.jpg
578 ms
infoLarge.png
234 ms
go_faces.png
235 ms
cheerleader.png
674 ms
157 ms
157 ms
cb=gapi.loaded_0
68 ms
cb=gapi.loaded_1
33 ms
fastbutton
448 ms
postmessageRelay
193 ms
cb=gapi.loaded_0
26 ms
cb=gapi.loaded_1
86 ms
api.js
99 ms
core:rpc:shindig.random:shindig.sha1.js
188 ms
2536007149-postmessagerelay.js
186 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
209 ms
faces.com 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
button, link, and menuitem elements do not have accessible names.
[aria-hidden="true"] elements contain focusable descendents
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
Image elements do not have [alt] attributes
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.
faces.com 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
faces.com 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 uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faces.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 Faces.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.
faces.com
Open Graph data is detected on the main page of FACES. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: