11.1 sec in total
2.4 sec
8.4 sec
342 ms
Welcome to fa-fa.com homepage info - get ready to check Fa best content for Japan right away, or after learning these important things about fa-fa.com
Visit fa-fa.comWe analyzed Fa-fa.com page load time and found that the first response time was 2.4 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fa-fa.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value4.8 s
31/100
25%
Value13.1 s
2/100
10%
Value1,300 ms
18/100
30%
Value0
100/100
15%
Value25.4 s
0/100
10%
2351 ms
191 ms
398 ms
385 ms
402 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 41% of them (39 requests) were addressed to the original Fa-fa.com, 11% (11 requests) were made to O.twimg.com and 7% (7 requests) were made to Api.pinterest.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Fa-fa.com.
Page size can be reduced by 362.9 kB (38%)
967.0 kB
604.1 kB
In fact, the total size of Fa-fa.com main page is 967.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. 50% of websites need less resources to load. Images take 475.0 kB which makes up the majority of the site volume.
Potential reduce by 61.6 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 61.6 kB or 81% of the original size.
Potential reduce by 9.7 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. Fa images are well optimized though.
Potential reduce by 177.4 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 177.4 kB or 68% of the original size.
Potential reduce by 114.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. Fa-fa.com needs all CSS files to be minified and compressed as it can save up to 114.2 kB or 74% of the original size.
Number of requests can be reduced by 52 (57%)
91
39
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fa. 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 16 to 1 for CSS and as a result speed up the page load time.
www.fa-fa.com
2351 ms
style.css
191 ms
styles.css
398 ms
wordpresscom-stats-smiley-remover.css
385 ms
style.css
402 ms
genericons.css
578 ms
jetpack.css
398 ms
tweets.css
397 ms
jquery.js
933 ms
jquery-migrate.min.js
608 ms
jquery.cycle.js
618 ms
superfish.js
597 ms
supersubs.js
597 ms
share.js
27 ms
comment-reply.min.js
787 ms
lib.js
803 ms
main.js
991 ms
jquery.form.min.js
836 ms
scripts.js
845 ms
devicepx-jetpack.js
4 ms
gprofiles.js
57 ms
wpgroho.js
995 ms
sharing.js
1010 ms
e-201611.js
4 ms
screen.css
852 ms
nav.css
845 ms
sdk.js
315 ms
20130516-033534.jpg
1800 ms
20130516-030619.jpg
949 ms
zCoFRr0u_normal.jpeg
76 ms
501cb85349e10bb08bc9f1a7f8088483_normal.jpeg
152 ms
photo3_normal.jpg
171 ms
rss.png
267 ms
cropped-IMG_0017.jpg
567 ms
20130516-033534-150x150.jpg
271 ms
20130516-030619-150x150.jpg
271 ms
search.png
268 ms
li.png
267 ms
twitter-logo.png
414 ms
bg_sm.png
414 ms
info-kino.png
413 ms
ajax-refresh-icon.gif
413 ms
rss.png
414 ms
loading.gif
646 ms
widgets.js
80 ms
Genericons.svg
1100 ms
8AAnjaY2BgYGQAgjO2i86D6AshzNIwGgBAmQUAAAA=
4 ms
ad516503a11cd5ca435acc9bb6523536
37 ms
g.gif
71 ms
ws.php
1827 ms
hovercard.css
61 ms
services.css
106 ms
graph.facebook.com
192 ms
count.json
52 ms
graph.facebook.com
220 ms
count.json
81 ms
graph.facebook.com
212 ms
count.json
77 ms
graph.facebook.com
209 ms
count.json
75 ms
graph.facebook.com
206 ms
count.json
73 ms
graph.facebook.com
200 ms
count.json
70 ms
graph.facebook.com
242 ms
count.json
86 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
84 ms
bg.png
349 ms
ajax-refresh.gif
349 ms
165 ms
xd_arbiter.php
226 ms
xd_arbiter.php
544 ms
syndication
87 ms
334702122446774273
257 ms
proxy.jpg
25 ms
proxy.jpg
100 ms
proxy.jpg
95 ms
proxy.jpg
100 ms
proxy.jpg
72 ms
proxy.jpg
98 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
6 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
14 ms
photo3_normal.jpg
342 ms
Mv4fgDci_normal.jpg
363 ms
iagE61JJ_normal.jpeg
392 ms
B_SfBaWXAAAA_d3.jpg:small
644 ms
B_TJZN5WsAAYFeN.jpg:small
551 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
39 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
54 ms
proxy.jpg
16 ms
proxy.jpg
53 ms
proxy.jpg
35 ms
proxy.jpg
41 ms
proxy.jpg
42 ms
jot.html
2 ms
print.css
198 ms
fa-fa.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
[aria-hidden="true"] elements contain focusable descendents
fa-fa.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
fa-fa.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fa-fa.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Fa-fa.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.
fa-fa.com
Open Graph description is not detected on the main page of Fa. 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: