4.6 sec in total
331 ms
3.7 sec
616 ms
Click here to check amazing Facephi content. Otherwise, check out these important facts you probably never knew about facephi.com
Especialistas en la protección y verificación de la identidad mediante soluciones tecnológicas que crean procesos libres de fraude.
Visit facephi.comWe analyzed Facephi.com page load time and found that the first response time was 331 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
facephi.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value12.9 s
0/100
25%
Value6.5 s
38/100
10%
Value1,480 ms
14/100
30%
Value0.001
100/100
15%
Value14.5 s
8/100
10%
331 ms
135 ms
342 ms
631 ms
677 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 64% of them (38 requests) were addressed to the original Facephi.com, 20% (12 requests) were made to Pbs.twimg.com and 7% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Facephi.com.
Page size can be reduced by 458.3 kB (27%)
1.7 MB
1.2 MB
In fact, the total size of Facephi.com main page is 1.7 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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 17.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. This page needs HTML code to be minified as it can gain 4.8 kB, which is 22% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 17.4 kB or 79% of the original size.
Potential reduce by 87.8 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. Facephi images are well optimized though.
Potential reduce by 216.5 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 216.5 kB or 69% of the original size.
Potential reduce by 136.7 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. Facephi.com needs all CSS files to be minified and compressed as it can save up to 136.7 kB or 84% of the original size.
Number of requests can be reduced by 17 (33%)
51
34
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Facephi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
facephi.com
331 ms
es
135 ms
342 ms
jquery-1.10.2.min.js
631 ms
jquery-ui-1.10.3.custom.min.js
677 ms
bootstrap.min.js
392 ms
cookies.js
267 ms
jquery.fancybox-1.3.4.pack.js
412 ms
toastr.js
283 ms
base.js
394 ms
bootstrap.min.css
844 ms
cookies-black.css
517 ms
jquery-ui-1.8.18.custom.css
725 ms
jquery.fancybox-1.3.4.css
549 ms
toastr.css
724 ms
estilos.css
741 ms
logo.png
189 ms
imagenes-banner-selphi.png
1404 ms
breadcrumbs.png
186 ms
imagenes-h2020.png
1390 ms
imagenes_1-banca.jpg
412 ms
imagenes_1-gobiernos.jpg
532 ms
imagenes_1-seguridad.jpg
415 ms
OpenSans-Regular-webfont.svg
505 ms
OpenSans-Regular-webfont.woff
470 ms
OpenSans-Light-webfont.svg
1013 ms
OpenSans-Light-webfont.woff
621 ms
OpenSans-Semibold-webfont.svg
1311 ms
OpenSans-Semibold-webfont.woff
674 ms
glyphicons-halflings-regular.woff
773 ms
widgets.js
95 ms
facebook.png
831 ms
twitter.png
993 ms
twitter2.png
1225 ms
googleplus.png
1293 ms
pintrest.png
1293 ms
linkedin.png
1293 ms
youtube.png
1462 ms
analytics.js
78 ms
timeline.5d8406ab2e764a871ed41bd9aa0b693f.js
76 ms
collect
21 ms
collect
95 ms
syndication
110 ms
275652967334547456
461 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
24 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
45 ms
a71f8390fd24dce8563d5b66c37576d4_normal.jpeg
645 ms
dy1MzZ-W_normal.png
648 ms
ImnrqnTR_normal.jpeg
649 ms
Lj8r2fnx_normal.jpeg
700 ms
18ef1c0da7f91ba25bc1fd5eda8c455f_normal.png
708 ms
stOXtICS_normal.jpg
737 ms
ProfilePhoto_normal.jpg
740 ms
oRjJYDyT_normal.jpg
736 ms
CdmYry2WEAAShe-.jpg
745 ms
CdmIkrwWoAEyJAq.jpg
800 ms
CdN7HFpXIAIgn-1.jpg
777 ms
CdMRxVmWoAAHRNg.jpg
800 ms
cerrar.png
159 ms
facephi.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
[role]s are not contained by their required parent element
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
facephi.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
facephi.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
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Facephi.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Facephi.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.
facephi.com
Open Graph data is detected on the main page of Facephi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: