2.2 sec in total
55 ms
1.8 sec
275 ms
Click here to check amazing Facecard content. Otherwise, check out these important facts you probably never knew about facecard.com
Looking for a nationally recognized leader in engagement, loyalty and incentive solutions? Learn more about Augeo Marketing today!
Visit facecard.comWe analyzed Facecard.com page load time and found that the first response time was 55 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
facecard.com performance score
55 ms
26 ms
1010 ms
29 ms
62 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Facecard.com, 66% (42 requests) were made to Edointeractive.com and 6% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Edointeractive.com.
Page size can be reduced by 347.2 kB (31%)
1.1 MB
786.5 kB
In fact, the total size of Facecard.com main page is 1.1 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 707.7 kB which makes up the majority of the site volume.
Potential reduce by 27.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 27.4 kB or 76% of the original size.
Potential reduce by 46.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. Facecard images are well optimized though.
Potential reduce by 133.8 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 133.8 kB or 60% of the original size.
Potential reduce by 139.2 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. Facecard.com needs all CSS files to be minified and compressed as it can save up to 139.2 kB or 83% of the original size.
Number of requests can be reduced by 28 (49%)
57
29
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Facecard. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
facecard.com
55 ms
edointeractive.com
26 ms
www.edointeractive.com
1010 ms
wp-emoji-release.min.js
29 ms
flexslider.css
62 ms
style.css
67 ms
edo_icons.css
60 ms
styles.css
59 ms
css
24 ms
jquery.fancybox-1.3.7.min.css
135 ms
jetpack.css
62 ms
styles.css
98 ms
jquery.js
125 ms
jquery-migrate.min.js
87 ms
jquery.flexslider-min.js
96 ms
gwu1yoh.js
187 ms
navigation.js
94 ms
jquery.treeview.js
109 ms
jquery.fancybox-1.3.7.min.js
131 ms
orbit.js
128 ms
photon.js
129 ms
jquery.form.min.js
132 ms
scripts.js
159 ms
devicepx-jetpack.js
4 ms
comment-reply.min.js
150 ms
jquery.easing.pack.js
150 ms
jquery.mousewheel.min.js
153 ms
e-201611.js
4 ms
trackalyze.js
189 ms
style.css
103 ms
ga.js
33 ms
www.edointeractive.com
188 ms
__utm.gif
64 ms
collect
52 ms
edotile.gif
43 ms
case-study-icon.png
37 ms
Poland.gif
37 ms
edo-e-logo.png
37 ms
bg-top-header.jpg
38 ms
resources.png
38 ms
about.png
35 ms
blog.png
36 ms
contact.png
36 ms
logo.png
105 ms
edo-banner-brill.jpg
180 ms
edo-banner-macbook-1200.png
315 ms
edo-visaeu-macbook-1200.jpg
255 ms
slide1.jpg
142 ms
icon-btn-arrow.png
103 ms
bg-footer.jpg
142 ms
icon-twitter.png
138 ms
icon-linkedIn.png
156 ms
icon-phone.png
178 ms
demo-play.jpg
29 ms
edo-marketplace.jpg
30 ms
widgets.js
14 ms
yuUb01KcOVXHTbbOaQCbPWACLrENv2DDPCXyrlinWvIffHPfggMmeMJ6Mk6f5Mb.woff
68 ms
RImEWId2bhnTSrSTn5_eketS3DOJ2DOWBcXbeHqG0vvffHAfggMmeMJ6Mk6f5MS.woff
68 ms
trackalyze.asp
102 ms
btn-play.png
66 ms
g.gif
20 ms
p.gif
131 ms
dot.gif
75 ms
icons-slideshow.png
23 ms
facecard.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Facecard.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 Facecard.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.
facecard.com
Open Graph description is not detected on the main page of Facecard. 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: