FACEBOOK.JP SEO SCORE

  • Passed
  • To Improve
  • Errors

www.facebook.jp

74,15 is not bad for a web site but not good for a better web site. There are things has been don on this site but seems not enough. Check our SEO articles or see listed information about web sites and make changes on your sites.

SEO Analyse for facebook.jp

SPEED
64 /100
Last Update : 2015-11-04 Check Again
  • Title Tag :

    The title tag of your web page has 31 characters. Best number is between 50-60 characters for most search engines.

    » Facebook - フェイスブック - ログイン (日本語)

  • Meta Description :

    Meta Description of your web site has length of 994 characters. There is no limit for Meta Desciription Lenght but search engines usally don’t show longer than 160 caharacters. You should keep between 150-160 characters.

    » Facebookは、友達や同僚、同級生、近所の人たちと交流を深めることのできるソーシャルユーティリティサイトです。....

  • Meta Keywords :

    Meta Keywords help search engines to understand what website is about and what kind of content serves to people. Meta Keywords are hidden in HTML code. Only search engines can see. Meta Keywords in your page is listed down below.

  • Keyword Cloud :

    Important keywords for your page are listed down below. Visitors can see Keyword Cloud on your page with a larger fonts.

    • » 3 times : facebookロゴ
    • » 2 times : 別の単語を表示
    • » 2 times : english (us)
    Sign Up here to see ful list for free!
  • H Tags :

    Heading is very important for HTML structure and that means very important for search engines as well. Use your important keyword H1 and never duplicate it.

    • » H1 (1 times) :
      • Facebookロゴ
    • » H2 (2 times) :
      • ブラウザでJavascriptが無効になっています。
      • セキュリティチェック
  • Meta Tags :

    Meta Tags describes aspect of the content of a web page.

    • Description : Facebookは、友達や同僚、同級生、近所の人たちと交流を深めることのできるソーシャルユーティリティサイトです。...
    • referrer : origin-when-crossorigin
    • og:site_name : facebook
    • og:url : https://ja-jp.facebook.com/
    • og:image : https://www.facebook.com/images/fb_icon_325x325.png
    • og:locale : ja_jp
    • robots : noodp,noydir
    More
  • HTML Tags :

    An HTML tag is a text document which must be used to explain the page structure.

    • » option :157
    • » div :81
    • » a :49
    • » link :37
    • » input :33
    • » td :31
    • » i :16
    • » script :13
    • » li :11
    • » meta :10
    • » span :9
    • » label :7
    • » tr :6
    • » img :4
    • » form :3
    • » noscript :3
    • » select :3
    • » button :2
    • » h2 :2
    • » p :2
    • » table :2
    • » body :1
    • » br :1
    • » h1 :1
    • » head :1
    • » html :1
    • » tbody :1
    • » title :1
    • » u :1
    • » ul :1
    More
  • Site Speed :

    Site speed for this page is 609 ms. You only have 10-20 seconds to impress your visitors; use this opportunity the best way you can.

    » 609 ms

MOBILE INSIGHTS

SPEED
56 /100
Last Update : 2015-11-04 Check Again
  • Prevent landing website page redirects :

    The page has 3 redirects. Before the page can be reloaded, redirects are meant to introduce additional relays. The redirects allow to send the visitors of a particular domain or a certain page to a completely different URL. Use redirects to send a user from a short to along URL.

    Evade landing page redirects for the following sequences of redirected URLS.

  • Active compression on webpage :

    Compression is enabled. Modern browsers automatically negotiate and support compression for the HTTP requests. If compression is enabled, overall size of the transferred response reduces by 90 %, which reduces the amount of time taken to download the resource and save data. Learn more about the process of enabling compression.

  • Leverage web browser cache :

    Browser caching is enabled. Know more about browser caching recommendations.

  • Reduce web server response time :

    The server can respond quickly. Know more about the server response time optimization process. The time taken to load the HTML in order to start rendering the page is called Server response time. A highly varying server response time, can indicate a basic performance issue.

  • Minimize CSS :

    The CSS is minified .Minification can lead to reduced byte count in the common CSS by the process of stripping down all the whitespace and by shortening the names of colors. You can use a filter to evade the extra step of minifying CSS. Know more minifying CSS.

  • Minimize HTML :

    The HTML is minified. Know more about minifying HTML. With the original settings, your compressed copy HTML layout will be hundred percent identical to the previous original layout in all the browsers. Moreover, optional settings give you savings that are more efficient. HTML compressor does not require dependencies.

  • Minimize JavaScript :

    If you compact java Script code, you can save on many bytes of data as well as speed up the parsing, downloading, as well as the execution time. The best way to make a webpage more responsive is by minimizing the number of files and the size of files.

    Minimizing JavaScript for the following resources will help to reduce the size in bytes. 1KiB (2% Reduce the number of files that have to be downloaded when the page is being loaded to make the response rate of the web page much faster .Some tool sexist to minimize the size .

  • When you publish your website you should put your Javascript and CSS code below in your HTML code. :

    The page has 2 blocking CSS resources and 1 blocking script resources. This causes a lag in the rendering of the page. All the CSS resources whether it exhibits is non-blocking or blocking behavior have to be downloaded by the web browser. CSS is treated as render blocking resource by default.

    Neither of the above –the fold contents on the page could have been rendered properly without having to wait for the following resources to load. Instead, you try to defer or asynchronously load the blocking resources or inline the crucial portions of the same resources directly in the HTML.

    Remove the render blocking JavaScript. Normally, external blocking scripts will wait for the web browser to wait for the fetching of the Java Script. this may or may not add more than one network round trips before the webpage can be rendered. This is to drastically improve loading time.

    Optimization of CSS delivery of the following. If the CSS external resources are small, then you can directly insert those inside the HTML document. This is called in lining. Inlining the small CSS resources in the similar fashion, enables the browser, to proceed with rendering of the web page.

  • Stow images :

    The images are optimized. Know more about the process of optimizing images. Images account for most of the basic downloaded bytes on the page and occupy visual space. That is why optimizing the images can result in the large saving of bytes and improved performance on the websites.

  • Priority visible web content :

    The above-the- fold content is properly prioritized. Know more about the prioritizing of visible content. Rendering a new web page needs many network resources, however not all of them are needed right then and there. The visible content in the page is prioritized on the browser and the network.

DESKTOP INSIGHTS

SPEED
84 /100
Last Update : 2015-11-04 Check Again
  • Prevent landing website page redirects :

    The page has 2 redirects. Before the page can be reloaded, redirects are meant to introduce additional relays. The redirects allow to send the visitors of a particular domain or a certain page to a completely different URL. Use redirects to send a user from a short to along URL.

    Evade landing page redirects for the following sequences of redirected URLS.

  • Active compression on webpage :

    Compression is enabled. Modern browsers automatically negotiate and support compression for the HTTP requests. If compression is enabled, overall size of the transferred response reduces by 90 %, which reduces the amount of time taken to download the resource and save data. Learn more about the process of enabling compression.

  • Leverage web browser cache :

    Browser caching is enabled. Know more about browser caching recommendations.

  • Reduce web server response time :

    The server can respond quickly. Know more about the server response time optimization process. The time taken to load the HTML in order to start rendering the page is called Server response time. A highly varying server response time, can indicate a basic performance issue.

  • Minimize CSS :

    The CSS is minified .Minification can lead to reduced byte count in the common CSS by the process of stripping down all the whitespace and by shortening the names of colors. You can use a filter to evade the extra step of minifying CSS. Know more minifying CSS.

  • Minimize HTML :

    The HTML is minified. Know more about minifying HTML. With the original settings, your compressed copy HTML layout will be hundred percent identical to the previous original layout in all the browsers. Moreover, optional settings give you savings that are more efficient. HTML compressor does not require dependencies.

  • Minimize JavaScript :

    If you compact java Script code, you can save on many bytes of data as well as speed up the parsing, downloading, as well as the execution time. The best way to make a webpage more responsive is by minimizing the number of files and the size of files.

    Minimizing JavaScript for the following resources will help to reduce the size in bytes. 2.7KiB (1% Reduce the number of files that have to be downloaded when the page is being loaded to make the response rate of the web page much faster .Some tool sexist to minimize the size .

  • When you publish your website you should put your Javascript and CSS code below in your HTML code. :

    The page has 3 blocking CSS resources and 1 blocking script resources. This causes a lag in the rendering of the page. All the CSS resources whether it exhibits is non-blocking or blocking behavior have to be downloaded by the web browser. CSS is treated as render blocking resource by default.

    Neither of the above –the fold contents on the page could have been rendered properly without having to wait for the following resources to load. Instead, you try to defer or asynchronously load the blocking resources or inline the crucial portions of the same resources directly in the HTML.

    Remove the render blocking JavaScript. Normally, external blocking scripts will wait for the web browser to wait for the fetching of the Java Script. this may or may not add more than one network round trips before the webpage can be rendered. This is to drastically improve loading time.

    Optimization of CSS delivery of the following. If the CSS external resources are small, then you can directly insert those inside the HTML document. This is called in lining. Inlining the small CSS resources in the similar fashion, enables the browser, to proceed with rendering of the web page.

  • Stow images :

    The images are optimized. Know more about the process of optimizing images. Images account for most of the basic downloaded bytes on the page and occupy visual space. That is why optimizing the images can result in the large saving of bytes and improved performance on the websites.

  • Priority visible web content :

    The above-the- fold content is properly prioritized. Know more about the prioritizing of visible content. Rendering a new web page needs many network resources, however not all of them are needed right then and there. The visible content in the page is prioritized on the browser and the network.

MOBILE USABILITY

SPEED
93 /100
Last Update : 2015-11-04 Check Again
  • Prevent application load interstitials that hide content :

    Your page does not appear to contain any application install interstitials that hides a notable amount of content. Know more about the importance of evading the use of application install interstitials

  • Prevent website page plugins :

    Your page does not seem to utilize plugins, which could be beneficial to prevent use of content on many platforms. Plugins do not work on mobile pages properly. Plugins are the leading cause of crashes, hangs and other such security incidents. Know more about the necessity of evading plugins.

  • Configure the web page viewport :

    Your page designates a viewport that is similar to the size of the mobile device. This enables it to render correctly on all the devices. A viewport actively controls how each webpage is displayed on the screen of a mobile device. Know more about the configuration process of viewports.

  • Size content to viewport :

    All the contents of the page fit in the viewport. Know more about sizing the content to the viewport. In developing the mobile site equipped with a Meta viewport tag, it is simple to accidently create content on a page which does not quite fit within the specific viewport.

  • Size tap targets appropriately :

    Some of the buttons /links on the webpage might be too small for a user to tap on the touchscreen easily. Think about making the tap targets larger to facilitate ease of access for the user. This will prevent users from getting frustrated when they tap the wrong target.

    The preceding tap targets are very close to the other tap targets and might need some extra spacing around them. Tap targets should be spaced far out to ensure that a particular user could easily press these tap targets without their finger pad accidentally overlapping other nearby tap targets.

  • Use legible font sizes :

    The text on the page is legible enough. It is important to configure a specific viewport, which will ensure that the fonts are scaled as per the expectations across all the different devices. Get more information about using legible font sizes. Use base font size of 16 CSS pixels.

TECHNOLOGY & NETWORK

  • » script :

    usage

  • » stylesheet :

    usage

SECURITY

Last Update : 2015-11-04 Check Again
  • WOT Rating :

    Excellent

  • Child Status :

    Excellent

  • AVG Antivirus AVG Antivirus
    Safe
  • Google Status Google Status
    Safe
  • Mcafee Mcafee
    Safe

HTML ANALYSE

Last Update : 2015-11-04 Check Again
  • Site :

    facebook.jp

  • Host :

    ja-jp.facebook.com

  • Site Language :

    ja

  • Site IP :

    66.220.146.5

  • Page Speed :

    609 ms

  • Charset :

    utf-8

  • HTML Size :
    • » mobile :
      • Request : 2.06 kb
      • Html : 27.01 kb
      • Css : 204.35 kb
      • Text : 0 kb
      • Image : 8.29 kb
      • Javascript : 728.46 kb
      • Other : 1.27 kb
    • » desktop :
      • Request : 2.05 kb
      • Html : 60.22 kb
      • Css : 305.43 kb
      • Text : 0 kb
      • Image : 57.27 kb
      • Javascript : 3496.32 kb
      • Other : 0.71 kb
  • Response Headers:

    Pragma : no-cache

    X-XSS-Protection : 0

    X-Content-Type-Options : nosniff

    X-Frame-Options : DENY

    X-FB-Stats-Contexts : www,V3

    Vary : Accept-Encoding

    Transfer-Encoding : chunked

    Connection : keep-alive

    Cache-Control : private, no-cache, no-store, must-revalidate

    Content-Type : text/html