3.1 sec in total
9 ms
1.9 sec
1.2 sec
Welcome to faceraceblog.wordpress.com homepage info - get ready to check Face Race Blog Wordpress best content for United States right away, or after learning these important things about faceraceblog.wordpress.com
a training game to reduce the cross race effect: the human tendency to more easily recognize members of our own race
Visit faceraceblog.wordpress.comWe analyzed Faceraceblog.wordpress.com page load time and found that the first response time was 9 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
faceraceblog.wordpress.com performance score
name
value
score
weighting
Value3.2 s
45/100
10%
Value4.7 s
32/100
25%
Value4.1 s
79/100
10%
Value1,130 ms
23/100
30%
Value0.235
53/100
15%
Value17.9 s
4/100
10%
9 ms
346 ms
123 ms
125 ms
125 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Faceraceblog.wordpress.com, 32% (21 requests) were made to Faceraceblog.files.wordpress.com and 17% (11 requests) were made to Fonts.wp.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Faceraceblog.files.wordpress.com.
Page size can be reduced by 117.2 kB (21%)
568.0 kB
450.8 kB
In fact, the total size of Faceraceblog.wordpress.com main page is 568.0 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. 65% of websites need less resources to load. Images take 236.4 kB which makes up the majority of the site volume.
Potential reduce by 116.1 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 116.1 kB or 76% of the original size.
Potential reduce by 0 B
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 Race Blog Wordpress images are well optimized though.
Potential reduce by 779 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 268 B
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. Faceraceblog.wordpress.com has all CSS files already compressed.
Number of requests can be reduced by 21 (41%)
51
30
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Face Race Blog Wordpress. 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 12 to 1 for CSS and as a result speed up the page load time.
faceraceblog.wordpress.com
9 ms
faceraceblog.wordpress.com
346 ms
webfont.js
123 ms
125 ms
style.css
125 ms
153 ms
123 ms
158 ms
css
165 ms
146 ms
global.css
151 ms
149 ms
hovercards.min.js
144 ms
wpgroho.js
149 ms
147 ms
147 ms
w.js
147 ms
css
55 ms
global-print.css
2 ms
conf
108 ms
importmap-polyfill.min.js
14 ms
ga.js
119 ms
modeller_morph_race1.jpg
253 ms
wpcom-gray-white.png
55 ms
move-face.gif
1249 ms
move-eye.gif
212 ms
move-nose.gif
215 ms
strength-nose-large.gif
190 ms
strength-nose-small.gif
182 ms
radius-lips-large.gif
268 ms
radius-lips-small.gif
265 ms
contract-lips.gif
452 ms
screen-shot-2016-05-05-at-10-22-27-pm.png
520 ms
screen-shot-2016-05-05-at-10-24-39-pm.png
589 ms
screen-shot-2016-05-05-at-10-22-58-pm.png
690 ms
move-arrow-black.png
353 ms
contract-arrow-black.png
442 ms
expand-arrow-black.png
558 ms
uv-deformation.gif
550 ms
img_1768-copy-2.jpg
609 ms
screen-shot-2016-05-06-at-9-39-35-pm.png
812 ms
screen-shot-2016-05-06-at-10-21-48-pm.png
696 ms
258316_55e9_4.jpg
687 ms
2ed8d47f-021b-470b-a2a6-d105bd5c9a95.jpg
684 ms
g.gif
133 ms
136 ms
g.gif
134 ms
g.gif
135 ms
rP2Bp2a15UIB7Un-bOeISG3pHlU28A.ttf
134 ms
rP2cp2a15UIB7Un-bOeISG3pFuAT4CDc6A.ttf
134 ms
rP2fp2a15UIB7Un-bOeISG3pHl4G-Qn8.ttf
132 ms
rP2ap2a15UIB7Un-bOeISG3pHl4OTCzs4Yuz.ttf
155 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
156 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
154 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
158 ms
z7NFdQDnbTkabZAIOl9il_O6KJj73e7Ff0GmDuvMQg.ttf
158 ms
Genericons.svg
52 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
2 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWV4exQ.ttf
156 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWV4exQ.ttf
156 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWV4exQ.ttf
156 ms
ata.js
131 ms
__utm.gif
67 ms
actionbar.css
3 ms
actionbar.js
16 ms
faceraceblog.wordpress.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
Image elements do not have [alt] attributes
Links do not have a discernible name
faceraceblog.wordpress.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
faceraceblog.wordpress.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 Faceraceblog.wordpress.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 Faceraceblog.wordpress.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.
faceraceblog.wordpress.com
Open Graph data is detected on the main page of Face Race Blog Wordpress. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: